A narrative that places a specific persona in a particular context and goal, describing how they would behave and what they would need from a product. Scenarios make abstract user needs concrete, grounding design decisions in realistic human situations rather than feature lists.
Common contexts
- Writing a scenario for a nurse accessing a patient record on a shared ward tablet under time pressure to anchor an IA decision
- Using a scenario during a design critique to test whether a proposed flow holds up in a realistic context rather than ideal conditions
- Presenting three contrasting scenarios to a product team to surface which user context the current design fails to accommodate
Use when
Write scenarios when the team is debating feature design in the abstract — they work best as a reality check that reintroduces human context into conversations that have drifted toward technical or business framing.
Avoid when
Don't use scenarios as a substitute for actual observation — a scenario that was written without fieldwork is a team's collective assumptions dressed in narrative form, and it can be just as misleading as a proto-persona used past its shelf life.
The most useful scenarios are the uncomfortable ones — the user who is stressed, distracted, or using the product in an unanticipated context, because that's when design assumptions reveal their weak points.
Real-world examples
- Nielsen Norman Group uses scenarios like 'Maria is a 52-year-old nurse who needs to check a patient's medication dosage quickly between rounds' to focus usability test tasks on realistic, emotionally grounded context.
- Google's design team writes 'day in the life' scenarios for each persona before beginning any new feature design, ensuring that edge cases surfaced in scenarios are handled in the design before prototyping.
- The GOV.UK design team wrote 150+ task scenarios derived from call-centre transcripts before designing their Universal Credit digital service, ensuring every user flow addressed a documented real-world situation.