Storyboarding
Drawing a proposed experience frame by frame, before anything is built, so that the moments you cannot draw reveal the parts of the idea that do not work.
A deck lets you write “and then it intelligently surfaces the right answer.” A storyboard makes you draw it. The frame you cannot draw is the idea you do not have.
The visual
Five frames. The sequence halts at the one nobody could draw. That halt is the method.
Three frames build the story. The fourth — the frame nobody could draw — is empty. The fifth frame shows the outcome, dimmed and unreachable until the gap is crossed. The gap is not a failure of the exercise. It is the finding.
What it is
If you cannot draw the frame, you do not have the idea.
Storyboarding is the practice of drawing a proposed experience frame by frame — not to produce a beautiful illustration, but to force the concept into specific, sequential decisions. You choose what happens in each frame. You draw who is involved, what they are doing, what they see, and what the product does. The act of drawing is the discipline: it is much harder to claim a mechanism exists when you have to show it.
The core teaching is not about drawing. It is about what happens when you cannot draw a frame. A team pitching a meal-planning app can write “the app intelligently suggests a recipe based on what the user has at home” in a slide, in a document, in a brief. None of those formats asks the team to draw how the app knows what is in the fridge. A storyboard does. And at the moment they try to draw frame four — the mechanism by which the app knows the fridge contents — they discover they have three different assumptions about it, none of which they have tested.
That moment of discovery is the method. The gap in the storyboard is not a problem with the exercise. It is the exercise doing its job. A story that cannot get from frame three to frame five is a concept that has not been thought through. Storyboarding exists to find that gap before the build begins — not after sprint four.
Try it
Click each frame. Find what it assumes. Try to fill the gap.
Every frame contains an assumption. The first two are probably safe. The third is less safe than it looks. When you try to fill the gap, you will find that every attempt names a new assumption rather than closing the old one. That is not a failure of the exercise.
When to deploy it
Use it before you build anything — especially before you are confident the concept works.
Use it when
- →The team can describe the concept but has not drawn what the user actually does in each moment of it.
- →A mechanism in the concept has been named but not designed — anything described with "automatically," "intelligently," or "seamlessly."
- →Different people in the room hold different mental models of the experience, and you need a shared, honest sequence to compare them.
- →You are about to begin building and want to confirm that every frame of the concept is specific enough to be built.
Do not lean on it when
- ×You want to generate many concept directions quickly — that is Crazy 8s, which produces breadth; storyboarding asks one concept to go deep.
- ×The concept is at the level of a whole journey across many sessions and touchpoints — that is Journey Mapping; storyboarding works best on a single, specific scenario.
- ×The purpose is communication or presentation rather than discovery. A storyboard used to sell an idea rather than test it loses its honesty.
- ×The team is drawing frames they cannot yet draw — and labelling them rather than naming the gap. A storyboard filled with labels is a slide deck.
The honest limit
Storyboarding finds gaps; it does not close them. The gap names a question the team cannot yet answer. That question still needs an answer — from concept testing, from a prototype, from a research session. Finding the gap is the first job. Crossing it is the next one.
How it works
Draw the sequence. Name the assumptions. Find the frame you cannot draw.
Choose a specific scenario, not a typical user
A storyboard begins with one person, in one situation, doing one thing. Not "a user wants to plan meals" — "a parent, opening the fridge at 5pm on a Wednesday, with no idea what to cook." The more specific the scenario, the harder it is to hide behind generality in later frames.
Agree on the beginning and end before drawing the middle
What is the first frame? What does the experience look like before the concept exists? What is the last frame? What does success look like for this person? Fix both ends first. The frames in between are the claim your concept is making.
Draw rough — the quality of the drawing is not the point
Stick figures, rough rectangles, gestural marks. The drawing does not need to be understood by anyone outside the room. It needs to be honest. A sophisticated illustration can mask the same gap that a rough sketch exposes immediately. Do not let drawing skill become drawing confidence.
Name what each frame shows — and what it assumes
For each frame: what does the user see? What does the user do? What does the product do? And what has to be true for this frame to work? Writing the assumption explicitly is the step teams skip, and it is where the method's value lives.
Find the frame nobody can draw
At some point in the sequence, a frame will resist being drawn. Someone will reach for a label instead — "the app intelligently…", "the system automatically…". Stop there. That is the gap. Mark it, name it, and treat it as the most important frame in the board. Everything before it builds toward it; everything after it depends on it.
Let the gap determine what comes next
The gap is not the end of the exercise — it is the beginning of the next one. What question does the gap name? Who can answer it? Does crossing the gap require a research session, a prototype, a technical spike? The storyboard gives you the question; the answer comes from whatever comes next.
Best practices
A storyboard with no gaps is a slide deck. A gap is a finding, not a failure.
When it goes well
The mistakes
Drawing what the product does instead of what the user does.
A storyboard full of product screens and UI wireframes is a prototype in disguise. The sequence should follow the person, not the interface. What is the user doing, and why, in each frame?
Labelling the gap instead of naming it.
"Frame 4: App suggests recipe." That is a label, not a frame. A frame shows what the person sees and does. The label hides the question. Name the question instead: what must be true for this frame to exist?
Treating the finished storyboard as the output.
The output is the gap. If the team leaves the session with a complete storyboard and no named question, the method has been used as a presentation tool rather than a discovery tool.
Skipping the assumptions.
Every frame contains a claim. Not writing the claim down means it will be carried forward implicitly — unexamined — into the prototype and the build. The assumption that was never written is always the one that breaks last and costs most.
Drawing only one version.
If the concept has a gap, there may be several ways to cross it. Drawing two or three versions of the gap frame — each with a different mechanism — reveals that each version is actually a different product. That is useful information.
Logistics
Everyone draws. Small enough that the gap is felt by everyone in the room.
Time
One to two hours for a first-pass sequence. An afternoon to walk it with the team, name the assumptions, and find the gap. Revisited when the concept changes, not on a calendar.
Who
3–8 people. Small enough that everyone draws — if someone is watching rather than drawing, they are observing another team’s assumptions rather than examining their own. The gap is most useful when it is felt collectively: the moment the room falls silent at frame four matters.
Approach
Physical first: large paper, markers, rough drawings pinned to a wall. Digital tools add friction and tempt teams toward visual quality. Keep the drawings rough. The gap is easier to find when the board looks unfinished.
AI and this method
AI eliminates the drawing barrier. It does not eliminate the gap — it hides it.
Toggle between modes. AI as author generates a complete storyboard quickly — and illustrates the gap with a label rather than a frame. AI as adversary reads your storyboard and finds the label faster than any workshop can. One of these uses is valuable.
In practice
A meal-planning app team draws five frames. The fourth one stops the room.
Tab A shows the storyboard working — the team finds the gap, names it precisely, and changes the concept before a single line of code is written. Tab B shows what happens when AI generates the storyboard instead, and the gap is illustrated rather than crossed.
SCENARIO
A team is storyboarding a meal-planning app that suggests recipes based on what ingredients the user has at home.
01
The team draws the sequence
Meal-planning app. Five frames: parent opens fridge, opens app, sees suggestions, adds ingredients to list, plans the week. The first three frames draw quickly. Everyone agrees on what the user sees.
02
Frame four stops the room
How does the app know which ingredients the user has? Someone suggests typing them in. Someone else says: do we actually think people do that? A third person says: we've been assuming they do. Nobody draws the frame. There is silence.
03
The gap reveals the concept
The real product question is now visible: the entire value proposition rests on knowing what the user has at home. The storyboard did not fail. It worked. Three mechanisms are proposed: manual entry, receipt scanning, pantry photo. Each is a different product.
04
The concept changes before anything is built
The team agrees on receipt scanning as the lowest-friction option. They draw a new frame four. The storyboard now has six frames, not five, and the gap is crossed with a specific behaviour. Sprint one builds that behaviour.
The storyboard worked because the team could not draw frame four. In two hours they discovered a product decision that would have cost months to find in a build. The gap was the method doing its job.
Where it fits in the frameworks
Storyboarding appears wherever a framework needs a concept to become specific.
On Wednesday of a Design Sprint, the team sketches solutions individually. Storyboarding is not a named step, but the act of drawing a solution in sequential frames is the Wednesday motion. The critical discipline is the same: any frame that says the product "intelligently" does something must be made concrete before Thursday's prototype can be built. The gap that appears in a Wednesday sketch is a signal, not a problem — it names what the prototype needs to test.
Storyboarding sits at the junction of Ideate and Prototype. In Ideation it is generative — drawing multiple concept sequences quickly exposes which directions survive contact with a real experience. In Prototype it becomes evaluative: the frame nobody can draw signals which concept has not reached a specific enough idea to build. The method's job changes at the boundary, but the logic is the same in both phases.
In the Develop phase, storyboarding is how rough concepts become concrete enough to test. The sequence forces specificity about what the user actually does — not what they might do, and not what the product "magically" enables. The gap in the storyboard is the signal that development has not yet reached a specific enough idea. You cannot develop what you cannot draw.
Before a build begins, a storyboard is a narrative check on the hypothesis. The frame nobody can draw is the frame the build is going to be wrong about. Drawing the sequence before sprint planning gives the team a visible map of what they are claiming to make — and makes the untested mechanisms visible before they are embedded in architecture.
Related methods
Methods that work before, alongside, or after the storyboard — including the rest of the Ideation & Prototyping group.
Journey Mapping traces the full end-to-end experience across all touchpoints and emotional states. Storyboarding focuses on a single scenario — usually a specific moment of value — and asks whether the concept for that moment holds together. Use the map to find the moment worth storyboarding; use the storyboard to find out whether the concept for that moment actually works. They answer different questions at different scales.
Storyboarding and rapid prototyping are two ends of the same intent: making the concept concrete before it is built. The storyboard is earlier — it is the test of whether the concept is worth prototyping. The gap in the storyboard identifies what the prototype needs to prove. Build the prototype to answer the question the gap named, not to bring the storyboard to life.
Storyboarding surfaces assumptions by forcing you to draw them. Assumption Mapping takes the assumptions the storyboard revealed — especially those in the gap — and sorts them by importance and uncertainty. The storyboard is the excavation; Assumption Mapping is the triage. Use them in sequence: the storyboard to find what you are assuming, and Assumption Mapping to decide which assumption to test first.
Crazy 8s generates many rough concept directions quickly; storyboarding takes one of those directions and asks whether it holds together in sequence. They are close in time: sketch the breadth with Crazy 8s, then follow the most promising direction into a storyboard to find out whether the concept survives the full experience. The frame nobody can draw in the storyboard is often the frame that would have been the decisive eighth sketch.
When the storyboard exposes a specific gap, concept testing is the method that fills it. You cannot draw the frame because you do not know what the user will do — or whether the mechanism you have in mind will work. Concept testing finds out. The storyboard names the question precisely enough to test; concept testing runs the experiment. Together they move from "we do not know" to "we tested it."
Sources and further reading
The books and practices behind the method.
Knapp, J., Zeratsky, J., & Kowitz, B. (2016). Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days. Simon & Schuster.
The Design Sprint book describes the Wednesday sketching session in detail — the closest equivalent to formal storyboarding in any widely used framework. The logic of drawing before prototyping is core to the Sprint methodology.
Buxton, B. (2007). Sketching User Experiences. Morgan Kaufmann.
The essential text on the value of rough, honest sketching over polished illustration in the early stages of design. The argument for why drawing quality should not track confidence applies directly to the storyboard discipline.
Goodwin, K. (2009). Designing for the Digital Age. Wiley.
Covers scenario-based design and the use of storyboards as tools for testing conceptual coherence — particularly the gap between what a product is supposed to do and what it can actually be designed to do.
Ideation & Prototyping — Method 6 of 6
40 methods across 6 stage groups