Menu

Research

Empathy Mapping

A practical UX research synthesis method for visualising user perspective across thoughts, emotions, statements, and actions.

How to run empathy mapping to turn qualitative insights into a shared understanding of user mindset, pain points, and opportunities.

4 min read

What it is

Empathy mapping is a UX and method used to visualise what users say, think, feel, and do in a given .

It involves creating a collaborative visual representation that organises from interviews, , or other into key quadrants: Say, Think, Feel, and Do.

The focus is on capturing user perspective and emotions to inform design decisions.

Key takeaway

The goal is to develop a shared understanding of users, highlight pain points, and identify opportunities to improve the experience.

When to use it

Use this method when you need to humanise user .

It is most useful when:

you want to understand user motivations and frustrations
designing new features, products, or services
you have qualitative research from interviews or observations
you need to align the team on user needs
you want to identify opportunities for innovation

It is less useful when:

only quantitative data is available
users’ context or emotions are not relevant
Empathy mapping is often used alongside personas, journey mapping, and thematic analysis.

How to run it

Set up properly

Be clear which user group the map is for, which it draws on, and what it is meant to inform. A map covering everybody describes nobody.

Prepare the in advance. An empathy map built from memory records the team's assumptions in a format that makes them look like findings.

Run the method

Empathy mapping is collaborative and visual. It works when it is a way of arranging evidence, and misleads when it becomes a way of imagining a user.

  1. Divide the board into Says, Thinks, Feels and Does, and keep the distinction honest: what someone says is evidence, what they think is .
  2. Place real into the quadrants, attributing each to its source so the map can be challenged later.
  3. Discuss and contradictions, particularly where Says and Does disagree. That gap is usually the most useful thing on the board.
  4. Highlight , motivations and opportunities as you go, rather than leaving interpretation to the end.
  5. Mark anything placed from assumption rather than evidence. Those are your questions for the next round.

Focus on understanding the person, not cataloguing their . The map is a means of building shared understanding, not an artefact to file.

Capture and make sense of it

The value comes from synthesising perspective. After mapping, document:

  • Key and themes, separated from the assumptions
  • Gaps that need validating before they inform a decision
  • How the findings change specific design or content choices
  • Where Says and Does diverged, and what that implies

Share the map with the team for . Its main value is that several people now hold the same picture, which is harder to achieve than it sounds.

Key takeaway

Use this to design experiences that resonate with users.

What to look for

Focus on:

User statements: what users actually say
Thoughts: what they think but may not voice
Feelings: emotions and frustrations affecting behaviour
Actions: observable behaviours and patterns
Opportunities: moments to improve experience or meet unspoken needs

Where it goes wrong

Most issues come from:

If the map is superficial, it provides little guidance.

Filling the quadrants from memory, which records assumption as finding
Blurring what people said with what you inferred they thought
Smoothing over contradictions, when the gap between saying and doing is the finding
Building it once and never revisiting it as research arrives
Producing an artefact for the wall rather than an input to a decision

What you get from it

Done properly, this method gives you:

A shared picture of one audience, held by several people at once
The gap between what people say and what they do
Assumptions made visible and marked for validation
A basis for design and content decisions that a team already agrees on

Key takeaway

It helps you create empathetic, user-centred experiences.

Get in touch

If this sounds like something you need, we can help you create empathy maps that uncover what users truly think, feel, and do, guiding design decisions that actually resonate.

No guesswork. No assumptions. Just design with empathy.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is empathy mapping in UX?

It is a method for visualising what users say, think, feel, and do to guide design decisions.

When should you use empathy mapping?

After qualitative research, during ideation, or when defining user needs.

What data do you need?

Interviews, observations, feedback, or notes capturing user perspectives.

What does an empathy map give a team?

It helps designers understand the user holistically and identify opportunities for improvement.

Does empathy mapping improve UX?

Yes. It ensures products and content meet real user needs and emotions.

Quick take

If you don’t understand what users feel, think, or do, you’re designing in the dark. Map empathy to see through their eyes.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer