Tell a story
Give the talk a narrative: why you did what you did, what the main challenges were, and the decisions you made along the way. A bare list of results with no throughline is hard to follow and easy to forget.
A technical talk works when the audience follows your reasoning and leaves holding the key technical points. These ten tips cover the whole arc: the story you tell, the slides you show, the language you use, and how you rehearse.
From the narrative and your slides to your technical language and delivery.
Give the talk a narrative: why you did what you did, what the main challenges were, and the decisions you made along the way. A bare list of results with no throughline is hard to follow and easy to forget.
Avoid trivial statements that amount to “good things are good and bad things are bad.” Spend your explanation where two or more valid options existed; you do not need to explain why you picked the obviously good option over an obviously bad one.
Rehearse out loud and record yourself. Some habits and tics, in your speech and your delivery, you simply will not notice until you watch the recording.
Do not overload a slide with information, and do not overuse heavy or decorative graphics. A crowded slide competes with you for the audience’s attention instead of supporting you.
Do not put anything on a slide that you do not expect the audience to read or understand. If it is not meant to be read, it does not belong there.
Remember that this is a technical presentation. Phrase your statements in clear technical language, using the right concepts and terms rather than vague paraphrase.
Make sure you know how the key model names, methods, and concepts are pronounced in English. Mispronouncing the core terms quietly undercuts your command of the material.
Make sure no important technical information is missing. The talk is technical, so your job is to actually deliver the technical points, not to talk around them.
Optimize the information content of the talk: give more time to the richer, more informative items, and less to the routine ones. Not every point deserves an equal slice of the clock.
Use visualizations, graphs, and diagrams wherever they fit, instead of or alongside text. A good figure often carries a technical point better than a paragraph does.