Empathy Map

Thinking Tools3.1 Finding the Current FactsAlso known as Empathy map canvas

Developed by Dave Gray and Scott Matthews at XPLANE and first published in Gamestorming (Dave Gray, Sunni Brown, and James Macanufo, 2010).

A one-page canvas that sorts research notes on a customer into what they say, think, do, and feel, making the gaps between stated and actual behavior visible.

Nine notes from a day with a payroll manager, sorted into says, thinks, does, and feels

Select a note, then the box it belongs in. Says and Does hold what was heard and seen; Thinks and Feels are inferred. Once sorted, read Says against Does: two of her statements are contradicted by what she does. Illustrative.

Items (select one, then a box)
  • Not placedPlacedSaysThinksDoesFeels
  • Not placedPlacedSaysThinksDoesFeels
  • Not placedPlacedSaysThinksDoesFeels
  • Not placedPlacedSaysThinksDoesFeels
  • Not placedPlacedSaysThinksDoesFeels
  • Not placedPlacedSaysThinksDoesFeels
  • Not placedPlacedSaysThinksDoesFeels
  • Not placedPlacedSaysThinksDoesFeels
  • Not placedPlacedSaysThinksDoesFeels

Kind of note

Thought or wordsFeeling or action
Thinks
Says
Feels
Does
Inside herOut in the open

Seen by others?

"The system is fine".Not placed yet."The system is fine".Says: Her words, quoted as she said them. Read this box against Does: the gaps are the findings.Her words in the interview. Contradicted in Does: she rechecks every run in a spreadsheet of her own."The system is fine".Thinks: What she believes and may not say, inferred from what she stressed, avoided, or repeated."The system is fine".Does: What she was seen doing, on screen, in logs, at her desk. When words and actions disagree, trust the actions."The system is fine".Feels: The emotion behind the work, read from tone, pauses, and how she described the worst days."Month-end? No problem".Not placed yet."Month-end? No problem".Says: Her words, quoted as she said them. Read this box against Does: the gaps are the findings.Also her words. Contradicted in Does: badge logs have her at her desk past nine before every run."Month-end? No problem".Thinks: What she believes and may not say, inferred from what she stressed, avoided, or repeated."Month-end? No problem".Does: What she was seen doing, on screen, in logs, at her desk. When words and actions disagree, trust the actions."Month-end? No problem".Feels: The emotion behind the work, read from tone, pauses, and how she described the worst days.Shadow spreadsheet.Not placed yet.Shadow spreadsheet.Says: Her words, quoted as she said them. Read this box against Does: the gaps are the findings.Shadow spreadsheet.Thinks: What she believes and may not say, inferred from what she stressed, avoided, or repeated.Shadow spreadsheet.Does: What she was seen doing, on screen, in logs, at her desk. When words and actions disagree, trust the actions.Seen on her screen: every payroll line copied out and checked by hand. It says the system is not fine.Shadow spreadsheet.Feels: The emotion behind the work, read from tone, pauses, and how she described the worst days.Stays late before runs.Not placed yet.Stays late before runs.Says: Her words, quoted as she said them. Read this box against Does: the gaps are the findings.Stays late before runs.Thinks: What she believes and may not say, inferred from what she stressed, avoided, or repeated.Stays late before runs.Does: What she was seen doing, on screen, in logs, at her desk. When words and actions disagree, trust the actions.From the badge logs, every month this year. It says month-end is a problem.Stays late before runs.Feels: The emotion behind the work, read from tone, pauses, and how she described the worst days.Calls IT before each run.Not placed yet.Calls IT before each run.Says: Her words, quoted as she said them. Read this box against Does: the gaps are the findings.Calls IT before each run.Thinks: What she believes and may not say, inferred from what she stressed, avoided, or repeated.Calls IT before each run.Does: What she was seen doing, on screen, in logs, at her desk. When words and actions disagree, trust the actions.Seen during the visit: a call to confirm nothing changed overnight, every run.Calls IT before each run.Feels: The emotion behind the work, read from tone, pauses, and how she described the worst days.One error, I get blamed.Not placed yet.One error, I get blamed.Says: Her words, quoted as she said them. Read this box against Does: the gaps are the findings.One error, I get blamed.Thinks: What she believes and may not say, inferred from what she stressed, avoided, or repeated.Inferred: she named the chief financial officer four times, each time about a past mistake.One error, I get blamed.Does: What she was seen doing, on screen, in logs, at her desk. When words and actions disagree, trust the actions.One error, I get blamed.Feels: The emotion behind the work, read from tone, pauses, and how she described the worst days.The vendor won't fix it.Not placed yet.The vendor won't fix it.Says: Her words, quoted as she said them. Read this box against Does: the gaps are the findings.The vendor won't fix it.Thinks: What she believes and may not say, inferred from what she stressed, avoided, or repeated.Inferred from her shrug when asked about support tickets.The vendor won't fix it.Does: What she was seen doing, on screen, in logs, at her desk. When words and actions disagree, trust the actions.The vendor won't fix it.Feels: The emotion behind the work, read from tone, pauses, and how she described the worst days.Dread the night before.Not placed yet.Dread the night before.Says: Her words, quoted as she said them. Read this box against Does: the gaps are the findings.Dread the night before.Thinks: What she believes and may not say, inferred from what she stressed, avoided, or repeated.Dread the night before.Does: What she was seen doing, on screen, in logs, at her desk. When words and actions disagree, trust the actions.Dread the night before.Feels: The emotion behind the work, read from tone, pauses, and how she described the worst days.Her tone changed when she described the evening before a run.Relief when totals match.Not placed yet.Relief when totals match.Says: Her words, quoted as she said them. Read this box against Does: the gaps are the findings.Relief when totals match.Thinks: What she believes and may not say, inferred from what she stressed, avoided, or repeated.Relief when totals match.Does: What she was seen doing, on screen, in logs, at her desk. When words and actions disagree, trust the actions.Relief when totals match.Feels: The emotion behind the work, read from tone, pauses, and how she described the worst days.She smiled for the first time showing the moment the spreadsheet agreed with the system.

Your sort matched 0 of 9.Your sort matched 1 of 9.Your sort matched 2 of 9.Your sort matched 3 of 9.Your sort matched 4 of 9.Your sort matched 5 of 9.Your sort matched 6 of 9.Your sort matched 7 of 9.Your sort matched 8 of 9.Your sort matched 9 of 9.

Says
Her words, quoted as she said them. Read this box against Does: the gaps are the findings.
Thinks
What she believes and may not say, inferred from what she stressed, avoided, or repeated.
Does
What she was seen doing, on screen, in logs, at her desk. When words and actions disagree, trust the actions.
Feels
The emotion behind the work, read from tone, pauses, and how she described the worst days.

The sort

  • "The system is fine": Says. Her words in the interview. Contradicted in Does: she rechecks every run in a spreadsheet of her own.
  • "Month-end? No problem": Says. Also her words. Contradicted in Does: badge logs have her at her desk past nine before every run.
  • Shadow spreadsheet: Does. Seen on her screen: every payroll line copied out and checked by hand. It says the system is not fine.
  • Stays late before runs: Does. From the badge logs, every month this year. It says month-end is a problem.
  • Calls IT before each run: Does. Seen during the visit: a call to confirm nothing changed overnight, every run.
  • One error, I get blamed: Thinks. Inferred: she named the chief financial officer four times, each time about a past mistake.
  • The vendor won't fix it: Thinks. Inferred from her shrug when asked about support tickets.
  • Dread the night before: Feels. Her tone changed when she described the evening before a run.
  • Relief when totals match: Feels. She smiled for the first time showing the moment the spreadsheet agreed with the system.

An example

A software company redesigning its payroll product sent two researchers to spend a day with the payroll manager of a six-hundred-person distributor. In the interview she said the system was fine and month-end was no problem.

The researchers came back with forty notes and sorted them on a blank map into says, thinks, does, and feels. The Does box told another story. She kept a spreadsheet beside the system and rechecked every payroll line in it, she stayed past nine the night before each run, and she phoned IT every month before pressing submit. The Thinks and Feels boxes, built from what she stressed and how she said it, held a fear of being blamed for one wrong paycheck. Setting Says beside Does changed the brief. The team dropped its plan for faster data entry and started on a pre-run check that shows her exactly what changed since last month.

Why it works

People describe their work in good order, and they mean it. They report the version they would defend, leave out the workarounds they no longer notice, and spare the interviewer their worries. A stack of raw notes hides this, because each note is true on its own.

Sorting the notes into four boxes, words on top and actions and feelings below, sets what someone says directly against what they do, and the gaps stand out. Those gaps are where design work pays: a spreadsheet kept beside the system is a feature request nobody made. The map also gives a team one shared picture of a person, so the argument moves from whose impression is right to what the evidence on the wall shows.

The thinking behind it

Dave Gray Dave Gray, a designer, developed the empathy map with Scott Matthews at XPLANE, his firm, as a canvas for recording what one person says, thinks, does, and feels. It first appeared in print in Gamestorming (2010), the collection of workshop games he wrote with Sunni Brown and James Macanufo, and in 2017 he published an updated version of the canvas. The map keeps a team's attention on one human being, with the evidence about her laid out in a single view.

Sunni Brown Sunni Brown, a writer and visual thinking consultant who argues for doodling and drawing as ways of thinking, co-wrote Gamestorming: A Playbook for Innovators, Rulebreakers, and Changemakers (2010) with Dave Gray and James Macanufo. The book is a practitioner's collection of structured games for meetings and design work, and it was the first to publish the empathy map from Gray's firm, XPLANE.

How to run it

  1. Pick one person or role per map. A map of "our users" averages away the contradictions that make it useful.
  2. Gather the raw material first. Interview notes, observations, support tickets, and logs, written one fact to a note.
  3. Sort each note into a box. Says and Does take only what was heard or seen; Thinks and Feels are inferences, so mark where each came from.
  4. Read Says against Does. Lay the two boxes side by side and draw a line between each pair that disagree.
  5. Add pains and gains. Under the map, list what the person is trying to avoid and what would count as a win.
  6. Write a design implication for each gap. One sentence per contradiction: what the product or process should do about it.
  7. Check the map with someone in the role. A second interview or a colleague in the same job catches the inferences that went too far.

Where it goes wrong

Thinks and Feels get invented. Teams fill the inner boxes with what they assume, and the map confirms the plan they walked in with. Every note in those two boxes should point to something heard or seen.

The map becomes a persona in disguise. Merging five interviews onto one canvas cancels out the contradictions. Keep one person per map and compare the maps afterward.

The map is made and filed. A finished canvas with no implications written under it changes nothing. Each gap between Says and Does should end in a sentence about what to build or change, with an owner.

When to use something else

  • Personas. When the team needs a lasting description of a user type to design for over months, built from several maps.
  • Customer Journey Mapping. When the problem lies in the sequence of steps a person goes through, beyond one moment of the work.
  • Jobs to Be Done. When the question is what progress the person is trying to make, and what they would hire to make it.

Where it sits in SOLVE eX

Go to the source

Back to the catalog