# User Persona

A user persona is a research-grounded representation of a meaningful user pattern, created to keep needs, contexts, goals, and behaviors visible in decisions.

- Type: artifact
- Domain: Market & business
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/user-persona/>)

## What it means

A user persona is a concise, realistic portrait of a user group whose members share relevant behaviors, motivations, needs, or contexts. Although presented as a person for memorability, it represents a pattern in evidence rather than an invented individual. Useful personas emphasize differences that affect product decisions.

## Why it matters

Personas can make research easier to recall and discuss across a team. They help participants ask whose goal is being served, compare conflicting needs, and evaluate scenarios with more specificity than “the user.” Their value comes from the evidence and decisions attached to them, not decorative biography.

## When to use it

Use personas when research reveals stable user patterns that recur across design questions, especially in products serving several roles or contexts. A lightweight proto-persona can expose assumptions early, but it must be labeled and tested. Retire personas that no longer influence decisions or reflect current evidence.

## How it works

1. Clarify which product decisions the personas should support.
2. Gather qualitative evidence and relevant behavioral data from representative users.
3. Identify recurring patterns in goals, context, behavior, constraints, and mental models.
4. Create the smallest set of distinct personas needed to explain consequential differences.
5. Include evidence, scenarios, uncertainties, and implications while omitting decorative trivia.
6. Use personas in prioritization and design reviews, then revise them as new research accumulates.

## A practical example

A hospital scheduling team finds that occasional patients and clinic coordinators both book appointments but face different constraints. A coordinator persona highlights bulk work, exception handling, and accountability across locations. The persona leads the team to test queue management instead of merely enlarging the patient calendar.

## Where it breaks

Personas compress diverse lives into a model and may conceal disability, culture, power, or situational variation. Fictional names and photos can encourage stereotypes or false confidence. Personas should not replace direct research, accessibility work, analytics, or testing with real users, and sensitive attributes require careful handling.

## Common mistakes

- Inventing personas in a workshop and presenting them as research findings.
- Filling profiles with age, hobbies, and quotes that do not affect decisions.
- Creating so many personas that teams cannot remember or use them.
- Treating one persona as representative of every user in a segment.

## Sources

1. [Personas: Study Guide](<https://www.nngroup.com/articles/personas-study-guide/>) — Nielsen Norman Group · Professional research guide
2. [3 Persona Types: Lightweight, Qualitative, and Statistical](<https://www.nngroup.com/articles/persona-types/>) — Nielsen Norman Group · Professional practice article

## Related topics

- [Ideal Customer Profile](<https://wiki.soroush.uk/topic/ideal-customer-profile/>)
- [User Interviews](<https://wiki.soroush.uk/topic/user-interviews/>)
- [Market Segmentation](<https://wiki.soroush.uk/topic/market-segmentation/>)
