Personas and Scenarios

Personas and scenarios are design representations that synthesize user research into memorable, concrete forms: fictional but research-based user archetypes and narratives of how they use a system.

Definition

A persona is a concrete, research-grounded description of a fictional but representative user, including goals and context, used to focus design; a scenario is a narrative describing how a user accomplishes a task with a system, used to envision and reason about design.

Scope

This topic covers techniques for representing and communicating user understanding: personas as archetypal users grounded in research, scenarios and use cases as narratives of activity, and scenario-based design that drives design from envisioned use. It addresses how research findings are turned into shared, actionable artefacts. It does not cover the gathering of the underlying data, treated under other user research topics, nor the design and prototyping process, treated under interaction design.

Core questions

• What makes a persona useful rather than a stereotype?
• How do scenarios help teams envision and reason about designs?
• How are personas and scenarios grounded in user research?
• What are the benefits and risks of relying on these representations?

Key concepts

• persona
• primary vs secondary persona
• scenario
• use case
• scenario-based design
• user goals
• design archetype
• grounding in research

Key theories

Goal-directed personas

Cooper popularized personas as precise, goal-oriented descriptions of archetypal users that keep design focused on specific people's needs rather than an elastic notion of the user, reducing the tendency to design for oneself.

Scenario-based design

Carroll argued that narratives of use, scenarios, are a powerful design medium because they make abstract requirements concrete, support reasoning about consequences, and connect design to envisioned activity.

Personas as practice and theory

Pruitt and Grudin examined personas in real organizations, showing they can align teams and communicate research effectively but require grounding in data and care to avoid misuse or unfounded assumptions.

Clinical relevance

Personas and scenarios give design teams a shared, concrete understanding of who they are designing for and how a product will be used, helping prioritize features and keep decisions user-focused; their value depends on being grounded in real research rather than invented.

History

Cooper introduced personas in design practice in the late 1990s, and Carroll developed scenario-based design as a complementary narrative approach around the same time. Pruitt and Grudin's 2003 analysis brought research scrutiny to personas in practice, and both techniques became staples of user-centered and UX design.

Debates

Are personas evidence-based or just convenient fictions?

Personas are valued for focusing and communicating design, but critics warn that when not grounded in real research they can encode assumptions and stereotypes; proponents stress that personas must be derived from and traceable to user data to be trustworthy.

Key figures

• Alan Cooper
• John M. Carroll
• John Pruitt
• Jonathan Grudin

Seminal works

• cooper1999
• carroll2000
• pruitt2003

Frequently asked questions

Are personas just made-up users?

Effective personas are fictional in that they describe a single representative individual, but they should be grounded in real research about actual users' goals, behaviours, and contexts. Personas invented without data risk encoding the team's assumptions and can mislead design rather than guide it.

How do scenarios help design?

Scenarios tell a concrete story of a persona using a system to reach a goal. By making abstract requirements tangible, they help teams imagine the experience, spot gaps and consequences, and discuss design alternatives in terms of real use rather than abstract features.