What it is
Short narratives describing how a particular persona, in a realistic context, uses a product to reach a goal. They add situational detail that abstract requirements lack.
When to use it
During Synthesize and into Ideate, to frame design around realistic use before detailing solutions.
Why (value)
Keep design grounded in context and motivation, expose edge cases, and give a shared story to design and test against.
How to run it
- Pick a persona and a goal.
- Describe the triggering situation and context.
- Narrate the steps they take toward the goal.
- Keep it solution-light early, detail it as design firms up.
- Use it to drive design and evaluation tasks.
Inputs and outputs
- Inputs: Personas, goals, contextual understanding.
- Outputs: Written scenarios that anchor design and test tasks.
Time and effort
Low. Quick to draft once personas and goals exist.
Evidence and limitations
A narrative framing tool, credible when built on research, speculative when not. Scenarios are not evidence that people behave this way; they encode intent and assumptions. See Evidence and limitations.
Tips and pitfalls
- Tie scenarios to real personas and contexts.
- Keep them solution-agnostic until later.
- Cover the important edge cases, not just the happy path.
Variations
Goal-based scenarios, day-in-the-life narratives, use-case scenarios.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
- 18F Methods (US government, public domain).
Explore related methods
- Personas — Represent key user types as memorable archetypes to keep design decisions grounded in real needs.
- Use cases — Specify the steps of an interaction between a user and system, including alternate and error paths.
- Storyboarding — Tell the user's story frame by frame to keep design grounded in context and narrative.
