Skip to content
Tutorials Center
My learning

Topics

Lesson 13 of 36 ยท User Research

Personas and Empathy Maps

Learn how to build research-based personas and empathy maps that guide design decisions, avoid fake stereotypes, and keep your team focused on real user needs.

After research you have notes, quotes and numbers. Teams need a way to remember who they are designing for. Personas and empathy maps are two common tools that turn research into something a team can discuss. Used well, they keep real people in the room. Used badly, they become decoration.

What is a persona?

A persona is a fictional but research-based profile that represents a group of users with similar goals, behaviors and needs. It is not an average person and not a real individual. A typical persona includes:

  • Name and a photo or illustration (a human face helps recall; choose carefully to avoid stereotypes).
  • Short background: role, context, relevant skills.
  • Goals: what they are trying to achieve.
  • Frustrations and pain points.
  • Behaviors: how they currently solve the problem, devices, tools.
  • A representative quote drawn from research.

Keep it to one page. Focus on information that changes design decisions: "checks orders between serving customers, on a phone, one-handed" matters more than "likes jazz".

Persona pitfalls

  • Made-up personas. If they come from assumptions rather than research, they merely confirm what the team already thinks. Base each one on interviews, observations and data.
  • Demographic stereotypes. Age, gender or job title rarely predict needs as well as goals and behavior. Segment by behavior.
  • Too many. Three to five is enough; more become unusable.
  • Never used. A persona nobody references in decisions is wasted effort. Put them on the wall and ask "Would Ana understand this label?"
  • Treating them as the whole truth. They are a communication tool and can go out of date.

A related idea is jobs to be done, which frames users by the progress they want ("get my receipts ready for tax time") rather than by who they are. Many teams use both.

Anti-personas and proto-personas

An anti-persona describes someone you are deliberately not designing for, to prevent scope creep. A proto-persona is an early draft from the team's assumptions, labelled as such and updated or discarded after research. If you create one, mark every assumption as something to validate.

Empathy maps

An empathy map is a quick one-page way to capture what you know about a user in four quadrants (sometimes a fifth section for pains and gains):

Says Thinks
Quotes from research What they believe but may not say
Does Feels
Observed actions Emotions and worries

The value is in the contrast. If someone says "the app is fine" but does a workaround every time and feels anxious, you have found a real problem. You build the map from research notes, often as a group, with sticky notes.

Empathy map

Says Direct quotes
Thinks Beliefs and doubts
1 / 2

A stand-in: building a persona from notes

This stand-in takes labeled research observations and produces a persona summary by picking the most frequent items. Real personas need human synthesis, so treat this as an illustration of tracing every claim back to evidence.

JS Persona from observations (stand-in)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Each line in a persona should trace back to evidence like this. If you cannot say where a claim came from, remove it.

Using personas in practice

  1. Frame decisions: "Would this help Ana check orders in one glance?"
  2. Prioritize features by how many personas benefit.
  3. Write scenarios: short stories of a persona achieving a goal (see user journey maps).
  4. Recruit test participants who match them.
  5. Revisit after new research; retire personas that no longer reflect reality.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What should a persona be based on?

    Research-based personas reflect real goals and behaviors; assumptions only confirm bias.
  2. 2. What does an empathy map compare?

    The four quadrants help reveal contradictions.
  3. 3. Which persona detail is most useful for design decisions?

    Behaviors and context change design; trivia does not.
  4. 4. What is an anti-persona?

    It helps avoid trying to serve everyone.

Summary

  • Personas are research-based profiles of user groups; keep them short and few.
  • Base them on goals and behaviors, not stereotypes, and use them in decisions.
  • Empathy maps capture says, thinks, does and feels and expose contradictions.
  • Mark assumptions and refresh personas as you learn more.

Next: Journey Maps and User Flows