Storyboarding
Storyboarding: Sketch a sequence of 4β12 panels showing a user (or customer, or employee) moving through a scenario over time. Each panel shows one moment: what they're doing, thinking, and feeling. The narrative sequence reveals friction, delight, and gaps invisible in feature lists or process diagrams. Used to align teams, test concepts, and communicate design intent without building anything.
What Is Storyboarding?β
Storyboarding was invented at Walt Disney Studios in the early 1930s, credited to animator Webb Smith, who pinned sequential sketches to a board to plan animation sequences. Before storyboarding, animated films were planned primarily in written scripts β storyboarding made the temporal and visual sequence visible as a whole, enabling directors to identify pacing problems, missing beats, and narrative gaps.
The technique migrated to advertising and live-action film production, then to product design and UX research in the 1980s and 1990s. In service and product design, storyboards serve the same function: making a temporal sequence visible as a spatial whole, so that patterns and problems in the sequence become apparent.
The key insight storyboarding provides is narrative continuity β it forces designers to show how a user gets from Point A to Point B to Point C, including the transitions that feature specifications often gloss over. A feature list tells you what a product does; a storyboard shows you what it's like to use it. The moments between features (finding the app, opening it, getting confused, giving up, trying again) are often more important than the features themselves.
How It Worksβ
Step 1: Define the scenario
β Who is the user/character?
β What is their goal?
β What is the context and starting condition?
Step 2: Identify the key moments
β What are the 6β12 most important moments in the story?
β Include: trigger, key interactions, decision points, emotional high/low points, resolution
Step 3: Sketch each panel
β Simple stick figures are fine β detail is not the point
β Each panel shows: action + context + (optionally) thought/feeling
β Captions below each panel describe what's happening
Step 4: Tell the story
β Walk through the storyboard with others as a narrative
β Identify moments that feel incomplete, confusing, or emotionally flat
β Note which panels require multiple sub-panels (too much happening)
Step 5: Iterate
β Add, remove, or reorder panels based on feedback
β Focus on the moments where users struggle or succeed emotionally
β Prototype the most uncertain moments
Panel components:
- Image: Simple sketch of the scene (stick figures welcome)
- Caption: 1β2 sentences describing what's happening
- Thought bubble (optional): What the character is thinking or feeling
- Context notes (optional): Device, location, time pressure
Three Real-World Examplesβ
Airbnb's Pivotal 2009 Storyboardβ
In 2009, Airbnb was struggling. Co-founder Joe Gebbia introduced storyboarding to map the full guest and host experience. The team created storyboards for a guest booking a stay and a host listing their space, drawing every moment from discovery through checkout. The exercise revealed that the listing photos were a critical trust moment β and that most hosts had no idea how to photograph their spaces. This insight led directly to Airbnb sending professional photographers to host properties, which contributed significantly to the company's first major growth inflection. The storyboard made the "photo quality" moment visible in a way no metrics report had.
Uber's Driver Onboarding Flowβ
Early Uber faced extremely high driver dropout during the signup process. The UX team storyboarded the complete driver onboarding journey β from first seeing a Uber ad through completing the first ride β in 24 panels. The storyboard revealed four moments where the driver experience was confusing or anxiety-inducing: the insurance documentation step, the first app navigation during a live ride, the payment timing, and the rating system. Each was a previously untracked friction point. Re-designing these moments reduced driver dropout by 15% in A/B testing.
Hospital Patient Journey Mappingβ
A UK NHS trust used storyboarding to map a patient's journey from GP referral to specialist consultation β a 47-step process that took up to 6 months. The storyboard was drawn on a long roll of paper, with each moment annotated with patient quotes from interviews. The visual sequence made visible four moments where no one in the hospital system had responsibility for the patient's experience (they were "in between" systems). Redesigning these four handoffs reduced the referral-to-consultation time by 31% without adding staff.
When to Use Itβ
β Storyboarding is valuable when:
- Designing a new product, service, or experience from scratch
- Communicating a design concept to stakeholders without a prototype
- Identifying friction points in an existing user journey
- Aligning cross-functional teams around a shared user narrative
- Preparing for user research (stories help frame interview questions)
β Less useful when:
- The interaction is too complex for sequential panels (highly non-linear flows)
- The team is already well-aligned on the experience and needs technical specifications
- The problem is purely functional (optimise algorithm speed) rather than experiential
| Pairs well with | Why |
|---|---|
| Jobs to Be Done | JTBD identifies the job; storyboarding shows how the product performs it |
| Design Thinking | Storyboarding is the primary prototype tool in design thinking's ideate and prototype phases |
| Empathy Map | Empathy maps go deep at one moment; storyboards cover the whole journey |
| Minimum Viable Test | Storyboards identify which moments to test with MVTs |
Common Misuses and Limitationsβ
Making it too polished. The value of storyboarding is speed and flexibility. Teams that invest in polished illustrations lose the ability to quickly rearrange, add, or remove panels. Rough sketches on index cards or sticky notes that can be moved are often more valuable than clean digital storyboards.
Missing emotional content. Technical storyboards that show only actions miss the most important dimension: what the user is thinking and feeling at each moment. The emotional arc of a user experience often reveals design priorities that the functional arc obscures.
Drawing the happy path only. Storyboards that show only the ideal successful journey are design fantasies. The most valuable storyboards include: failed states (the user can't find what they need), error recovery (the user makes a mistake and fixes it), and emotional lows (the moment of frustration before the resolution).
Related Modelsβ
| Model | Relationship |
|---|---|
| Design Thinking | Storyboarding is a core tool in the design thinking prototype phase |
| Jobs to Be Done | JTBD defines what the storyboard should show |
| Minimum Viable Test | Storyboards reveal which moments require experimental validation |
Frequently Asked Questionsβ
Do you need to be able to draw to create storyboards?
No. Stick figures are entirely sufficient. The purpose of storyboard panels is to anchor the narrative moment spatially β to give the team something to point at when saying "this is where users struggle." The fidelity of the drawing is irrelevant to this function. Experienced UX designers often deliberately draw crudely to signal that the storyboard is a thinking tool, not a deliverable, and to encourage teammates to annotate and modify it freely.
What's the difference between a storyboard and a user journey map?
A user journey map is typically more structured and quantitative β it maps stages, touchpoints, actions, emotions, and pain points in a tabular format, often supported by research data. A storyboard is more narrative and qualitative β it tells a specific story about one user in one context, using images to convey the moment's texture. Journey maps are better for cross-team alignment on the full scope; storyboards are better for empathy-building and rapid concept communication. They are complementary: use a journey map to identify which moments matter most, then storyboard the critical moments in detail.
How many panels should a storyboard have?
6β12 is the productive range for most product and service design applications. Fewer than 6 risks missing critical transition moments. More than 15 becomes hard to hold in mind simultaneously β the key value of a storyboard is that the full sequence is visible at once. If the story genuinely requires more than 15 moments, consider separating it into multiple storyboards for different phases of the journey (acquisition, onboarding, regular use, churn).
Further Readingβ
- Martin, B. & Hanington, B. (2012). Universal Methods of Design β storyboarding and 99 other design research methods
- Unger, R. & Chandler, C. (2009). A Project Guide to UX Design β storyboarding in product design practice
- Brown, T. (2009). Change by Design β storyboarding as an empathy and communication tool
Apply with AIβ
π Storyboard your user journey with MindMax β
This page is part of the MindMax Mental Models Knowledge Base.