AI will hand you twenty slides before you’ve finished reading this sentence. It won’t hand you an argument.
That’s the strange position presentations are in now. Building the thing used to be the slow part. It isn’t any more, which means the only part still worth anything is the part nearly everyone skips: working out what the presentation is for, what gets said, in what order, and how many slides it takes to land.
That’s a presentation storyboard. A rough map of a deck that doesn’t exist yet.
It takes an afternoon, a pencil and a fair amount of arguing. And here’s the thing nobody selling you an AI deck generator will mention: AI is genuinely good at this stage. Much better than it is at the stage everyone’s using it for.
What a presentation storyboard is (and what it isn’t)
A presentation storyboard is a rough, sequential map of every slide in a deck, showing what each slide has to say and what job it does, drawn up before a single slide is designed.
It’s boxes. That’s it. One box per slide or per idea, in a row, with a scrawled headline in each and arrows between the ones that connect. Films get storyboarded. Comics get storyboarded. Adverts get storyboarded. Presentations, for reasons that have never made sense to us, mostly don’t.
What it isn’t: a first draft in PowerPoint. The moment you’re in the slide deck you’re thinking in one direction, top to bottom, slide 1 to slide 40, and you’ve quietly stopped asking whether slide 12 should exist at all. It also isn’t a bullet-point outline in a Word document. An outline is a list. A storyboard is a shape, and you can see the shape is wrong from across the room.
The storyboard isn’t the story
This is the distinction almost every guide on this topic gets wrong, and it matters.
The storyboard is the architecture. How many slides, what’s said where, what each section is doing in service of the outcome. It’s a structural job with a defensible right answer.
The story is what happens afterwards: the tension, the pacing, the language, the visual idea, the moment where the room goes quiet. That’s the craft, and it can’t start until the architecture is standing up.
In our discovery workshops the storyboard comes first, on the wall, before any of the storytelling work begins. Get that order the wrong way round and you end up doing beautiful narrative work on a structure that was never going to hold your outcome.
You don’t need a storyboard for every deck
We won’t pretend otherwise. Storyboarding is a from-scratch tool.
If you’re updating last quarter’s board pack, or you’ve been handed a template and a content doc and the argument is already made, skip it. Ten minutes on fire safety procedures does not require a wall of post-its.
Where it earns its keep is the blank page. New pitch, new proposition, an open brief, a keynote where nobody has yet agreed what the point is. That’s where an afternoon of boxes saves a fortnight of building the wrong thing.
Start with the outcome, and don’t take the first answer
Before any boxes, one sentence at the top of the page: what do you want the people in that room to do?
Almost everyone’s first answer is limp. “Raise awareness.” “Build credibility.” “Get them excited about the vision.” None of those are outcomes, because none of them describe anything a human being could actually go and do on Thursday.
So we keep digging. That’s what we mean by positive friction — asking the uncomfortable follow-up question until the belief underneath the brief falls over. Awareness of what, held by whom, so that what happens next? Usually about four questions in, someone in the room says the real thing out loud. Sign off the budget. Choose us over the incumbent. Stop the project they’ve already started.
Write that sentence down. Every box you draw afterwards either serves it or gets binned. It also means you know roughly what your final slide is before you’ve drawn your first, which feels backwards for about five minutes and then feels obvious.
How to build a presentation storyboard in six steps
- Write the outcome at the top. One sentence, active verb, names the thing you want the audience to do. If it doesn’t survive being read aloud, it isn’t finished.
- Dump every headline you’ve got, in no order at all. Not sentences. Headlines. The point of each idea in eight words or fewer. Don’t edit while you’re dumping, and don’t worry about sequence.
- Give each idea its own box. One box, one idea. Some will later need three slides, some will merge into one. Not your problem yet.
- Work backwards from the ending. You know the last slide, because you wrote the outcome. Ask what someone would have to believe immediately before that to say yes, then what they’d have to believe before that. Keep going until you hit the beginning.
- Put a slide count on it. Now count the boxes and be honest about how many slides each one needs. This is the number that determines how long the deck takes to build, how long it takes to deliver, and what it costs.
- Reorder until it argues. Read only the headlines, in order, out loud. If the argument holds up with nothing but the headlines, you have a storyboard. If it doesn’t, the design was never going to rescue it.
Post-it notes beat a single sheet of paper here, for the obvious reason: step six involves moving things, and a sheet of paper will not let you.
Where AI earns its place, and it isn’t the slides
Our position, plainly: AI will do a far better job of building your storyboard than it will of building your presentation.
That’s not the received wisdom, and the received wisdom is wrong. Structure is a logic problem. Sequence, dependency, gaps in an argument, the question a sceptic asks on slide 14 — these are exactly the things a language model is good at, because there’s a defensible right answer and it’s checkable against your outcome. Slide design isn’t like that. Taste, restraint, one specific idea landing in one specific room: that’s where the generated deck falls apart, which is why AI decks look finished and say nothing.
Microsoft Copilot, Gamma and the rest are all pointed at the wrong end of the job. Point them at the other end.
What to hand it
- Your messy headline dump, with the outcome, asked to propose three different running orders and explain the logic of each
- Your storyboard, asked where the argument has a hole in it
- Your storyboard, asked what a sceptical CFO, procurement lead or technical buyer would push back on, and where
- A section that isn’t working, asked what’s missing between box four and box five
What to keep it away from
- Generating the deck. One prompt, twenty slides, nothing said.
- Choosing your outcome. It’ll happily accept “raise awareness” and build you forty slides on top of it.
- Writing your headlines. It’ll produce eight competent ones and not a single memorable one.
Use it as the sharp colleague who asks why slide nine is there. Not as the designer.
Paper for the mess, screen for the order
The original version of this post said keep storyboarding strictly offline. We’d now split it.
The divergent, messy, half-formed bit stays on paper. There’s real evidence behind this: a 2024 high-density EEG study led by Audrey van der Meer at NTNU, published in Frontiers in Psychology, found that handwriting produced widespread brain connectivity that typing on a keyboard didn’t. Something about the drag of a pen keeps ideas forming while you’re mid-thought. Post-its, a marker, a wall.
The convergent bit — ordering, pressure-testing, spotting the gap — is where the screen and the model earn their place. Mess by hand, order by machine.
A storyboard is also how you get a straight quote
Here’s the commercially useful part that nobody mentions.
Presentation design is priced on slide count and complexity. Turn up to an agency with “we need a pitch deck, not sure how long” and nobody can give you a real number, because nobody yet knows whether it’s 18 slides or 60. You’ll get a range, or a quote after discovery.
That’s not a problem — helping you do the structural thinking is a large part of what a discovery workshop is for, and we quote properly once it’s done. But if you want a firm price before you commit, a storyboard is the thing that gets you one. It converts a vague ambition into a countable object.
The slides were never the hard part
They’re certainly not the hard part now. A machine can produce a competent-looking forty slides while you make a coffee, and it will say nothing, because nobody told it what the room is supposed to do afterwards.
That’s still your job. It’s an afternoon with a pencil, some post-its and one uncomfortable question asked four times.
We don’t build slides, we build presentation experiences. And every one of them starts as a wall of boxes.
Presentation storyboard FAQs
What is a presentation storyboard?
A presentation storyboard is a rough, sequential map of a deck made before any slide is designed. Each box represents one slide or one idea, carries the headline for that slide, and shows what job it does in the overall argument. It’s the presentation equivalent of the storyboards used for films and adverts.
How do you storyboard a PowerPoint presentation?
Write your outcome in one sentence, dump every headline you have with no regard for order, give each idea a box or a post-it, work backwards from the ending to find what the audience has to believe at each stage, put a slide count against each box, then reorder until the headlines alone make the argument. Only then open PowerPoint.
Do you need a storyboard for every presentation?
No. Storyboarding is a from-scratch tool. If you’re updating an existing deck, working to a template, or the argument is already settled, go straight to building. Use a storyboard when the page is blank, the brief is open, or nobody has agreed what the presentation is actually for.
Can AI create a presentation storyboard?
Yes, and it’s better at this than at generating finished slides. Structure is a logic problem: sequencing, dependencies and gaps in an argument are all things a language model handles well. Give it your headlines and your outcome and ask for running orders and holes in the logic. Don’t ask it to choose the outcome or write the headlines.
What’s the difference between a storyboard and a presentation outline?
An outline is a list, read top to bottom. A storyboard is a shape, seen all at once. That difference matters because most structural problems are visible spatially and invisible sequentially: you can see that the middle of a storyboard sags from across the room, and you’ll never spot it scrolling a bulleted list.
How many slides should a presentation have?
There’s no universal number, and any guide that gives you one is guessing. The count falls out of the storyboard: one box per idea, then an honest assessment of how many slides each idea needs to land. Work it out before you build, because it’s also what determines how long the deck takes and what it costs.
