In short
An empathy map is a simple canvas that captures what users say, think, do and feel, so a team can build a shared view of their perspective.
What is an empathy map?
An empathy map is a visual snapshot of one user group. The classic version has four quadrants: what does the person say, think, do and feel? Many teams add two more areas for pains and hoped-for gains. The format goes back to Dave Gray and is now widely used in workshops and design thinking sessions.
It is deliberately simple. The goal is not a polished document but a way to sort research observations so that everyone on the team pictures the same person.
Why an empathy map matters
The gap between what people say and what they do is often the most revealing part. In an interview, a customer might claim price does not matter, then abandon checkout the moment shipping costs appear. An empathy map puts contradictions like this in plain sight. It also gets product, design, marketing and engineering onto common ground quickly, before anyone starts debating solutions.
How to use an empathy map in practice
- Fill it with real data: Use notes from interviews, usability tests or support tickets, not gut feeling.
- One map per group: Do not merge audiences that clearly differ, such as admins and end users.
- Flag assumptions: Mark entries that are not backed by evidence yet and plan how you will check them.
- Treat it as a starting point: Turn the map into questions for your next research round or hypotheses for tests.
Common mistakes
The most common mistake is filling the map in an hour from the team's own imagination, without ever talking to users. At that point it only confirms existing opinions. Another mistake is never looking at it again after the workshop. An empathy map is only useful if you keep updating it as new insights come in.
written by
Benedikt Geisberger
Got the theory? Let’s test your product.
We use real user tests to show you where your product gets stuck and what to improve first.