User Persona
A research-based profile representing a key segment of your users.
A user persona is a semi-fictional character that captures the goals, behaviours, and frustrations of a real user segment, distilled from research. Personas keep teams aligned on who they're designing for and prevent the trap of designing for everyone (and therefore no one).
A useful persona is grounded in data, not demographics-for-their-own-sake — it focuses on motivations and context of use that actually change design decisions.
Key characteristics
- A composite character built from real research data, not invented demographics.
- Captures goals, motivations, frustrations and context of use rather than trivia.
- Gives teams a shared shorthand — "would Maria understand this?" — to align decisions.
- Most useful in small numbers (2–4); too many dilute focus.
Example
"Maria, 34, freelance designer who needs to invoice clients in under two minutes between projects" guides an invoicing app toward speed and simplicity over advanced accounting features.
Frequently asked questions
Are user personas still useful?
Yes, when grounded in research. Evidence-based personas align teams and keep decisions user-centred. Personas invented from assumptions can mislead — the discipline is in the data behind them, not the format.
How are personas different from jobs-to-be-done?
Personas describe who the user is and what they want; jobs-to-be-done describes the progress a user is trying to make in a situation. Many teams use both — personas for empathy, JTBD for prioritisation.
Related terms
Need this done, not just defined?
I design and build it — Framer sites, product UI/UX, and more.