Every consulting engagement has a night like this: the readout is tomorrow morning, the steering committee expects a deck, the analysis is done, the interviews are synthesized, the recommendations are formed, but the slides are not built yet. It’s 11pm, and the temptation is to open PowerPoint and start designing. This is the moment where content-first either holds or breaks. The discipline is to write the narrative before building the slides. Content before slides is easy to follow at 2pm; the test is whether it holds at 11pm.
Each step in the content-first sequence depends on the one before it
Before any slides exist, the consulting team writes the story of the deck in plain text. What does the audience need to understand? What decisions does this readout enable? What is the ask? The narrative is a half-page to a page that answers three questions:
- What is the situation and what does it mean
- What should the audience do about it
The two questions every deliverable must answer (i.e., what decision does this enable, and who needs to see it) are what the narrative makes explicit. Once the narrative exists, the deck structure follows from it. Each section serves a piece of the narrative. If the narrative has three components (e.g., current state assessment and recommended path forward), the deck has three sections. Sections that do not serve the narrative do not get built. Slide design happens last because the content determines the format. A slide communicating a single decision point looks different from one comparing three options; a dependency map needs a different layout than a stakeholder feedback summary. Format follows content, and content follows narrative.
Reversing the sequence optimizes for coverage instead of clarity
When someone opens PowerPoint first, the template becomes the thinking structure. The agenda slide goes first because it always goes first. The executive summary goes second because the template has one. Each section gets built in the order the template suggests, and the content fills the container rather than shaping it. The result is a deck that is complete on its own terms but misaligned with what the audience needs. The steering committee sits through forty slides when the decision they need to make is on slide thirty-two; the executive sponsor receives a comprehensive overview when what they needed was a focused recommendation with supporting evidence. A deck that covers every topic superficially is less useful than one that covers three topics with enough depth and clarity to enable a decision.
Thirty minutes of narrative saves hours of rework
At 11pm, writing the narrative first feels like a delay. The instinct says start building and refine as you go; the discipline says spend twenty minutes writing the narrative, ten minutes structuring the deck from it, then build the slides with a clear map of what each one needs to accomplish. That thirty-minute investment changes the next three hours. Without the narrative, the consulting team builds slides, realizes mid-deck that the story does not flow, rearranges sections, builds a new transition slide, discovers that the risk section belongs before the recommendation rather than after, and rebuilds. The rework consumes more time than the narrative would have taken. With the narrative, we build in sequence. Each slide has a defined purpose. The transitions work because the story was written before the structure was imposed; the deck gets built once rather than rebuilt twice. Content-first is a discipline that applies across the work we do: in intake documents, architecture diagrams, readout decks, and operating model documentation. The same thinking applies to critique before you create (testing the argument before polishing the slides) and to designing the closing slide hit that determines what people carry out of the room.
