The method helps clarify user actions, touchpoints, and product concepts concretely. It makes user flows, service contacts, and product decisions visible. The result is captured as a storyboard, concept narrative, and testable assumptions.
Storyboarding
Turns user actions, touchpoints, and product concepts into a tangible result by defining a scenario, sketching key scenes, and refining the concept.
How does the persona experience the scenario frame by frame, and which assumptions about context, behavior and expectations become visible?
The team follows the steps: define scenario, sketch key scenes, add annotations, check flow, and revise the concept. Each step is captured visibly. At the end, a storyboard, concept narrative, and testable assumptions are available so decisions, tests, or actions can follow directly.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Define scenario
- 2Sketch key scenes
- 3Add annotations
- 4Check flow
- 5Refine concept
The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- Concept testing
- Service design
- Prototype planning
Not good for
- Precise UI specification
- Deep analytics
Deep dive
Storyboarding follows a clear working logic: defining scenario, sketching key scenes, adding annotations, checking flow, and refining the concept. This turns the method into a visible thinking process rather than only a conversation. Participants move step by step from raw material, observations, or options toward a shared structure. As a result, a storyboard, concept narrative, and testable assumptions support decisions, learning, or further planning.
Prepare a clear guiding question, the right information, and a visible workspace. Plan about 30-90 min with 1-8 people and use the format either in a workshop or asynchronously. The facilitation needs notable structure and preparation; short timeboxes, visible intermediate results, and a parking lot for open questions help.
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.
When to choose differently
Short decision aid for existing alternatives.
Statt Storyboarding, wenn du mehrere Lösungsskizzen parallel erzeugen und direkt im Team kritisieren lassen willst.
Similar methods
All methodsTurns user actions, touchpoints, and design concepts into a tangible result by clarifying the problem and constraints, sketching individually, and iterating together.
Statt Storyboarding, wenn du mehrere Lösungsskizzen parallel erzeugen und direkt im Team kritisieren lassen willst.
Turns user actions, touchpoints, and product details into a tangible result by selecting a persona or customer group, defining journey phases, and deriving opportunities and actions.
Turns ideas, open questions, and testable next steps into a tangible result by mapping the challenge, sketching solutions, and testing with users.
Turns user actions, touchpoints, and concept details into a tangible result by defining service scope, laying out the customer journey, and deriving owners and actions.
Parallel design teams turn a shared challenge into comparable concepts, open questions, and a consolidated direction.
Alternating divergent and convergent phases keep problem framing and solution design visibly separated for product work.