Marcus Andrey Study
Ler em português Library

Framework · Facilitation techniques · 3 min read

Empathy map

Says / Thinks / Does / Feels for a user role, to align stakeholders on who the user is, based on real research.

SSays

What the user says out loud. Use real quotes from research.

e.g. "I just need the numbers."
TThinks

What they think but may not say. Infer from research.

e.g. "If this is wrong, I get blamed."
DDoes

What you observed them doing: actions and workarounds.

e.g. Copies data into a spreadsheet
FFeels

Their emotions: worries, frustrations, what makes them proud.

e.g. Anxious at month-end

One map per user role · mark where Says and Does contradict

An empathy map puts one user role in the centre and shows what they say, think, do and feel, based on research.

Use it when

  • Stakeholders talk about "the user" but mean very different people, and you need one shared picture.
  • You have just finished interviews or field visits and want the team to absorb the findings in 20–30 minutes.
  • A new product manager or developer joins, and you want to introduce the main user roles quickly.

How to use it

  1. Pick one user role. Write the role and a short context in the centre, for example "Shift planner, end of the day". Make one map per role; don't mix roles. Output: one role in the centre of a four-part board.
  2. Fill Says and Does from research. Add real quotes to Says and observed actions and workarounds to Does. Mark the source on each sticky. Output: evidence-based stickies in two quadrants. About 10 minutes.
  3. Infer Thinks and Feels. Based on what users said and did, write what they probably think but don't say, and how they feel. Link each inference to evidence. Output: Thinks and Feels quadrants with sources. About 10 minutes.
  4. Highlight contradictions. Look for gaps between Says and Does, for example "says the tool is fine" but "exports everything to a spreadsheet". Mark them clearly. Output: 2–3 marked contradictions.
  5. Agree what it means. Ask: "What surprised you? What does this mean for our design?" Write 2–3 takeaways and any open questions for more research. Output: takeaways and research questions. About 5–10 minutes.

Worked example

After 5 field visits, a UX lead runs a 30-minute empathy map session with a product manager, 2 developers and a designer for the "shift planner" role on an internal operations platform.

Quadrant Examples from the board
Says "I just need the numbers." · "The tool is fine, I'm used to it."
Thinks "If this plan is wrong, I get blamed." · "The totals might be wrong."
Does Exports the plan to a spreadsheet every day · Writes notes on paper for the next shift
Feels Anxious at the end of the month · Proud when the plan runs without problems

Contradiction: planners say the tool is fine, but every one of them rechecks the totals outside it. The team agrees on a takeaway: trust in the data matters more than speed. The product manager adds "Why don't planners trust the totals?" to the research plan.

Watch out for

  • Invented content. A map filled from assumptions only confirms what the team already believes. Mark any sticky without a source as an assumption.
  • One map for everyone. Planners and managers have different days, tasks and worries. Make one map per role.
  • Skipping the contradictions. The gap between Says and Does is often the most useful insight. Look for it on purpose.
  • A map nobody uses. Link the takeaways to a decision or research question, or the map stays on the board.

Template

Draw four quadrants around the role, or use this as a list.

EMPATHY MAP                                       20–30 min
User role: __________________   Context: __________________
Research sources: __________________________________________

SAYS (real quotes)               THINKS (inferred, with source)
-                                -
-                                -

DOES (observed actions)          FEELS (emotions, with source)
-                                -
-                                -

Contradictions (Says vs Does):
1.
Takeaways for design:
1.
Open research questions:
1.
Source
Dave Gray (XPLANE)

Books to go deeper

  • GamestormingDave Gray, Sunni Brown & James MacanufoBook · 2010
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close