Marcus Andrey Study
Ler em português Library

UX Foundations · Step 2 · 4 min read

Personas and archetypes

A persona is a short, evidence-based portrait of a group of users that helps a team design for real people instead of "everyone". Where personas came from, the three kinds, what to put in one (and leave out), why demographics mislead, and how to keep personas alive.

"The user" doesn't exist. Some people use your product every day, others once a year; some are experts, some are nervous; some are on a fast laptop, some on a cracked phone. A persona gives one of these groups a name and a face so the team can ask "would Ana manage this?" instead of arguing about an imaginary average user.

What you'll be able to do after reading:

  • Explain what a persona is and where the idea came from
  • Choose between lightweight, qualitative and statistical personas
  • Write a persona built on behaviour and needs, not demographics
  • Use personas in decisions, and avoid the common traps

1. What personas are

Alan Cooper introduced personas to software design in The Inmates Are Running the Asylum (Sams, 1999). NN/g describes a persona as a fictional but realistic description of a typical or target user, built from research (NN/g, Dykes, Personas Make Users Memorable, 2025). "Archetype" is often used for the same thing: NN/g says "Personas and archetypes are functionally the same" (NN/g, Laubheimer, 2022).

A pile of
A persona gives a group of real users a name so the team can talk about them. The name is the easy part; what matters is what they need and do. Photo: Travis Wise from Bay Area, California, United States, Wikimedia Commons, CC BY 2.0.

2. Three kinds of persona

NN/g distinguishes three, by how much research is behind them (NN/g, Laubheimer, 3 Persona Types, 2020):

Kind Built from Good for
Lightweight (proto) What the team already knows; assumptions A start, to be checked and replaced
Qualitative Interviews and observation with real users Most product teams
Statistical Qualitative research confirmed with survey data Large products with many segments

A lightweight persona is honest only if everyone knows it's a guess.


3. What to put in, and what to leave out

KeepGoal

What they want to achieve.

Get reimbursed without losing an evening
KeepContext

When, where, on what.

Twice a year, on a phone, on the train
KeepBehaviour

What they actually do.

Keeps paper receipts in her bag
KeepFrustrations

Where it hurts, in their words.

"I have to relearn the form"
KeepFor design

What this changes in the product.

Remember the last claim
DropDecoration

Details that change no decision.

Age, hobbies, a stock photo
What a useful persona holds, and what to leave out. Diagram: Marcus Andrey, CC BY 4.0.

Leave out what doesn't change design decisions. NN/g warns that "Demographics are troublesome", and that many personas are really "marketing segments being masqueraded as personas" (NN/g, Personas vs. Jobs-to-Be-Done, 2017). Age, gender and a stock photo invite stereotypes; goals, context and behaviour invite good design.


4. A worked example

Ana, the occasional claimer (qualitative persona, from eight interviews):

  • Goal: get reimbursed for work travel without it taking her evening.
  • Context: travels twice a year; does expenses on her phone, on the train home.
  • Behaviour: keeps paper receipts in her bag; forgets the rules between trips.
  • Frustrations: "Every time, I have to relearn the form."
  • What this means for design: remember her last claim, explain the rules in context, let her photograph receipts.

The last line is the point of a persona: it changes what you design.


5. Common mistakes

  • Personas built on assumptions and presented as research.
  • Demographic details that add stereotypes but no design value.
  • Too many personas: nobody remembers seven.
  • A beautiful poster that nobody uses after the workshop.

6. Vocabulary

Term Meaning
Persona A realistic description of a group of users, built from research
Archetype Often used to mean the same thing as persona
Proto-persona A persona built from assumptions, to be checked
Segment A group of customers defined for marketing, often by demographics

7. Try it (no tools needed)

  1. Think of two very different people who use the same product (for example, a banking app).
  2. For each, write: goal, context, one behaviour, one frustration, and what it means for design.
  3. Remove anything that wouldn't change a design decision.

Reflection questions: What did you know from evidence, and what did you guess? Which detail would most change the design?


8. If you already practise

  • Bring personas into decisions: name them in critiques, tickets and test plans ("does this work for Ana on the train?").
  • Pair each persona with the jobs it hires the product for (see User needs and jobs to be done).
  • Indi Young's Practical Empathy is a deeper take on understanding people without stereotypes.

Checklist

Learn more

Books, courses and videos to go deeper

Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

User needs and jobs to be done · Journey maps · Users, tasks and context · Empathy map · Synthetic users and digital twins

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close