User Persona

A persona distills patterns from user research into a memorable, representative character: who they are, what they are trying to accomplish, the context they work in, and what gets in their way. It gives a team a shared, specific "who" to design for instead of a vague "the user."

Personas are only as good as the research behind them; invented from assumptions, they become a way to launder opinion. Used well, they anchor prioritization — "would this actually help Maya close her month-end faster?" — and feed directly into journey maps and flows.

In practice

A roadmap debate stalls: sales wants an admin console, product wants richer reports. The team's two research-based personas settle it — “Maya, the ops lead who buys and configures” touches the console monthly, while “Dan, the analyst who lives in reports” is the daily active user whose renewal depends on output quality. Reports win the quarter. The personas didn't add data; they made existing research impossible to argue past.