Scenario mapping
Walk a persona through a key activity step by step, to agree the experience they should have and spark ideas from it.

- Time
- 20–30 min
- People
- Design team, 4–8
Overview
In the board’s own words: a collaborative exercise where the design team explores how different persona segments approach a key activity, using this to understand their needs, envision the experience they should have, and spark ideas for potential future solutions.
It sits in concept discovery, alongside the user journey mapping the Discovery Introduction lists for that phase. The distinction from a journey map is the ambition: the deck’s as-is user journey belongs to framing and records what happens today, while a scenario map describes the experience the persona should have and collects design ideas as you go.
Used in ideation ahead of Crazy 8’s: the steps, ideas and questions it surfaces are where that session’s opportunity statements come from, so run this first rather than walking into Crazy 8’s with nothing but a persona.
When to use it.
Once you have a persona and a key activity worth examining in detail. It builds directly on Persona — the board pins a protopersona above the scenario, so the steps stay tied to somebody specific.
Who to involve.
The design team, four to eight. Worth pulling in someone who has watched the activity happen; the steps get vague fast without them.
Effort.
Low prep Medium engagement Runs as activity 4 of a larger workshop on the board.
Outcomes.
An agreed picture of the experience the persona should have, a set of design ideas anchored to specific steps rather than floating free, and a questions list that becomes the research plan for validation.
Recommendations.
Do not let it become a wireframe — steps and ideas, not screens; screens come later, from this. Run it for more than one persona segment if you can, because the comparison is where the insight is. And carry the questions lane straight into validation: it is more honest than a research list written from scratch afterwards.
How to run it
Pin the persona above the scenario
Goals, pain points, needs and behaviours, visible while you work. Every step should be checkable against them.
Name the scenario
As a group, agree on one realistic activity to walk through, start to finish — the board’s own example is a dispatcher beginning her shift with a handover, reviewing overnight issues and setting up her console for the day.
Write the steps as a sequence
One sticky per step, in order, in the persona’s terms. Concrete beats general — “confirms who has signed on, who is absent, and overall crew readiness” is a step; “checks the team” is not.
Add the three lanes underneath
Below each step, add three parallel rows of stickies:
- Design idea — what could make this step better
- Comments and considerations — constraints, dependencies, things to remember
- Questions — what you do not know yet
Keep them in separate rows. Ideas and open questions get muddled otherwise, and the questions are what turn into research.
Repeat for the next persona segment
Run the same four steps again for a second persona segment if you can — one scenario for one persona is a useful artifact; two is an insight.


