Template first, content second (usually)

The argument for template-first is partly about productivity but more about optionality. When you build inside a template from the beginning, you have something presentable at every moment. If the deadline moves forward three days, you have a usable artefact. If you're interrupted in the middle and need to show progress, you can. If your collaborator needs to review the structure before the content is complete, they can. Content-first authoring, by contrast, requires a long final sprint to apply formatting, and the sprint collapses if anything disrupts the timeline.

The productivity numbers

When teams have measured time-to-first-draft and total-time-to-final for template-first versus content-first approaches, the template-first wins by about 20% on both metrics. This is a consistent finding across the engagements I've been involved in. The gain is not massive, but it's large enough to compound meaningfully over a year of presentations. For a senior manager producing a serious presentation every two weeks, that's the equivalent of a full working week recovered annually. It's not the kind of productivity gain that changes lives, but it's real and it's easy to capture by adopting the template-first habit.

The efficiency comes from avoiding rework. When you write content first and format second, you often discover that your content doesn't fit the shape you committed to - ideas overflow slides, diagrams don't render at the right size, the structural hierarchy you wrote in prose doesn't map cleanly to a slide deck's left-to-right flow. The formatting pass becomes an editing pass, and the editing pass is where the time goes. Template-first catches these mismatches early, when fixing them is cheap.

The thinking cost

There is a genuine counter-argument that deserves serious consideration. Template-first presentations can let the template dictate the argument rather than the argument dictating the template. The rigid grid of a slide deck imposes a structure - problem, solution, proof, ask - that most business arguments fit reasonably but that some genuinely don't. Forcing a nuanced or non-linear argument into the standard deck structure flattens it, and the nuance can be lost. The best practitioners notice when this is happening and break the template when the argument requires; the weaker ones let the template shape thinking they should be shaping independently.

The middle path that I've settled on is template-first for presentations with well-understood structure (regular status reviews, project updates, investment requests), and content-first for presentations with complex arguments (strategy shifts, novel recommendations, multi-dimensional tradeoff analyses). The first category is maybe 80% of the presentations a senior person gives. The second category is where reputations are made, and it rewards the extra authoring cost of content-first thinking.

The tool question

The tool you use really doesn't matter much. The debates about PowerPoint versus Keynote versus Figma versus Miro versus Lucidchart are mostly aesthetic preferences that persist because decision-makers enjoy having them. The structural discipline - template first, maintain presentability throughout, end with a short polish pass - works in any tool. The best case against PowerPoint specifically is its strong structural bias toward bullet-point thinking; the best case for Figma specifically is its structural bias toward visual-first thinking. For most business presentations, either is fine. The habits you bring to the tool dominate the tool's influence on the output.

For teams working collaboratively on a document, the tool choice does start to matter - specifically around conflict-free simultaneous editing, comment workflows, and version control. Figma and Google Docs are strong here. PowerPoint and Keynote are weaker. This is the one dimension where tool choice has operational consequences beyond personal preference. For solo authoring, it's all preference. Stop relitigating it every quarter and pick one that feels good to work in.

The first slide should be the last thing you write.

The opening-slide discipline

The single most important discipline for any serious presentation is that the first slide should be the last thing you write. The opening line of a presentation is the conclusion of your thinking. You can't write a good opening before you've done the thinking, and the opening sets what the audience expects for the next thirty minutes. Writing it early locks you into a pitch before you've worked out the argument; writing it last means it captures what the argument actually turned out to say.

This discipline is independent of template-first or content-first. Both approaches benefit from writing the opening last. The discipline is also violated more often than I'd have expected - most of the decks I review as a reviewer have a first slide that contradicts or undersells the actual content. Writing the opening last prevents this. It's a five-minute habit that produces materially better presentations, and it compounds across a career in ways that few other single practices do.

The cultural caveat

One caveat worth naming: template-first presenting is an Anglo-consulting norm. French business culture, in particular, tends toward bespoke structures for serious presentations and views templates as lazy. The aesthetic expectation is higher and the production time is longer. This produces notably different deliverables for French versus Anglo engagements on similar problems, and it's neither better nor worse - it's a cultural preference with real consequences. If you're working in a French or French-influenced environment, the template-first advice will need recalibration. The underlying discipline (know your argument, don't let the form dictate the thinking) transfers. The specific template advice doesn't.

More generally, the formation of a good presentation has less to do with method and more to do with time. Great presentations are made by people who write their opening line last, use whatever structural approach gives them a presentable draft throughout, and spend enough time on review to notice their own argument-gaps. Everything else is details. The details vary by tool, culture, and domain. The underlying craft doesn't.