Method
A visual sequence of frames that shows how a user experiences a concept over time.
Choose this if
This method works when visualizing end-to-end experience concepts before prototyping.
Pack = one session you can run now. Workspace = a saved thread for method choice, planning, and shareable outputs.
What Workspace helps you carry forward
Artifact preview
Storyboard artifact
Ideate · Low
Decide fit before you spend session time.
The core facilitation flow, with enough structure to run the method confidently in the room.
Standard setup for Mixed in remote delivery.
Total planned time: 90 min
What happens
Select user, context, and trigger event.
Facilitator does
Name the user, their goal, and the context in three sentences on the board before any sketching starts. Agree specifically on where the story begins and ends. If the room can't agree on scenario parameters, the storyboard will describe multiple different users simultaneously.
Participants do
Name a specific user — not a persona archetype, but someone you've actually spoken to or can picture clearly. Agree on the trigger that starts the story and the moment that ends it. Write both on the board before sketching begins so every frame is anchored to the same journey.
Output / signal of success
The group is aligned on the exact challenge, actor, or scope the rest of the method will serve.
Watch for
Scenario is too generic to anchor the story to a specific user situation.
Recovery tip
If the room can't agree on the scenario parameters, the storyboard will describe multiple different user situations simultaneously. Stop. Run a quick vote on three candidate scenarios and commit to one before sketching begins. A storyboard for one specific user situation is more useful than a blended story that doesn't represent anyone accurately.
What happens
Outline beginning, middle, and end moments.
Facilitator does
Identify the four to six moments in the experience where the user's state changes, a decision is made, or something could go right or wrong. Write these as text captions before sketching. Sequence disputes are worth resolving here, not during sketching.
Participants do
Name each moment from the user's perspective — what they're trying to do, what happens, and how they respond. Avoid naming moments from the product's perspective ("the system processes the request") rather than the user's ("the user waits, unsure if anything happened").
Output / signal of success
The shared structure now makes dependencies, relationships, or evidence gaps visible.
Watch for
Key moments list too many details and the storyboard becomes unwieldy.
Recovery tip
If the list of key moments grows beyond six, vote to keep only the ones where the user's state visibly changes or a decision is made. A transition frame with no user state change doesn't need its own sketch — it can be handled by a caption.
What happens
Create simple scene-by-scene storyboard.
Facilitator does
Keep sketches rough — stick figures and labeled boxes are sufficient. Remind participants that every frame needs a caption explaining the intent, not just the visual. If a sketch needs extensive explanation, it's carrying too much information in one frame.
Participants do
Sketch fast and captioned — one moment per frame, with a written caption underneath that explains what the user is experiencing or deciding. If you find yourself adding details that don't change the user's state or decision, those details belong in a separate annotation, not in the main frame.
Output / signal of success
Each frame has a rough visual and a written caption that explains the intent without requiring the author to narrate it. A person who wasn't in the session could read the storyboard and follow the story without explanation.
Watch for
Frames become so detailed that the overall narrative arc is lost.
Recovery tip
For frames that need extensive explanation, stop the author mid-narration. Say: "Let's add one line to the caption that captures what you just said." If the caption can't contain the frame's meaning in one sentence, the frame is carrying too much information and needs to be split into two.
What happens
Identify confusion points and refine flow.
Facilitator does
Walk the complete storyboard and ask: would a viewer who has never heard of this experience understand what is happening in each frame? Flag any frame that requires verbal explanation from the author. Identify narrative jumps and fill them with a bridging frame before closing.
Participants do
Walk the storyboard as a first-time viewer — not as someone who was in the room when it was made. At each frame, ask: would I understand what this person is experiencing if I hadn't heard the earlier discussion? Note any frames where you need the author's narration to make sense of it.
Output / signal of success
Storyboard artifact
Watch for
Review focuses on individual frames and misses whether the complete sequence tells a coherent story.
Recovery tip
Walk the complete storyboard as a group. At each transition between frames, ask: "Would a viewer understand how we got from this moment to the next?" If the answer is no, name the missing frame and add it before closing. Narrative jumps are the most common reason storyboards fail in stakeholder review.
Prepare the room, the evidence, and the working surface so the session can stay focused on synthesis.
A specific concept idea or solution direction to storyboard, and a defined user — who they are, what they're trying to accomplish, and what triggers the story. A storyboard without a specific user and situation produces a generic interaction narrative that could describe anyone and therefore describes no one convincingly.
Concept idea
Optional
Scenario prompt
Optional
Operational context note
Optional
Bring examples, pain points, or service evidence the room can point to quickly.
Storyboard frames
Optional
Markers or digital whiteboard
Optional
Remote facilitation choreography
Required
Pre-plan handoffs, breakout usage, and how people rejoin the main board.
Storyboard frames
Required
Markers or digital whiteboard
Required
Shared digital board with timer and voting
Required
Keep instructions and voting visible at all times.
Storyboard frame set
Keep the output usable, then use the recovery guidance when the room starts drifting.
What this does not produce
A storyboard produces a testable narrative about how a concept would work in context. It does not validate whether real users would experience the story as intended — that requires putting the storyboard in front of actual users. A storyboard that impresses in an internal review is a concept worth testing, not a concept worth building.
Failure mode
Why it happens
Designers and visual thinkers spend disproportionate time on the frames they find most interesting or challenging, producing some polished frames and some rough ones, with uneven time distribution across the story. The result is a storyboard with three beautifully detailed moments and five placeholder frames that don't carry the narrative.
Recover now
If this happens, enforce equal time per frame — set a timer for each one. If a participant has finished a frame early, ask them to move to the next one. A rough frame that advances the story is more valuable than a polished frame that stalls it.
Prevent next time
Next time, set the expectation before sketching begins: "Every frame gets the same amount of time. Rough and readable beats polished and incomplete."
Failure mode
Why it happens
Storyboards that focus on the product interaction — screen states, button presses, interface flows — often omit the user's environment, emotional state, and situational constraints. Without context, the story describes a user in a vacuum rather than a person in a real situation with real competing demands.
Recover now
If this happens, for each frame, ask: "Where is this person? What else is happening in their life at this moment?" Add one context detail to every frame — a location, a time pressure, a competing priority. Context makes the story credible and makes friction points more recognisable.
Prevent next time
Next time, in the scenario definition step, agree the user's context explicitly: "Our user is [doing X] in [location Y] when [trigger Z] happens." Write this on the board and keep it visible throughout sketching.
Failure mode
Why it happens
In the review step, participants comment on specific frames — "this doesn't look right," "the interface wouldn't work that way" — without checking whether the sequence as a whole tells a coherent story. The storyboard is reviewed frame by frame rather than as a narrative, and gaps between frames are missed.
Recover now
If this happens, read the complete storyboard aloud from beginning to end, describing each frame in one sentence. Any moment where the narration requires "and then somehow..." is a gap that needs a bridging frame.
Prevent next time
Next time, start the review by reading the complete sequence before any frame-level feedback. Narrative gaps can only be spotted when the story is read in full.
Change the shape of the session only after the fit and runbook are clear.
Standard variant for Mixed in remote delivery. Waypoint is adapting timing, facilitation emphasis, prep, and recovery guidance here, but the room still needs final tailoring to the exact stakes and participants.
Use this after you have checked the fit and know you want to carry the method forward.
The pack is the fastest way to run this now. Use the links below when you need prep, sharing, or a saved reference point.
Sources and references used in this method page.
Storyboarding in UX and service design contexts.
Sprint ideation and concepting patterns from GV.
Reviewed 2026-02-27 by Discovery Waypoint Editorial Team
Related playbooks
These pages translate recognizable external methods into Waypoint-native guidance so the team can borrow the useful part without importing the whole mythology.
Treat the sprint as a compact operating sequence for answering a specific risky question, not as a default wrapper for any ambiguous project.
Open when Risky concepts that need one compressed answer and fast user reaction.
Borrow the candor and critique discipline, but do not pretend you recreated Pixar’s Braintrust by putting senior creatives in one room with notes.
Open when Teams with promising work but weak critique quality and too much polite feedback.
A vivid stretch-ideation exercise that is useful when the room needs to break out of incremental thinking, but only if it quickly returns to what is plausibly worth building next.
Open when Teams stuck in timid incremental ideas that need permission to think bigger before narrowing back down.
