What Is a User Persona and How to Create One

What a persona is

A user persona is a fictional but realistic description of a group of users who share similar goals and behaviour. It gives the team one shared picture of "who we design for", so discussions shift from "I think users want…" to "Would Dilnoza be able to do this on her phone between meetings?"

A persona is a summary of patterns, not a portrait of one real person and not a marketing segment. Marketing segments describe who buys; personas describe how people use the product and why.

Research-based vs assumed personas

Assumed personas are not useless: they make the team's assumptions explicit. The mistake is treating them as truth. Mark them clearly as hypotheses and replace them with research as soon as you can.

Fields that matter

Many templates are full of age, hobbies and favourite brands. Most of that does not influence design. Focus on:

• Name and short role — to make the persona easy to refer to.
• Context — where, when and on what device they use the product.
• Goals — what they are trying to achieve, in their words.
• Tasks — the specific actions they come to do.
• Pain points — what frustrates or blocks them today.
• Behaviour and skills — tech confidence, habits, alternatives they use now.
• Motivations and concerns — what makes them choose or hesitate.
• A quote from research — one line that captures their attitude.

Demographics belong in a persona only when they affect behaviour, for example language, accessibility needs or limited mobile internet.

Ready template

## [Name], [short role]
"[Real quote from an interview]"

**Context:** where, when and on which device they use the product
**Goals:** 1–3 outcomes they want
**Key tasks:** what they come to do most often
**Pain points:** what blocks or annoys them now
**Current solution:** what they use instead (tools, people, workarounds)
**Tech confidence:** low / medium / high, with a short note
**Decision factors:** what makes them trust, choose or leave
**Source:** which research this is based on, and when

Keep each persona to one page. If it does not fit, it is probably mixing several user groups.

How to create a persona step by step

1. Collect data. Interview users, talk to support and sales, review analytics and feedback.
2. Find patterns. Group users by goals and behaviour, not by age or job title.
3. Pick the main groups. Usually a few personas are enough; one primary persona helps resolve conflicts.
4. Fill the template with real findings and quotes.
5. Validate with the team and with people who talk to customers every day.
6. Review regularly as the product and audience change.

How personas should inform design

A persona is working when it changes concrete decisions:

• Prioritising features: "Does this solve a pain point of our primary persona?"
• Choosing flows: a persona who books from a phone on the go needs short steps and guest checkout.
• Writing interface text: a persona with low tech confidence needs plain words, not jargon.
• Planning tests: recruit usability participants who match persona criteria.
• Settling debates: check proposals against the persona's goals instead of personal taste.

Common mistakes

• Personas invented in one meeting and never checked.
• Too many personas, so none of them guides decisions.
• Rich biography but no goals or pain points.
• Stock photos and stereotypes that distract from real needs.
• A finished document that lives in a folder and is never referenced.