Storyboard a Presentation Before You Build a Single Slide

Forty slides on Thursday, thirty in the bin on Friday

Picture a strategy analyst who has spent eight days building a 40-slide deck on whether to enter a new region. The charts are clean. The appendix is thorough. On Thursday evening her director flips through it in four minutes, reading only the titles. “What are you recommending?” It is on slide 31. “And the board will ask about the partner option first. Where is that?” It is not there, because nobody asked for it. Thirty slides go in the bin.

Nothing she built was wrong. The order, the question and one missing option were wrong, and all three were visible in the titles. She could have seen them on day one, on a single sheet of paper, before a single chart existed.

Storyboarding a presentation means writing the deck as a sequence of slide titles, each a full sentence stating what that slide will prove, with a rough sketch of the evidence beneath it, before opening slide software. You read the titles in order to test the argument, mark which evidence you do not yet have, and show the board to the decider for ten minutes. Then you build.

The thesis of this page is simple. Sentences are cheap to move and slides are not. Every hour spent on a chart is an hour of attachment to a slide that may not belong in the deck. A storyboard makes the argument cheap to change at the moment changing it matters most.

A storyboard is the cheapest draft of the deck you will ever throw away.

What a storyboard is, and what to call it

The presentation design firm Duarte describes how its own team “sketched out slides–one per sticky note–to plan out the flow of the story,” chose sticky notes because they are “small, easily movable and readily recyclable,” and used the method to refine the message and “get group buy-in before heading to the computer to wrangle your slides” ¹. That is the whole idea: a cheap, movable unit per slide, arranged until the order works.

Strategy teams add one discipline: each note carries a sentence that states a finding, not a topic. Barbara Minto's pyramid principle is the logic underneath. Thinking is easy for a reader to grasp when the ideas are organized “as a pyramid under a single point,” and her textbook explains “the entire thinking process that should precede writing” ². A storyboard is that thinking, laid out left to right. Michael Alley's assertion-evidence approach supplies the slide unit: a sentence headline stating the main message, supported by visual evidence ³.

Consultants often call a storyboard of titles and blank or sketched slides a ghost deck. The term is widespread in practitioner guides, and it is often credited to one consulting firm or another. We could not find a primary source for its origin, so treat any story about who invented it as folklore. The practice matters more than the name.

The template

Two parts: a frame you fill in first, and the board itself. The frame is five lines. Do not start the board until all five are written.

Work on a wall with sticky notes, on a whiteboard, or in a document table. The medium matters less than one rule: no slide software until the board passes the tests below. The tool on this page assembles the frame and the title row into a document you can share.

Build the board in an hour

1. Write the frameTen minutes. If you cannot write the answer, write your best guess and mark it as a hypothesis. A storyboard built around a guess is still faster than one built around nothing; the hypothesis-driven problem solving page explains why.
2. Write the three or four reasonsUnder the answer, write the few claims that, if true, would make the answer right. These become section openers. Each states what its slides mean, not that the section exists.
3. Write the slide titles beneath each reasonTwo to five titles per reason, each a sentence that states a finding at the scale your evidence supports. Add the opening: what the decider already knows, what has changed, and the question it raises.
4. Sketch the evidenceUnder each title, draw the chart you expect: axes, rough shape, source. If you cannot imagine the chart that would prove the title, the title is not ready.
5. Mark the statusHave, need or hypothesis. Count the needs. They are your work plan, and the hypotheses are what could change the answer.
6. Read the titles aloudIn order, without the sketches. They should sound like a short memo. Where you stumble, the logic has a gap.
7. Show it to the decider, or the decider's closest proxyTen minutes, board only. Ask two questions: is this the question you need answered, and what would you ask first? Then reorder.

A filled-in storyboard

Read the titles alone and the argument holds: recommendation, the problem, why it is not the same everywhere, the case for refits, a cost of closing that is easy to miss, the option rejected, the risk and the ask. Four slides are marked “need.” Two are hypotheses. That is the work plan for the next two weeks, and title 6 is the one to start on, because if the online loss is much larger than a fifth, the answer changes.

Notice title 7. In the opening scene, the missing option sank the deck. Here it has its own slide before anyone asks.

Reading the board: five tests

1. The paragraph test. Titles read aloud, in order, form a paragraph that makes the case. If they read as a list of topics, rewrite them as claims. The action title drill is good practice.
2. The swap test. Could you swap two slides without anyone noticing? If so, the sequence is not doing any work. Each title should follow from the one before or answer a question it raises.
3. The scale test. Does each title claim exactly what its evidence sketch could show? “Customers prefer us” over a chart of one survey question is an overclaim that will be caught in the meeting.
4. The proportion test. Count the slides that describe the situation versus those that argue for the answer. If background is more than a quarter of the main body, the deck is a report.
5. The fear test. Write down the question you most dread. Find the slide that answers it. If there is none, add it, or know which backup slide holds it.

Run these tests on the board, not the finished deck. Once the slides exist, every test that fails costs a day. The strategy deck checklist covers the inspection to run later, when the slides are built.

The case against storyboarding first

The strongest objection is that a storyboard writes the conclusion before the analysis. Put a recommendation on slide 1 in week one, and the team will spend three weeks finding evidence for it. The board becomes a contract, and analysts learn that a chart which contradicts a title is a problem to manage rather than a finding.

That risk is real, and it is a reason to build the board in a particular way, not a reason to skip it. Three habits keep a storyboard honest.

• Mark hypotheses as hypotheses. A title in the “hypothesis” column is a claim you are testing, and everyone on the team should know it can flip.
• Write the slide that would kill the answer. For each reason, add one note: the result that would prove it wrong. If title 6 in the example came back at half the online sales instead of a fifth, closing would look worse. Knowing that in advance makes the result a finding, not an embarrassment.
• Redraw the board when the evidence moves. A board that has not changed in three weeks of analysis means either the first guess was perfect or nobody is looking. The second is more common.

A softer objection is that some work is exploratory: there is no answer yet, only a question. Storyboard anyway, with the question at the top and the titles phrased as the claims you expect to test. The board then shows which analyses could change the decision and which would only add pages. Without one, exploratory work tends to produce the 40-slide deck from the opening, in which everything is true and nothing is decided.

Storyboards as a team's work plan

On a team, the board does a second job. Each “need” note is an assignment with an owner and a date. Put the board on a wall or a shared page and run the daily check-in from it: which titles moved from hypothesis to have, which flipped, which are stuck. The board becomes the plan, and the deck becomes the board's last state.

• Senior people review the board, not the slides. A director's hour is worth most in week one, on titles. Spent in the last week on formatting, it buys almost nothing.
• Assign titles, not slides. An analyst given “slide 14” builds a slide. An analyst given “In 8 of the 22 catchments, core customers are a growing share” knows what would count as an answer, and what would count as a surprise.
• Keep one board. Parallel versions drift. One owner edits the titles; everyone else proposes changes.
• Watch for the slide factory. If the team's output is measured in slides produced, the board will fill with slides nobody needs. Measure by titles proved or disproved.

Before you open the slide software

• The frame's five lines are written, including an answer, even a provisional one.
• Every note carries a sentence that could be wrong.
• The titles, read aloud, make the case in under two minutes.
• Rejected options and the biggest risk have their own titles.
• Every title has an evidence sketch and a status.
• The decider, or their closest proxy, has seen the board and said what they would ask first.

The analyst in the opening did not lack skill or effort. She lacked a single sheet of paper on day one. Write the deck as sentences first, while every sentence is still free to move. The slides will take the same time to build. They will just be the right ones.

Questions

What is a presentation storyboard?

A presentation storyboard is the deck written as a sequence of slide titles, each a full sentence stating what that slide will prove, with a rough sketch of the evidence underneath, made before any slides are built. It lets you test the argument, find missing evidence and agree the question with the decider while changes are still cheap.

What is a ghost deck?

A ghost deck is consulting slang for a storyboard built as slides: action titles with blank or sketched bodies, laid out in order before the analysis is finished. The term is widely used in practitioner guides, but its origin is not documented in any primary source we found, so stories about who invented it are best treated as folklore.

How do you storyboard a presentation?

Write the frame first: the decider, the question, your answer, the ask and the time slot. List the three or four reasons that would make the answer right. Under each, write slide titles as claims and sketch the chart each needs. Mark each as have, need or hypothesis, read the titles aloud, and show the board to the decider before building.

Doesn't storyboarding first bias the analysis?

It can, if the board is treated as a contract. Keep it honest by marking unproven titles as hypotheses, writing down the result that would overturn each reason, and redrawing the board when the evidence moves. A storyboard that never changes during the analysis is a warning sign.

Where to go next

• The Pyramid Principle for Strategists
• Strategy Deck Checklist
• Executive Summary Template
• Strategy Narrative Builder
• Slide and presentation tools for strategy teams