UX Design Mapping tool

Storyboarding

Makes a concrete use moment visible as a sequence of understandable scenes.

Storyboarding arranges a scenario, visual scenes, and short captions into a readable flow. It helps teams review the context and transitions of a researched experience or proposed solution. Assumptions about thoughts and feelings must be labeled.

Core question

Which situations, actions, and transitions shape this specific user flow or proposed experience?

Prepare a storyboard Method guide

Start comparison

Give feedbackIs this method useful to you?

Participants: 1-8 Contributors
Time: One session or sequence

The phase bar moves from scenario and sequence to visuals and review.

Six paper cards show a person moving from a problem through a service flow to a completed outcome.

Scenario
Bound the scenario
Choose a case with a beginning, goal, and answerable design question.
Sequence
Sketch the sequence
Break the scenario into a small number of ordered key moments.
Storyboard
Add visuals and captions
Draw simply and caption actions and relevant context.
Review
Review the flow together
Read the sequence without verbal explanation and mark unclear transitions.

Check where sequence, context, or a service transition remains unclear. Revise the scene and mark whether it comes from research, observation, or a concept assumption.

A good fit when

Use storyboarding to discuss one concrete current experience, concept idea, or critical flow. Choose one case and show only scenes that matter to the decision.

Ideal for

Concept testing
Service design
Prototype planning

Not good for

Precise UI specification
Deep analytics

Outputs

Scenario storyboard
A connected sequence of context, action, and consequence.
Testable assumptions
Visible gaps, critical transitions, and open tests.

Six storyboard scenes

Fictional concept example

One connected scene per row with context, action, and evidence status.

Six storyboard scenes
Storyboard frame	Frame	Scene and context	Action or touchpoint	Evidence or assumption
Frame 1Show the trigger and goal.	1	A shelf comes loose on Saturday.	The person decides they need a cordless drill.	Fictional assumption about need; not an observed case.
Frame 2Show the first step and search context.	2	The person opens a fictional tool catalog.	They search for a suitable item.	Concept assumption; no real research.
Frame 3Show decision-relevant information.	3	The tool card shows stock and location.	A Saturday pickup window appears beside availability.	Proposed touchpoint, not tested yet.
Frame 4Explain the transition to the next action.	4	The person chooses a time window.	A reservation step confirms the plan.	Untested functional assumption.
Frame 5Show access to the service.	5	The person arrives at the lending site.	Directions and access information support pickup.	Opening hours and access conditions to check.
Frame 6Show the outcome and an open follow-up.	6	The tool is returned after the repair.	The flow ends with an available return option.	Fictional assumption; validate return in everyday use.

1. Frame
Frame 1
1
Frame 2
2
Frame 3
3
Frame 4
4
Frame 5
5
Frame 6
6
2. Scene and context
Frame 1
A shelf comes loose on Saturday.
Frame 2
The person opens a fictional tool catalog.
Frame 3
The tool card shows stock and location.
Frame 4
The person chooses a time window.
Frame 5
The person arrives at the lending site.
Frame 6
The tool is returned after the repair.
3. Action or touchpoint
Frame 1
The person decides they need a cordless drill.
Frame 2
They search for a suitable item.
Frame 3
A Saturday pickup window appears beside availability.
Frame 4
A reservation step confirms the plan.
Frame 5
Directions and access information support pickup.
Frame 6
The flow ends with an available return option.
4. Evidence or assumption
Frame 1
Fictional assumption about need; not an observed case.
Frame 2
Concept assumption; no real research.
Frame 3
Proposed touchpoint, not tested yet.
Frame 4
Untested functional assumption.
Frame 5
Opening hours and access conditions to check.
Frame 6
Fictional assumption; validate return in everyday use.

Substantiate inner states and events from research or label them as assumptions.

NN/G

First step

Name the scenario, person or role, and question the sequence should clarify.

Open the method guide

Good to do first

Paper illustration of an eight-panel idea sheet with varied sketches beside a timer set to eight minutes.

Innovation

Crazy 8s

Supplies the chosen sketch as the starting image for the scene sequence.

Innovation

Design Sprint

Supplies the concept status and insights for the depicted scene.

Where to go next?

Paper illustration of a participant using a prototype while an observer takes notes beside a highlighted usability issue.

UX Research

Usability Testing

Tests the assumption visible in the storyboard against real tasks.

Product Discovery

Riskiest Assumption Test

Tests the core assumption flagged in the storyboard ahead of time.

Deep dive

Purpose

When a usage scenario needs to become understandable early, it condenses situations, context, and flow into a legible sequence. It helps check concept ideas before anything gets built.

How it works

It depicts key scenes so that sequence, context, and possible breaks in the flow stay visible. Because the representation starts narrative rather than technical, concepts can be checked early with stakeholders before an interface gets detailed.

In detail

Storyboarding works because usage situations become visible as a sequence of scenes, making the logic, transitions, and meaning of a solution more concretely checkable. Good use shows action, context, and reaction in a form that enables discussion about behavior, not just surface. The method is strong when it uncovers gaps between intent and actual usage experience early, preparing better design decisions.

Facilitation

Start with a concrete trigger for the usage and keep the narrative thread consistent across all scenes. The most clarity emerges at the point where a scene only works because knowledge or motivation is silently assumed. Close with an understandable flow, marked breaks, and a selection of the scenes to test or design next.

The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics

Visualization Concepts Sequence Prototype

Sources

Storyboards Help Visualize UX Ideas - NN/Gnngroup.comA specific scenario, sequence of visuals, and short captions communicate context and a proposed experience.UX Stories Communicate Design - NN/Gnngroup.comUX stories help teams discuss a user journey and the context around a design idea.

In playbooks

Moderate Solution IdeationMove from problem understanding to many ideas, structured selection, and first concept.

Artifact templates

Workshop AgendaCompact agenda template for method sequences with timebox, purpose, and output.

agenda

workshop-agenda-markdown.md

Compact agenda template for method sequences with timebox, purpose, and output.

Workshop Agenda

Goal: ... Participants: ... Duration: ...

Time	Method	Purpose	Output
00:00	Check-in	Set focus	Shared start
00:10	How Might We	Ideation questions	HMW list
00:35	Brainwriting	Generate ideas	Idea pool
01:10	Dot Voting	Prepare selection	Prioritized ideas
01:30	Storyboarding	Make the concept tangible	Storyboard

Close-out

Decision, owner, next test.

Storyboarding: WorksheetPrepare a short, focused sequence for one use scenario or concept.

markdown

storyboarding-working-template.md

Prepare a short, focused sequence for one use scenario or concept.

Storyboarding: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

One focused storyboard Time: About 45–90 minutes for one sequence; research and validation are outside the session.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

Materials: Scenario description, relevant research evidence or clearly labeled assumptions, paper or a digital board with frames, and pens.
Roles: One person assembles the story; a small team checks readability and transitions. For user-centered storyboards, use statements and emotions only when supported by evidence or label them as hypotheses.
Advance information: Set the role, goal, timeframe, starting problem, and pending decision. Gather research notes and gaps.
Overall time needed: About 45–90 minutes for one focused sequence including scenario, sketches, and review. Plan research and later validation separately.
Setup: Arrange frames in reading order. Choose low fidelity before drawing. Mark evidence, hypotheses, and unknowns visibly.