By the end of this lesson you can
- Explain what a persona is for and when it helps a team.
- Build a persona from research evidence rather than imagination.
- Avoid stereotypes and the common ways personas go unused.
The idea
A persona is a short, realistic description of a group of users with similar goals, behaviours and frustrations. It is a communication tool: it helps a team keep real people in mind when making decisions.
Evidence first
Useful personas come from research. They summarise patterns you saw across several participants: what they are trying to do, how they currently do it, what gets in the way, and what matters to them. A persona invented in a meeting reflects the team's assumptions, which is the opposite of what personas are for.
Behaviour over demographics
Age, job title and a stock photo feel concrete but rarely change design decisions. Behaviour does: "orders the same lunch every day and wants it in two taps" versus "explores new restaurants and reads every review". Many teams now leave out photos and names that suggest a gender or ethnicity, because these invite stereotypes and add little.
Keep the set small
Two to four personas are usually enough. Choose a primary persona whose needs you design for first. If you try to satisfy ten personas equally, you satisfy none.
Why it matters in real projects
Personas help teams argue about real needs rather than personal preferences. "Would Priya, who checks her balance at the bus stop, understand this?" is a better question than "Do you like this?" But personas are only as good as the evidence behind them. Fictional personas can give false confidence and bake in bias, so knowing how to build and use them well matters.
A realistic example
A coworking space app team runs ten interviews. Two clear behaviour patterns emerge. Some members book the same desk every week and want booking to be invisible. Others work there occasionally, mainly for meetings, and need to find a room at short notice.
The team writes two personas: The Regular and The Drop-in. Each has goals, current behaviour, frustrations and three quotes from real interviews. There are no stock photos. The Regular becomes the primary persona because they make up most revenue. In design reviews, the team asks "Does this slow down the Regular?" and catches several unnecessary steps.
Step by step
Start from research
Use interview notes and affinity map themes. If there is no research, do some first.
Find behaviour patterns
Look for variables that split participants: frequency, confidence, goals, context.
Group participants
Cluster participants who behave similarly on the most important variables.
Write each persona
Include goals, current behaviour, frustrations, context and real quotes. Keep it to one page.
Choose a primary persona
Decide whose needs come first and explain why.
Use them
Refer to personas in design reviews, prioritisation and test recruitment.
Common mistakes
Mistake Inventing personas without research.
Instead Base every detail on observed patterns, and label anything assumed as an assumption.
Mistake Filling personas with irrelevant demographics.
Instead Include details only if they change design decisions.
Mistake Making too many personas.
Instead Merge similar ones and choose a primary persona.
Mistake Creating personas and never using them.
Instead Build them into reviews, briefs and test plans.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 45 min
Evidence-based persona
Using your interview notes or affinity map, build one persona.
Steps
- List three behaviour variables that split your participants.
- Group participants on those variables.
- Write a one-page persona with goals, behaviour, frustrations and real quotes.
- Mark any detail that is assumed rather than observed.
Deliverable
A one-page persona with sources noted.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Personas summarise groups of users with similar goals and behaviour.
- They must be grounded in research.
- Behaviour matters more than demographics.
- Keep the set small, choose a primary persona, and use them in decisions.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
- Personas make users memorable for product team members (opens in a new tab)Nielsen Norman Group
- 3 persona types: lightweight, qualitative, and statistical (opens in a new tab)Nielsen Norman Group
Your notes
Marking complete updates your course and roadmap progress.