Storyboard
A storyboard uses a short sequence of scenes to show a person’s context, actions, and experience with a proposed product or service.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/storyboard/
01What it means
A storyboard is a visual narrative that explains how a situation unfolds. Panels combine simple drawings and captions to show the person, trigger, environment, interaction, and outcome. Unlike a screen flow, it can show events away from the interface and why someone would use the product at all.[1][2]
02Why it matters
Storyboards expose assumptions about timing, motivation, and surrounding circumstances that a feature description leaves implicit. They help a team compare concepts before detailed interaction design and invite feedback on whether the scenario is plausible.
03When to use it
Use storyboards to discuss an unfamiliar concept, a service encounter, or a product used across physical and digital contexts. Use a prototype for detailed interaction questions or a journey map for systematic coverage of an existing experience.
04How it works
- Choose a specific person, situation, and question the story should explore.
- Outline the trigger, key actions, and outcome in a few scenes.
- Draw context and behavior with brief captions; artistic polish is unnecessary.
- Mark invented assumptions separately from research observations.
- Review plausibility with relevant people and revise the concept or next research question.
05A practical example
A delivery team illustrates a customer realizing that they will miss a parcel, changing the drop-off location on a phone, and receiving confirmation before the courier arrives. Reviewing the sequence raises a cutoff-time dependency that was absent from the original feature request.
06Where it breaks
A persuasive narrative can make a weak concept seem inevitable. One story cannot represent all users or failure cases, and agreement with the story does not demonstrate purchase or successful use. Keep alternative scenarios available.
Common mistakes
- Drawing only interface screens without a person or context.
- Presenting an imagined scenario as research evidence.
- Spending more time illustrating than examining assumptions.
07Sources
- Storyboards Help Visualize UX IdeasNielsen Norman Group · Professional guidanceStoryboards Help Visualize UX Ideas
- StoryboardIDEO.org Design Kit · Method guideStoryboard