Empathy map

An empathy map is a collaborative visualization tool that organizes what a team knows about a particular user segment into a structured format. Typically divided into quadrants representing what users say, think, feel, and do, the map synthesizes research findings into a digestible picture that helps teams develop genuine understanding of user perspectives. It's a tool for building shared mental models, not just documenting facts.

Why it matters

Products fail when teams build for imaginary users instead of real ones. The features that seem obviously valuable to an engineer or product manager may be irrelevant or confusing to actual customers. Empathy maps combat this disconnect by forcing teams to articulate what they actually know about users and confront what they're assuming.

The collaborative nature matters as much as the output. When designers, engineers, product managers, and stakeholders build an empathy map together, they surface different perspectives and create shared understanding. The map becomes a reference point that keeps the team aligned on who they're building for.

The classic quadrants

The traditional empathy map divides user understanding into four areas, each capturing a different dimension of the user experience.

Says captures direct quotes and statements from user research. What do users tell you about their needs, preferences, frustrations, and goals? This quadrant should contain actual language users employ, not paraphrased summaries. The specific words people choose reveal how they frame their problems and what matters to them.

Thinks addresses what users believe but might not articulate directly. What assumptions do they hold? What preoccupies them? What doubts do they have? Often what people think differs from what they say-they might tell you they prioritize security while actually prioritizing convenience. This quadrant requires inference from behavior and context.

Feels explores the emotional dimension. What frustrates users? What excites them? What anxieties do they carry? Understanding emotional states helps teams design experiences that address feelings, not just functionality. A user might need to feel confident, relieved, or in control-and design choices can support or undermine these emotional needs.

Does describes observable behaviors. What actions do users take? What workarounds have they developed? How do they actually spend their time? Behavior often contradicts stated preferences, making this quadrant particularly valuable for grounding the map in reality.

Extended elements

Many teams add additional elements to enrich the basic quadrant structure.

Goals articulates what users are trying to achieve. What does success look like from their perspective? Goals might be task-oriented (complete a purchase) or outcome-oriented (feel prepared for the meeting).

Pains captures frustrations, obstacles, and negative experiences. What makes users' lives difficult? What keeps them up at night? Where do current solutions fall short?

Gains identifies what users want to achieve beyond basic goals. What would delight them? What would exceed their expectations?

These additions-sometimes called "pains and gains"-connect the empathy map to value proposition design and jobs-to-be-done frameworks.

Creating an empathy map

Gathering input

Empathy maps should be grounded in actual research, not imagination. Before creating a map, gather:

The richer the input, the more accurate the map. Teams that build empathy maps from assumptions rather than evidence end up with confident fiction.

Running the session

Empathy mapping works best as a collaborative workshop. Gather cross-functional team members-engineering, design, product, support, sales-and work through the quadrants together.

Start by identifying the specific user segment the map will represent. Trying to map "all users" produces meaningless generalities. Focus on a particular persona, job role, or customer segment with distinct characteristics.

Have participants write observations on sticky notes and place them in the appropriate quadrants. Encourage specificity-"frustrated by slow load times" is better than "frustrated." Direct quotes are particularly valuable.

After populating the quadrants, discuss patterns and surprises. What themes emerge? What contradictions appear? Where does the team lack information? These discussions often generate the most valuable insights.

Synthesizing insights

The goal isn't a beautiful poster-it's shared understanding. After the session, synthesize observations into key insights:

These insights should inform product decisions, design priorities, and communication strategies.

Using empathy maps effectively

Keep them visible. An empathy map filed away provides no value. Display it where the team can reference it during discussions and decisions.

Update as you learn. User understanding evolves with ongoing research. Treat the map as a living document that gets refined, not a one-time artifact.

Use them to challenge assumptions. When someone proposes a feature, ask how it relates to what's on the empathy map. Does it address a real pain? Does it align with observed behavior?

Create multiple maps. Different user segments have different needs. A map for power users won't capture the experience of new customers. Create separate maps for distinct segments.

Common mistakes

Making it up. Empathy maps built from imagination rather than research are worse than useless-they create false confidence. Base every entry on actual evidence.

Being too generic. Statements like "wants a good experience" tell you nothing. Specificity makes empathy maps valuable. What specific experience? Good in what way?

Stopping at the map. Creating an empathy map is not the goal; informing decisions is. Teams that treat map creation as an end in itself miss the point.

Conflating different users. Combining distinct user segments into one map obscures important differences. If users have fundamentally different needs or contexts, they need separate maps.

Forgetting to update. User needs evolve, and initial research may have missed important aspects. Treating an empathy map as permanent truth leads to outdated assumptions.

Empathy maps and other tools

Empathy maps complement other user understanding tools without replacing them.

Personas provide richer demographic and biographical context but can become so detailed that teams lose sight of essential needs. Empathy maps focus specifically on experience and perspective.

Journey maps track user experience across time and touchpoints. Empathy maps capture a moment-in-time perspective that journey maps can then elaborate.

Jobs-to-be-done frameworks focus on what users are trying to accomplish and why. Empathy maps can help identify jobs by revealing what users think, feel, and do in pursuit of goals.

The right tool depends on what questions you're trying to answer. Empathy maps excel at building initial shared understanding; other tools go deeper in specific dimensions.

The deeper purpose

Beyond the mechanics of quadrants and sticky notes, empathy maps serve a more fundamental purpose: they help product teams remember that they're building for real people with real needs, emotions, and constraints. It's remarkably easy to lose sight of this amid the daily pressure of roadmaps, sprints, and stakeholder requests.

Klero supports this user-centric focus by making customer feedback central to product decisions. When teams can see what real users say, think, feel, and do through systematic feedback collection, empathy becomes grounded in ongoing evidence rather than occasional workshops.