Human Skills · Presenting

Presentations That Work

Definition

Presenters want their audience to remember the main message — and ideally to want more: downloading the paper, buying the book, or inviting the presenter back. A good presentation delivers an important message, is somewhat entertaining, and leaves the audience wanting more — but entertainment is never a substitute for solid technical content underneath it. Good technical speaking skills open career opportunities in a way that’s easy to underrate until you’re five years into a job and want to try something new.

Learning Outcome

After using this technique, you should be able to structure and deliver a technical talk that respects a fixed time limit, stays focused on a handful of memorable points, and survives technical failure — rather than a talk that tries to cover everything and loses the room halfway through.

Core Structure

Structure and content:

  1. Tell a story. Give the talk a real beginning, middle, and end. Address what the audience should care about, and why they should care about it.
  2. Pick a realistic scope. Choose the most important elements for the time you actually have, and stick to a core message — trust that your paper carries the rest of the detail.
  3. Stay focused. Identify your key points first, then remove anything from the talk that doesn’t help the audience understand and respect them.
  4. Make slides complement what you say, not repeat it. Put technical details, dates, names, and facts on the slide and trust the audience to read them — don’t recite them aloud. Include a big-picture diagram illustrating the overall mental model. A slide’s title should state the point being made, not just label a topic. Avoid slides that are just an outline of what you’re about to say.

Delivery and preparation:

  1. Prepare for disaster. Keep a copy of your slides available online or on another device, and be ready to speak even if the slides fail entirely.
  2. Be ready to explain and defend what you say. Anticipate likely questions and have backup material ready. Don’t say things in the talk you’re not prepared to defend — and if you don’t know the answer to a question, say “I don’t know” rather than improvising.
  3. Respect your time limit. Practice and track how long the talk actually takes. Know what you’ll cut if you’re running long, and never go over your allotted time.
  4. Dress up. Wear clothes from the more formal end of your own wardrobe.

Story and close:

  1. Remind the audience where they are in the story. For longer talks, periodically signal which part of the arc you’re in — an outline slide revisited partway through works well.
  2. Make your final key points. End with a handful (3–5) of clear, concise takeaways that synthesize the story and remind the audience what they should care about and why.

Worked Example

A 3-minute talk on “how to debug a Java program” (the kind of everyday-technical topic this skill applies to as well as any research topic): the story is “debugging is a search problem, not a guessing problem” (rule 1). Scope narrows to one technique — binary-searching a stack trace to isolate a failure — rather than trying to cover every debugging strategy (rule 2). Two slides: one diagram showing the search-space-halving idea, one showing a real stack trace with the search boundary marked; slide titles state the point (“Cut the search space in half each time”), not just “Debugging Tips” (rule 4). The talk closes with three takeaways: debugging is a search problem, binary search beats linear scanning, and this generalizes past Java to any language with a call stack (rule 10).

Common Pitfalls

  • Slides that are really just an outline of the spoken content — the audience reads faster than you can talk, so this makes the talk feel slow rather than clear.
  • No backup plan when the projector, laptop, or slide file fails.
  • Going over the time limit rather than having a plan for what to cut.
  • A talk that tries to cover everything in the paper instead of a focused subset with a real through-line.
  • Ending without distinct, memorable key points — trailing off instead of closing.

Rubric / Checklist

  • Has a real beginning, middle, and end — a story, not a list
  • Scope fits the time available; a core message survives, not everything from the paper
  • Every part of the talk connects to a key point; disconnected content is cut
  • Slides complement the spoken word rather than repeating it; titles state the point
  • A backup plan exists for technical failure
  • Anticipated questions have been thought through in advance
  • Practiced against the actual time limit, with a plan for what to cut if needed
  • Dressed appropriately for the venue
  • Longer talks periodically remind the audience where they are in the story
  • Closes with 3–5 clear, memorable key points