What it is
Short narratives describing how a particular persona, in a particular situation, pursues and achieves a goal, grounding design in realistic context.
When to use it
During Synthesize, after personas, to connect user types to concrete tasks and contexts.
Why (value)
Makes abstract requirements tangible and keeps the team focused on real goals and contexts rather than isolated features.
How to run it
- Choose a persona and a meaningful goal.
- Set the context: trigger, environment, constraints.
- Narrate how they move toward the goal.
- Note needs and friction along the way.
- Use scenarios to drive design and test cases.
Inputs and outputs
- Inputs: Personas and research about real goals and contexts.
- Outputs: A set of goal-based narratives.
Time and effort
Low. Hours once personas exist.
Evidence and limitations
Scenarios are inference built from research; they are plausible stories, not evidence, and are only as sound as the research behind them. See Evidence and limitations.
Tips and pitfalls
- Ground scenarios in real research, not wishes.
- Keep them goal-focused, not feature tours.
- Include realistic constraints and interruptions.
Variations
Goal-based, elaborated, and edge-case or failure 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
- 18F Methods (US government, public domain).
Explore related methods
- Scenarios — Narrate how a specific person accomplishes a goal so the team designs for realistic context.
- Personas — Represent key user types as memorable archetypes to keep design decisions grounded in real needs.
- Journey mapping — Visualize a person's end-to-end experience across steps, emotions, and touchpoints to find pain and opportunity.
