Slide Deck Builder

A slide deck is an argument, not a filing cabinet. Every structural choice either advances or dilutes the central point. Build the narrative before touching any slide.

Build the spine first

Before writing a single slide, answer three questions in writing:

1. What does the audience believe now?
2. What should they believe or do after?
3. What is the single most important thing standing between those two states?

That gap is the deck's job. Every slide serves the journey across it. A deck that does not answer all three is not ready to build.

Narrative arc

Default structure for a decision-driving deck:

• Situation - shared context the audience already holds as true
• Complication - what changed or what is broken; the tension
• Resolution - the proposed path forward
• Proof - evidence the resolution works
• Ask - the specific decision or action requested

Never start with the ask. Never bury the complication in slide 9.

Size the deck to the meeting: budget roughly 2 minutes of talk time per slide, so a 30-minute decision meeting supports 10-15 slides - anything past that is appendix material.

One idea per slide

If a slide requires a sub-bullet to be understood, it has two ideas. Split it. The test: cover the body and read only the headline. If the point still lands, the slide is right. If the body is doing the work, the headline is wrong.

Do not use slides as documents. If content requires more than 40 words to be understood, it belongs in an appendix or a leave-behind - not on a live slide.

Headlines as takeaways

Every headline should be a complete, opinionated sentence - not a topic label - and short enough to read in one glance (about 12 words is the ceiling).

• Wrong: 'Market Analysis'
• Right: 'The market is growing 3x faster than our current capacity'

A reader who only reads headlines should get the whole argument. If the headlines form a logical chain, the deck is structurally sound.

Worked example: the headline chain

The fastest structural check is reading only the headlines aloud.

Bad (topic labels - no argument):

1. Background
2. Market Overview
3. Our Product
4. Financials
5. Next Steps

Good (each headline a claim, and the sequence is the argument):

1. Support tickets doubled in two quarters while headcount stayed flat
2. Manual triage is the bottleneck: 60% of agent time goes to routing, not solving
3. Auto-triage cuts routing time to near zero in the three teams that piloted it
4. Rolling it out company-wide costs $200k and pays back in under two quarters
5. We're asking for approval to start the rollout next sprint

Read the bad chain and you learn nothing. Read the good chain and you could make the decision without seeing a single slide body - which is exactly the standard.

Slides to audit before finalizing

• Slide 1 (title): Does it name the audience's problem, not the presenter's topic?
• Agenda slide: Cut it unless the deck is longer than 20 slides or the audience is unfamiliar with each other.
• 'About us' slide: Move it to the appendix unless credibility is genuinely in question.
• Last slide: The final slide should show the ask, not 'Thank You'.

Quality bar

• The three spine questions are answered in writing before slide one exists.
• Reading only the headlines, in order, delivers the complete argument.
• No live slide exceeds one idea or 40 words of body.
• The final slide is the ask, stated as a specific decision or action.
• The slide count fits the meeting length at ~2 minutes per slide.

Do NOT

• Do not open the slide tool before the headline chain is written - building slides first locks in a structure the argument then has to fight.
• Do not paste dense tables or full paragraphs from the source document onto live slides; excerpt the one number or claim that matters and move the rest to the appendix.
• Do not soften or hide the ask to seem less presumptuous - an audience that cannot tell what you want will decide nothing.
• Do not write bullets you intend to read aloud verbatim; the slide supports the talk, it is not the script.
• Do not let appendix content creep into the main flow "just in case someone asks" - that is what the appendix is for.
• Do not reuse a deck built for one audience on another; the spine questions have different answers, so the deck must too.

Escape hatches

For conference talks, lead with the resolution - audiences came to learn, not to be convinced. For investor decks, follow the problem / solution / traction / team / ask sequence. For board updates, lead with the decision needed; context comes after.