Write Slide Titles That Carry the Argument
Change nothing about your slides except the titles, and a deck that had to be presented becomes one that can be forwarded.
Here is a test that takes two minutes and tells you more about a deck than any design review. Open the outline view and read only the slide titles. If they form an argument you could follow without seeing a single slide, the deck is sound. If they read as a list of topics — "Background", "Market", "Results", "Next steps" — the deck only works with you standing next to it narrating.
Most business decks fail that test, and the fix is smaller than it sounds.
Label titles versus assertion titles
A **label title** names the subject of the slide. "Q3 Performance". "Customer Feedback". "Competitive Landscape".
An **assertion title** states what the slide shows. "Q3 revenue grew 14%, driven entirely by enterprise renewals". "Customers value reliability over new features, three to one". "We win on integration depth and lose on price".
Both sit above the same chart. The second does three things the first cannot:
- It tells a skim-reader the conclusion without decoding the visual.
- It commits you to having a point — which surfaces slides that do not have one.
- It survives forwarding. Most decks are read alone, not presented.
Why this makes the deck easier to build
The usual objection is that assertion titles take longer to write. In practice they save time, because they expose structural problems while they are still cheap to fix.
Try to write an assertion title and you will occasionally find you cannot — the slide has three charts making three different points, or none. That is not a titling problem, it is a slide problem, and you have found it before spending an hour on formatting.
Writing titles first also produces a better outline than an outline does. A list of assertions *is* the argument. Rearranging them is rearranging the logic, which is far easier in a text list than in a deck full of formatted slides.
What a good assertion title looks like
- **Specific rather than general.** "Churn is concentrated in accounts under £5k" beats "Churn analysis".
- **One clause.** If it needs a semicolon, the slide is doing two jobs.
- **Under about twelve words.** Long enough to say something, short enough to read at a glance from the back of the room.
- **Honest about strength.** "Early data suggests" is fine when that is what the data supports. Overclaiming in a title is the fastest way to lose a careful reader.
- **Free of jargon that hides the point.** The federal plain language guidelines are the clearest short reference here; the core advice — familiar words, active voice, one idea per sentence — applies directly to slide titles.
Where labels are still correct
This is a default, not a law. Section dividers should be labels: "Part Two: Operations" is doing navigation, not argument. Reference slides, appendices and data tables are fine with descriptive titles, because their job is to be findable rather than persuasive. Agenda slides are labels by definition.
The distinction is whether the slide is making a point or providing a resource. Points get assertions; resources get labels.
The order this suggests
Titles first, then structure, then content, then design. Concretely:
- Write the argument as a list of sentences — one per intended slide, in order.
- Read the list. If it does not persuade you, no amount of visual work will fix it.
- Cut and reorder until it does. This is the cheapest possible stage to do that.
- Only then decide what evidence each slide needs.
- Design last.
Most people invert this, building slides and titling them afterwards, which is why so many decks have a beautiful slide twelve that should not exist.
What it looks like in practice
Before:
- Background
- Our Approach
- Results
- Recommendations
After:
- Support costs rose 40% while headcount stayed flat
- Ticket volume is concentrated in three preventable issues
- Fixing onboarding removed two of the three
- Recommend funding the onboarding rebuild in Q1
Same four slides, same charts. The second version can be forwarded to someone who missed the meeting and still lands, which is a meaningful difference given how most decks are actually consumed.
Sequoia's guide to writing a business plan makes a similar point for fundraising specifically: the reader is pattern-matching at speed, and anything that makes them work to find the point costs you.
Our business presentation templates leave room for two-line titles for exactly this reason. A layout that only fits "Results" quietly pushes you back toward labels.
Start from a template
Every deck in the library is a native .pptx built on widely available fonts, so it looks the same on the machine that presents it.