Empathy Maps: Understanding Users at a Deeper Level
An empathy map is a visual framework for understanding a user's needs, feelings, and environment by exploring what they think, feel, see, say, do, and hear.
What is an Empathy Map?
Imagine sitting with a user for a day, observing everything they do, listening to everything they say, noticing what frustrates them, what excites them, what others influence their decisions. An empathy map is that day of observation, organized visually. You divide a page into sections: What does the user think? What do they feel? What do they see around them? What do they say to others? What actions do they take? Who influences their decisions? By systematically exploring each dimension, you move beyond assumptions into genuine understanding of what users actually need, what obstacles they face, and what drives their decisions. It’s not about data—it’s about meaning. Data tells you how many users abandoned at checkout; empathy mapping tells you why they abandoned and what would make them stay.
Why is it important?
Replaces assumptions with observation: Designers often think they understand user needs without actually talking to users. Empathy maps force you to base understanding on evidence—what users actually said, did, and felt—not what you assumed.
Uncovers unarticulated needs: Users often don’t consciously recognize their own pain points. Asking “what frustrated you?” yields generic answers. Observing what makes them pause, sigh, or workaround problems reveals needs they never mentioned. Empathy maps surface these hidden needs.
Aligns teams on user understanding: When different team members research independently, they form different mental models of users. Empathy maps create a shared reference point. Everyone sees the same user insights and can discuss from that common ground.
Identifies design priorities: Understanding not just what users need, but what they feel, think, and value reveals what matters most. A technical improvement means nothing if it doesn’t address an emotional or environmental need that actually drives behavior.
Empathy Map Dimensions
Think: What’s on the user’s mind? What occupies their attention when not using your product? What are their goals, concerns, and priorities? What do they believe about the category?
Feel: What emotions does the user experience? What frustrates or excites them? What are they anxious about? What brings them satisfaction? Emotional drivers often trump logical ones.
See: What’s in the user’s environment? What do others around them do or say? What media do they consume? What alternatives and competitors do they notice? What’s their context?
Say: How does the user describe their problem to others? What language do they use? What would they tell a friend about your product? What do they claim to want?
Do: What actions does the user take? What’s their actual workflow? What do they try when something isn’t working? Actual behavior often differs from claimed behavior.
Hear: Who influences the user? What do trusted voices say about your category? What are influencers, friends, or experts claiming? What industry trends are they hearing about?
How to Build an Empathy Map
Start with a specific user persona — Pick a real representative user or research participant, not a generic “user.” Specific helps; abstract doesn’t.
Conduct observation and interviews — Talk to actual users. Better: observe them using your product and competitors’ products in their real context, then discuss your observations with them.
Fill each dimension separately — Resist summarizing. For “think,” list specific thoughts. For “feel,” name specific emotions. Specificity reveals insight; vagueness reveals missing research.
Identify contradictions — If a user says one thing but does another, investigate the gap. These contradictions are where design problems hide. Maybe they claim to want simplicity but actually want powerful options.
Extract design implications — From completed empathy maps, identify what matters to the user. What unmet needs emerged? What emotional needs does your design need to serve? These become your design priorities.
Mentor Tips
Empathy maps aren’t user personas: Personas are composite characters representing user segments. Empathy maps are deep dives into specific individuals or archetypes. You might create one persona representing five actual users, but an empathy map for a single representative user.
Separate “what they said” from “what you interpreted”: In the diagram, distinguish between direct quotes and your interpretations. Users won’t literally say “I feel frustrated with complexity.” Translate observed behavior into emotional language, but track the difference.
Contradictions are most interesting: If someone says they want one thing but does another, you’ve found the real problem. Users rarely lie; they’re just unconscious of their actual priorities. Contradictions reveal priorities.
Update maps after launch: Empathy maps are not one-time exercises. As you gather actual usage data and feedback, update maps to reflect reality. Maps from assumption are nice; maps from evidence are useful.
Resources and Tools
Books & Framework
- This is Service Design Doing by Marc Stickdorn — Contains detailed empathy mapping methodology alongside other service design research techniques
Research/Application Tools
- User Interviews — The best empathy maps emerge from direct conversation and observation
- Personas — Combine empathy maps with personas for comprehensive user understanding