Start presentations on the second slide
Presenters and engineers weigh the benefits of skipping traditional slide-deck preambles—title, bio, company history—in favor of jumping straight into the “good part” of a talk, such as a compelling problem, demo, or punchline. Many argue that audiences, especially at technical conferences, have limited attention and care more about concrete value, clear stories, and bottom-line insights than credentials or exhaustive context, which can often be moved later or offloaded to handouts. Others note that context, pacing, and even conventional structures still matter in some settings, emphasizing that effective presentations balance engagement with audience needs, presentation goals, and the dual role of slides as both live aids and later reference material.
Hook-first presentations (“start on the second slide”)
- Many agree that talks and videos waste early minutes on titles, credentials, history, or company bios; viewers often skip ahead to “the first code slide” or use heuristics like jumping to 30%.
- Recommended pattern: start with the problem, payoff, or “spoilers” (end state, key results, demo), then fill in background. Related ideas: inverted pyramid, BLUF, “do the last thing first,” in medias res.
- This is seen as especially effective for technical talks, demos, and sales: don’t make the audience “earn” the payoff.
Role of the first slide / intro content
- First slide is often treated as a static “book cover” or room locator while people settle; many suggest not talking to it at all, or advancing quickly.
- Some argue intros help nervous speakers warm up and cover latecomers, but should be kept to ~15–30 seconds.
- Opinions diverge on credential/bio slides: technical audiences often dislike them; some contexts (execs, clients, certain cultures) care a lot about background and trust.
Slides, structure, and storytelling
- Strong emphasis on presentations as stories: conflict → tension → resolution; hero’s journey patterns adapt well to “we had problem X, tried Y, finally did Z.”
- Several criticize dense bullet-point decks; suggested alternatives include:
- Minimal text, emphasis on visuals and live explanation.
- Assertion–evidence style: full-sentence claim plus supporting image.
- Animating content so slides build gradually, avoiding “walls of text.”
- Tension between decks as live aids vs. standalone documents; ideal is separate versions, but few have time.
Audience behavior and interruptions
- Programmers often start solving posed problems mentally (“nerd sniping”), which can distract from the talk.
- Exec audiences may derail BLUF-style summaries with detailed questions on later slides; coping strategies vary and frustration is common.
Meta-advice and skepticism
- Recurrent themes: know your audience, focus on value to them, practice a lot.
- Some dislike rigid formulas like “tell ’em what you’ll tell ’em…”, arguing they produce tedious, repetitive agendas; others say they help retention, especially in longer talks.