Storyboarding

Purpose

Storyboarding translates an idea, user flow, or service experience into a sequence of visual scenes — like a comic strip. By drawing key moments frame by frame, teams surface gaps in logic, missing steps, and emotional highs and lows that text-based descriptions obscure. Storyboards also serve as powerful communication tools for stakeholders.

At a glance

• Group size: 2–8
• Duration: 40 minutes
• Difficulty: Intermediate
• Facilitation style: Visual, narrative
• Setting: In-person or virtual

How to run

1. Define the scenario (5 min). Agree on the user, context, and goal. Write a one-sentence scenario: “A new customer discovers our product and makes their first purchase.”
2. Identify key moments (5 min). Brainstorm the 6–12 critical moments in the journey. Write each on a sticky note and arrange in sequence.
3. Sketch frames (20 min). Draw one frame per moment. Include: setting, character action, dialogue/thought bubbles, and any UI or environmental detail. Stick figures are fine.
4. Review and refine (7 min). Walk through the storyboard as a group. Identify gaps, unrealistic steps, or missing emotional beats. Add or revise frames.
5. Annotate (3 min). Add brief captions below each frame to clarify context, data points, or design requirements.

Materials needed

• Storyboard template (grid of 6–12 blank frames) or blank paper
• Markers and pencils
• Sticky notes for annotations
• Reference: persona or user profile

Pitfalls & common mistakes

• Too many frames. 6–12 is the sweet spot. More becomes a specification document, not a storyboard.
• Focusing on UI details. At this stage, focus on the story, not pixel-level design.
• Skipping emotional beats. Show how the character feels at each step — frustration, delight, confusion.

Inclusion & accessibility

• Pair non-drawers with drawers — one describes, the other sketches.
• Read the storyboard aloud as a narrative for participants who cannot see it.
• Offer digital storyboarding tools for remote participants.

Variations

• Before & After storyboard: Show the current experience, then the improved one.
• Branching storyboard: Include decision points with alternative paths.
• Video storyboard: Use the frames as a shot list for a video prototype.

When NOT to use this

• When the idea is too abstract to express as a sequential user experience.
• When detailed wireframes or prototypes already exist and a storyboard would be redundant.

Source & further reading

• Knapp, J., Zeratsky, J., & Kowitz, B. (2016). *Sprint.* Simon & Schuster.
• Quesenbery, W. & Brooks, K. (2010). *Storytelling for User Experience.* Rosenfeld Media.