# Storyboard

A storyboard uses a short sequence of scenes to show a person’s context, actions, and experience with a proposed product or service.

- Type: artifact
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-10-20
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/storyboard/>)

## What 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.

## Why 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.

## When 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.

## How it works

1. Choose a specific person, situation, and question the story should explore.
2. Outline the trigger, key actions, and outcome in a few scenes.
3. Draw context and behavior with brief captions; artistic polish is unnecessary.
4. Mark invented assumptions separately from research observations.
5. Review plausibility with relevant people and revise the concept or next research question.

## A 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.

## Where 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.

## Sources

1. [Storyboards Help Visualize UX Ideas](<https://www.nngroup.com/articles/storyboards-visualize-ideas/>) — Nielsen Norman Group · Professional guidance
2. [Storyboard](<https://www.designkit.org/methods/storyboard.html>) — IDEO.org Design Kit · Method guide

## Related topics

- [Concept Testing](<https://wiki.soroush.uk/topic/concept-testing/>)
- [Customer Journey Map](<https://wiki.soroush.uk/topic/customer-journey-map/>)
- [Prototype](<https://wiki.soroush.uk/topic/prototype/>)
