How to use user personas
A user persona turns "our users" into a specific person with goals and frustrations. That specificity is the point — it makes design and prioritization decisions concrete instead of abstract.
- Ground them in reality — base personas on real research where you can.
- Lead with goals and pains — that's what drives product decisions.
- Keep the set small — 2–4 personas a team can actually remember.
Frequently asked questions
- What is a user persona?
- A user persona is a fictional but realistic profile of a target user — their role, goals, and frustrations — that helps a team design for real needs instead of a vague "average user".
- What should a user persona include?
- At minimum a name and role, their goals, their frustrations or pain points, and a representative quote. The point is empathy: enough detail to picture a real person.
- Why use personas?
- Personas keep teams focused on the user. When a decision comes up, "would this help Maria?" is far more useful than abstract debate about features.
- How many personas should you have?
- Usually 2–4 primary personas. Too many and they lose their power to focus the team. This tool generates two to start.