Empathy Mapping for Design Teams

Empathy mapping is more than a sticky-note exercise; it’s a foundational strategic tool that transforms raw user data into a shared compass for your team. By visualizing what users say, think, do, and feel, you move beyond assumptions and demographic data to uncover the motivations and emotional conflicts that truly drive behavior. This process is critical because it aligns cross-functional teams—from designers to product managers and developers—around a nuanced, human-centered understanding of the people you’re designing for, ensuring that priorities and solutions address real needs and not just surface-level requests.

What an Empathy Map Is and Why It Works

An empathy map is a collaborative visualization used to articulate what we know about a particular type of user. It externalizes knowledge about the user’s internal state, creating a digestible reference point that is far more actionable than a lengthy research report. The classic model divides a user’s experience into four key quadrants: Says, Thinks, Does, and Feels.

The power of this framework lies in its ability to highlight contradictions. Users often state one thing (Says) but exhibit a different behavior (Does). They may rationalize actions with certain thoughts (Thinks) while grappling with conflicting emotions (Feels). Mapping these elements side-by-side reveals these gaps, pushing teams to ask "why" and uncover deeper insights. Ultimately, it builds a shared understanding across the team, ensuring everyone is making decisions based on the same consolidated knowledge, which is invaluable for preventing disjointed design solutions.

Deconstructing the Four Quadrants

To use an empathy map effectively, you must understand the distinct purpose of each quadrant and the type of data that belongs there. This structure forces specificity and prevents vague generalizations.

• Says: This quadrant contains direct, verbatim quotes from user interviews, survey responses, or support tickets. It represents the user’s stated beliefs and self-reported actions. Examples include: "I need a budgeting tool that’s simple," or "I always compare prices on three different sites before buying."
• Thinks: Here, you capture what the user is thinking but might not be voicing aloud. This is inferred from their hesitations, tone, contradictions with their actions, or what they emphasize. For instance, while a user might say they want simplicity, they might be thinking, "I hope this doesn’t mean it’s missing advanced features I might need later."
• Does: This quadrant documents observable behaviors and actions. What does the user physically do? Data comes from usability studies, analytics, or ethnographic research. Examples: "Refreshes the page five times during a slow checkout process," or "Uses keyboard shortcuts instead of the mouse navigation."
• Feels: This is the emotional quadrant, describing the user’s emotional state, often framed as an adjective and a reason. What is their frustration, anxiety, excitement, or hope? Emotional dimensions are critical as they heavily influence loyalty and adoption. An example: "Feels overwhelmed by the number of options on the dashboard," or "Feels relieved when a transaction completes with a clear confirmation number."

The quadrants are not isolated; the tension between them generates insight. A user might say they are confident in using technology (Says) but feel anxious about making a financial mistake (Feels), which explains why they do excessively double-check entries (Does).

How to Build an Empathy Map: A Collaborative Process

Creating an empathy map is a team workshop activity, not a solo task. The collaborative process is what synthesizes diverse perspectives and builds collective buy-in.

1. Define a Specific User Persona or Scenario: Start with a clear focus. Are you mapping "First-time investors using our mobile app" or "Administrators reconciling monthly reports"? Broad maps lead to vague insights.
2. Gather and Distill Research Data: The map must be based on evidence. Prior to the workshop, gather relevant data from interviews, surveys, analytics, and support logs. Have key quotes, observations, and statistics readily available.
3. Run the Workshop: In a physical or digital space, create the four quadrants. Have team members silently write observations from the research data on sticky notes and place them in the appropriate quadrant. This is followed by a group discussion to cluster similar notes, debate placements, and resolve contradictions.
4. Synthesize and Define Insights: Once the quadrants are filled, step back and look for patterns, conflicts, and surprises. The key outcome is to articulate clear insights. For example: "Users feel a lack of trust because the app doesn’t explain why a transaction is pending, leading them to abandon transfers." These insights directly inform design priorities, user stories, and job-to-be-done statements.

From Map to Strategy: Informing Design Decisions

An empathy map is not an endpoint; it’s a springboard for action. The consolidated view of the user’s experience provides a powerful lens for evaluating and generating solutions.

Use the completed map to ask strategic questions: Which emotional dimension (e.g., anxiety, trust) is most critical to address for user retention? What gap between what users say and what they do points to an unarticulated need? For example, if the map shows users feel intimidated by financial jargon but think they should understand it, a design priority might be creating plain-language educational tooltips rather than a simplified interface that hides information.

This visual framework helps influence design priorities and solutions by making user pain points and aspirations undeniable. It can prioritize a feature roadmap, guide content strategy to address fears, or inform interaction design to reduce friction observed in the Does quadrant. It turns empathy from a buzzword into a tangible filter for decision-making.

Common Pitfalls

Even well-intentioned teams can undermine the value of empathy mapping by falling into common traps.

• Pitfall 1: Guessing Instead of Using Data. Filling the map with team assumptions or stereotypes creates a map of your biases, not your user. This invalidates the entire exercise.
• Correction: Rigorously anchor every sticky note in a research artifact. Ask, "Which interview quote supports this?" or "Which analytics funnel shows this behavior?"
• Pitfall 2: Mapping a Generic "User." Creating one map for "all users" results in bland, averaged insights that are useless for making specific design choices.
• Correction: Always map for a specific persona or user segment in a defined scenario. Create multiple maps if you have distinctly different user types.
• Pitfall 3: Treating It as a One-Time Activity. Sticking the map on the wall and never referencing it again wastes the effort and fails to maintain team alignment.
• Correction: Treat the map as a living document. Revisit and update it with new research. Reference it in sprint planning, design critiques, and prioritization meetings to ground discussions in user reality.
• Pitfall 4: Neglecting the "Feels" Quadrant. Teams often focus on observable actions and statements, sidelining emotions as "soft" data.
• Correction: Champion the emotional data. Emotions drive decisions. Spend dedicated time brainstorming feelings, as addressing a user's anxiety or building their confidence can be a more powerful design lever than optimizing a single click.

Summary

• An empathy map is a visual framework that synthesizes user research into four quadrants: Says, Thinks, Does, and Feels, building a holistic picture of the user’s experience.
• Its primary value lies in revealing gaps between user statements and behaviors, forcing teams to uncover deeper motivations and unarticulated needs.
• The process is inherently collaborative, transforming individual research findings into a shared understanding that aligns cross-functional teams.
• Paying close attention to the emotional dimensions in the Feels quadrant is crucial, as emotions are key drivers of user loyalty and decision-making.
• The final map must directly influence design priorities and solutions, acting as a constant reference point to ensure decisions are user-centered and evidence-based.