Where a persona says who a user is, the empathy map captures what it feels like to be them — what they think, see, hear, say, and do around the problem you're solving.
▸ Try the interactive toolThe Empathy Map, created by Dave Gray at XPLANE, is a collaborative tool that builds shared team understanding of a user's inner world. Where a persona describes who a user is structurally — role, goals, frustrations, metrics — the empathy map goes deeper into what it actually feels like to be that person in relation to the problem your product solves.
It's usually built as a team workshop, which is half the point: the act of filling it in together surfaces the different assumptions team members hold about the user and forces them into one shared picture. The classic quadrants capture what the user thinks and feels, sees, hears, and says and does — often with their pains and gains called out explicitly.
Think & feel — their inner thoughts, worries, aspirations
See — their environment, what's in front of them
Hear — what others around them say, influences
Say & do — their observable behaviour and words
(plus explicit pains and gains)
Personas can become structural and dry — a list of attributes. The empathy map restores the emotional reality that actually drives behaviour, and aligns the team on it.
| The shortcut | What it costs | What it gives you instead |
|---|---|---|
| Structural-only understanding | A persona's attribute list misses the emotional drivers of behaviour. | The map captures what the user thinks and feels, which is what moves them. |
| Divergent team assumptions | Each team member quietly pictures the user differently. | Building the map together forces one shared, explicit picture. |
| Designing from the outside | Teams design for observable behaviour without understanding motivation. | The think/feel quadrant surfaces the why behind the what. |
| Pains and gains left implicit | The user's real frustrations and hopes stay vague. | The map calls out pains and gains explicitly, feeding the value proposition. |
An empathy map is for a single persona at a time. Choose the one you're trying to understand more deeply — usually the primary.
Gather the cross-functional team and fill the quadrants together. The disagreements that surface are as valuable as the agreements — they reveal mismatched assumptions.
Populate each quadrant from research and observation. Push hardest on think/feel — it's the least obvious and the most decision-relevant.
Explicitly extract the user's frustrations (pains) and hopes (gains) from the quadrants. These feed directly into the value proposition canvas.
An empathy map that stays on the wall is wasted. Turn the sharpest insights — especially from think/feel — into design and roadmap implications.
A team thought they understood their primary user until they built an empathy map together — and discovered they disagreed sharply on what the user was actually feeling when they used the product. Some assumed confidence; others, anxiety.
Working it out as a group, grounded in interview quotes, they landed on the truth: the user felt quietly judged and afraid of looking incompetent. That single insight in the think/feel quadrant reframed several design decisions — from tone of copy to error handling — in ways the structural persona alone had never prompted.
The deliverable is the filled quadrant map for one persona, with pains and gains extracted — a shared emotional portrait, not an attribute list.
| Quadrant | Captures | Feeds into |
|---|---|---|
| Think & feel | Inner thoughts, worries, hopes | The why behind behaviour |
| See | Their environment & options | Context for design |
| Hear | Influences & others' voices | Messaging & trust |
| Say & do | Observable behaviour | What to actually support |
A persona tells you what the user is; the empathy map tells you what it's like to be them. Behaviour follows from how people think and feel — and that inner world is exactly what attribute lists leave out.
The dual value is the catch worth remembering: the map is a tool for understanding the user and a tool for aligning the team. Built alone, it's a deeper persona; built together, it's a forcing function that drags every team member's private, slightly different mental model of the user into one shared, explicit picture. The think/feel quadrant usually does the heavy lifting — because the emotional truth it surfaces (fear, pride, anxiety, hope) is what actually drives the behaviour everyone else is trying to design for.
Half the value is the team alignment. Build it as a workshop, not a solo document.
The emotional quadrant is the hardest and most valuable. Don't rush it to fill the easy ones.
An empathy map that doesn't change a decision is decoration. Extract implications.
Think/feel should come from real research and quotes, not the team's projection.
The empathy map is the emotional layer beneath a persona (Tool 12) — same user, richer inner world.
The pains and gains it surfaces flow straight into the VPC customer profile (Module 1, Tool 06).
Its content comes from interview data — the think/feel quadrant especially needs real quotes.
As a workshop tool, it's also a stakeholder-alignment device — connecting to the communication tools in Module 6.
Pick a user type and sketch the four quadrants: what do they think and feel, see, hear, and say and do around the problem? Push hardest on think/feel.
Extract one pain and one gain. Then ask: does the emotional truth in think/feel change any design decision you'd make?
If the think/feel quadrant reveals something the structural persona never would — a fear, a quiet hope — you've found exactly why the empathy map exists.