Empathy Map

An empathy map is a simple but powerful visualisation tool used to synthesise research findings into a shared understanding of who your users are and what their experience feels like from the inside. The classic format divides a canvas into four quadrants — Says, Thinks, Feels, and Does — with the user (or user segment) at the centre. Teams fill each quadrant with observations drawn from interviews, usability testing, surveys, or contextual inquiry, creating a composite portrait that goes far beyond demographics or feature requests. The goal is not statistical rigour but empathic alignment: getting everyone in the room to see the world through the user’s eyes.

The format was popularised by Dave Gray at XPLANE and has since become a staple of design thinking workshops. Its strength lies in its accessibility — you do not need specialised research training to contribute to an empathy map, which makes it an ideal tool for cross-functional teams that include engineers, marketers, and stakeholders alongside designers. By externalising assumptions and grounding them in observed behaviour, empathy maps surface the contradictions that are invisible in spreadsheets. A user might say “I love this product” while their behaviour reveals they abandon it after three days. That gap between Says and Does is where the most valuable design insights live.

Empathy maps are closely related to personas but serve a different purpose. A persona is a polished, narrative artefact designed to be referenced throughout a project. An empathy map is a working document — messy, collaborative, and often created in real time during a synthesis session. In practice, empathy maps frequently feed into persona development: the raw observations captured on sticky notes become the evidence base that gives a persona credibility and specificity rather than leaving it as a fictional character built on assumptions.

The most common mistake teams make with empathy maps is filling them in without research. An empathy map populated entirely by the team’s guesses about what users think and feel is just a projection of internal biases dressed up in a framework. The tool only delivers value when the quadrants are grounded in real data — direct quotes from interviews, observed actions from usability sessions, and sentiment patterns from support tickets. When used honestly, empathy maps are a humbling exercise that frequently overturns the team’s comfortable assumptions about their users.

Why it matters

Empathy maps matter because they close the gap between knowing about users and understanding them. Product teams often have access to quantitative data — analytics dashboards, conversion funnels, NPS scores — but these numbers describe what is happening without explaining why. An empathy map forces qualitative depth: what is the user worried about, what language do they use, what are they trying to accomplish beyond the immediate task? This richer understanding changes the kinds of solutions a team generates. Instead of adding another feature to address a symptom, the team can address the underlying mental model that caused the confusion in the first place.

Empathy maps also serve as alignment tools. In any organisation larger than a handful of people, different teams carry different mental images of the user. Marketing sees the aspirational buyer; engineering sees the power user filing bug reports; support sees the frustrated novice. An empathy map created collaboratively from shared research creates a single, grounded reference point that prevents these fragmented views from pulling the product in contradictory directions. This alignment is especially valuable during the early stages of a project, when strategic decisions about scope, priority, and tone are being made and the cost of misalignment is highest.

In practice

• Post-interview synthesis sessions. After conducting a round of five to eight user interviews, gather the team around a whiteboard or digital canvas and build an empathy map in real time. Have each team member write observations on sticky notes and place them in the appropriate quadrant. Discuss conflicts — if one interviewer heard the user say they found the process easy while another observed them struggling, that tension is a signal worth investigating. These sessions typically take 60 to 90 minutes and produce a shared understanding that no written report can replicate.

• Segmented maps for distinct audiences. If your product serves multiple user types — say, a project management tool used by both managers and individual contributors — create a separate empathy map for each segment. The manager might feel pressure to demonstrate team productivity and say things like “I need visibility,” while the contributor might feel surveilled and think “Why does my boss need to see everything?” Mapping both perspectives reveals the tension your design must navigate and prevents you from optimising for one group at the other’s expense. These segmented maps pair naturally with distinct personas.

• Empathy maps as onboarding tools. When a new designer, engineer, or product manager joins a team, walking them through an existing empathy map is one of the fastest ways to transfer user knowledge. Rather than handing them a dense research report, you can point to specific quadrants and say, “Here is what our users actually say during checkout, and here is what they are feeling underneath.” This narrative format sticks in a way that bullet points do not, and it establishes from day one that the team makes decisions grounded in user experience research, not gut instinct.