User Scenarios

Also known as: Usage Scenarios / Persona-Based Scenarios

discoveryexplorationmediumIntermediate

TL;DR

Narratives describing how a Persona interacts with a product to achieve a specific goal.

Strategic value

Allows starting designs from a story that describes an ideal experience from the user's perspective. Helps decision-makers visualize the system without getting bogged down in premature technical debates.

Category: synthesis-empathyEstimated time: 2-4 hours per context scenario; 4-8 hours for complete set

What is it

User Scenarios are narrative descriptions that tell the story of a user — represented by a Persona — interacting with a product or system to achieve a specific goal in a particular context. Unlike technical documents, they focus on the human experience, the user's thoughts and behavior, not the system.

What it is for

✓Bring Personas to life with concrete usage stories
✓Help decision-makers visualize the system without premature technical debates
✓Define design requirements from the user's perspective
✓Provide realistic context for usability tests

Research methods that feed it

In-depth interviewsContextual inquiryPreviously created User PersonasIdeation workshops

When to use it

✓In early requirements definition phases
✓During ideation workshops to anchor the team in the user's daily life
✓In usability tests to provide realistic context before the task

When NOT to use it

✗Not for capturing exhaustive functional requirements or mapping every database response (Use Cases are for that)
✗Not for documenting all alternative paths and conditional logic — scenarios typically assume the ideal 'happy path'

Required components

✓The Actor/Persona: the story's protagonist, must be a specific archetype or Persona, not an abstract user
✓The Goal/Problem: what the main character needs to achieve or solve
✓The Context (Setting): the physical, emotional, or situational environment where the action occurs
✓The Trigger Event: the situation that starts the story and establishes preconditions

Optional components

○Plot points: interesting events that visualize important system aspects
○Visual support: illustrations, photographs, or storyboards accompanying the narrative
○Interaction vocabulary: interface details (only in advanced phases)

How to create it step by step

1Define the problem and Persona expectations: Select the target Persona and clarify what they need to achieve.
2Build Context Scenarios: Create high-level stories without detailing technology — 'pretend the interface is magic'.
3Identify requirements: Extract design requirements that naturally emerge from the scenario.
4Evolve to Key Path Scenarios: Add step-by-step detail with specific interface vocabulary.
5Create Validation Scenarios: 'What if...?' stories to test design resilience against unexpected situations.

Tips for small teams

Start with 1-2 context scenarios per primary Persona
Use simple, narrative language — if it reads like a technical spec, there's a problem
Share scenarios with stakeholders to validate they reflect real situations
Evolve scenarios as design progresses (context → key path → validation)

Common mistakes

✗Confusing them with Use Cases: writing from the system's perspective instead of the user's
✗Unnecessary detail excess: including every button and edge case in early stages makes the scenario read like code
✗Irrelevant details: data that doesn't affect the goal belongs in the Persona, not the scenario
✗Using abstract actors: generic roles like 'the User' prevent empathy generation
✗Describing the status quo: the scenario should illustrate the ideal future experience, not the current system
✗Biasing usability: technical vocabulary that induces participant responses

Quality criteria

✓Concrete but flexible: provokes 'What if...?' in the team
✓Reads as a credible narrative that reveals why the user does things
✓Facilitates decisions without premature technical debates
✓Doesn't assume preconceived technology

Authority quotes

“Scenarios are written from the perspective of the individual human user represented by the 'Persona', not from the perspective of the system or business process.”
— About Face

“Persona-based scenarios are concise narrative descriptions of one or more personas using a product to achieve specific goals.”
— About Face

Contextualized example

Context: Personal finance management app for young professionals in Chile.

Persona: Camila, 27, freelance designer. Variable income. Wants to save for a trip but doesn't know how much she actually spends per month.

Context Scenario: It's Sunday evening and Camila reviews her week. She's had 3 client payments and multiple small expenses. She wants to know if she's on track for her savings goal. She opens the app and in seconds sees a visual summary of income vs. expenses for the month. She notices her delivery spending exceeds her budget. The app suggests adjusting her weekly delivery target.

Design insight: The scenario reveals Camila needs to see income vs. expenses at a glance (no drill-down) and receive proactive suggestions, not just data.

Template available

Format: Google Docs$10 USD

Phase

discoveryexploration

Audience

product-teammultidisciplinary

Complexity

medium

Experience level

Intermediate

Related deliverables

Free tool by UXR — UX Research Consulting in Chile