Talk checklist

TalkChecklist.md

This is to be copied and used as a template. The best practice is to start with your conclusion and introduction. Once these sections are done you can focus on your talk outline. From there everything should follow. SELECTION COMMITTEES:

Many selection committees are looking for these things when they score a proposal: Relevance: Is this topic interesting to an audience of Go programmers? What is it about the topic that is unique to its use of Go? Novelty and Originality: Does the talk provide the audience with new information? Preference will be given to presentations not previously available to a wide audience. Knowledge: Has the speaker demonstrated a strong understanding of their subject? Coverage: Does the proposal cover the topic in depth? What are the main insights? Organization: Is the proposal well organized? Will the audience tune into the narrative? Will the speaker use their time effectively? Bottom Line: What’s the takeaway of your talk? How will the presentation improve attendees’ knowledge, outlook, and inspiration? TITLE:

A descriptive title tells attendees what your talk is about. Keep it short, pithy, and to the point. Maybe it could be a little punny, or a little cryptic, but please avoid 8 shocking things that make your proposal read like a Buzzfeed headline. TARGET AUDIENCE

Who you think would be interested in this talk CONCLUSION (5 sentences) =======================================================================I I I believe X (this is a hard cold fact) I have shown you X We now both agree on X Call to Action The have shown or both agree statement can get the extra sentence. INTRODUCTION (5 sentences)

I believe X (this is a hard cold fact) I believe X because (this is why I am an authority) This is the problem I see. What I am going to share/teach The believe X because or the problem I see statement can get the extra sentence. KEY TAKEAWAYS (bullet points)

It’s important that attendees leave your session with clear takeaways. List what attendees will learn from the talk including examples or GitHub repositories. Just the facts. One sentence that describes the topic that you’ll be talking about, and one sentence that describes what the audience will take away from listening to your talk or participating in your workshop, is all you need. But, just like a tweet, make those sentences count. ABSTRACT

Abstracts are the hook for other people to sync into - I like them when they show some personality too. These are better with a little more of your personality throughout it! OUTLINE (5 sentences then bullet points)

The outline describes the content of the talk and provides additional details. BIO (5 sentences)

Who are you REFERENCES/BIBLIOGRAPHY (Bullet points)