Empathy Map | Agile Scrum Master
Empathy Map is a collaborative visual tool used in discovery to capture what a user says, thinks, does, and feels about a situation, aligning the team on needs and assumptions. It improves decisions by making beliefs explicit, revealing pains and gains, and informing personas, journeys, and backlog prioritization without jumping to solutions too early. Key elements: target user and scenario, Says/Thinks/Does/Feels quadrants, evidence vs assumptions, themes and insights, and agreed implications for experiments and stories.
How Empathy Map works
Empathy Map is a collaborative canvas used to build a shared understanding of a specific user segment in a specific scenario. It captures what the user says, thinks, does, and feels so the team can align on needs, constraints, and decision drivers before exploring solutions. Teams typically create it in a short workshop with product, design, engineering, and relevant stakeholders, then refine it as new evidence arrives.
In Agile product work, Empathy Map is a lightweight learning loop: make beliefs transparent, inspect them against evidence, and adapt what you do next. It helps teams separate observations from assumptions, surface the riskiest unknowns, and translate them into hypotheses, discovery experiments, and thin-sliced backlog items. It delivers value when it changes decisions—what to test next, what to stop, what to simplify—not when it merely looks complete.
Purpose and benefits of Empathy Map
Empathy Map improves product decisions by anchoring discussion in user reality. It is especially useful when teams hold conflicting views about users, or when “requirements” are framed as solutions rather than problems.
- Alignment - creates a shared view of the user so conversations move from opinion to evidence and learning.
- Clarity of needs - separates user goals and pains from proposed features, internal constraints, and technical preferences.
- Better prioritization - highlights the problems worth solving and the assumptions that should be tested first.
- Improved collaboration - gives cross-functional teams a common language for user-centered decisions and trade-offs.
- Reduced solution bias - keeps focus on what the user is trying to achieve before debating how to implement.
- Faster feedback - clarifies what to learn next so discovery work becomes smaller, timeboxed, and easier to inspect.
Empathy Map also supports communication. When teams need to explain why a backlog item matters, the map provides a concise narrative grounded in user behavior and motivation rather than internal preference.
Core structure of an Empathy Map
Empathy Map is commonly represented as four quadrants, sometimes extended with additional fields. The key is to keep a clear distinction between evidence and assumptions and to avoid generic statements that cannot be tested.
- Says - direct quotes or close paraphrases from interviews, feedback, or observed daily work.
- Thinks - beliefs, concerns, and mental models that influence decisions, marked as assumptions when not validated.
- Does - observable behaviors and actions, including workarounds, repeated patterns, and what happens under constraints.
- Feels - emotional states such as anxiety, confidence, frustration, or relief associated with the scenario.
- Pains - obstacles, risks, and frictions that block the user from achieving their goal.
- Gains - desired outcomes and benefits that indicate what success looks like for the user.
Some teams also add “Sees” and “Hears” for environmental cues, or “Jobs” to connect to Jobs to Be Done. Add fields only when they sharpen the next decision. Always anchor the map to one segment and one scenario; without this, the canvas becomes generic and stops producing actionable learning.
Steps to Create an Empathy Map
Empathy Map works best when it is created quickly and then validated through short learning loops. A typical flow is:
- Choose the target and scenario - define the segment and situation, including goal, constraints, and what “success” means for the user.
- Gather evidence - bring interview notes, observation snippets, analytics, support themes, and real artifacts to ground the discussion.
- Populate the quadrants - add short statements and tag each as evidence or assumption.
- Cluster themes - group notes to reveal patterns, tensions, and decision drivers that are most likely to affect outcomes.
- Extract insights - agree a small set of insights that explain behavior and highlight the biggest uncertainties.
- Derive next actions - convert insights into questions, hypotheses, and experiments, plus the smallest backlog slices needed to test them.
- Validate and refine - run the smallest ethical test to confirm or refute the riskiest assumptions and update the map with what changed.
Treat the map as a living artifact, not a one-time deliverable. It is “done” only when it enables a better decision, such as selecting the next hypothesis to test, shaping a story slice, or removing an assumption that was driving rework.
Facilitating an Empathy Map workshop
Empathy Map outcomes depend heavily on facilitation. The facilitator keeps the group focused on one user and scenario, pushes for evidence-based statements, and prevents the session from becoming a design debate.
- Timebox the session - keep momentum with short rounds per quadrant and a clear end state.
- Separate evidence from assumptions - label items clearly so the team can plan validation and avoid false certainty.
- Use real artifacts - bring quotes, screenshots, recordings, analytics, or support excerpts to keep discussion grounded.
- Include constraints early - surface operational and technical realities so experiments and slices remain deliverable.
- End with decisions - capture the key insights plus the next experiments or backlog actions, with owners and a review point.
For remote teams, Empathy Map works well with digital whiteboards. Keep notes short, avoid storytelling in long sentences, and close with a brief check for shared understanding.
Using Empathy Map with Agile planning
Empathy Map can directly improve backlog refinement and prioritization by connecting user reality to what the team does next. Themes become hypotheses and experiments, then delivery work is thin-sliced based on what is most uncertain and most valuable to learn. This reduces the risk of shipping “complete” work that fails to improve outcomes.
Empathy Map also connects well to personas and customer journey mapping. The map adds depth about motivations and emotions, while a journey map shows end-to-end steps and touchpoints. Together, they help shape user stories and acceptance examples (for example with Three Amigos and Given-When-Then) that reflect real constraints and decision drivers. When the map reveals multiple distinct motivations, it often signals the need to segment personas or split the backlog so learning is tested with the right user group.
Best Practices
- Ground in evidence - start from real data and tag assumptions that still need validation.
- Keep it specific - focus on one segment and one scenario so signals stay strong and testable.
- Write observable notes - prefer quotes, behaviors, and situations over abstract traits.
- Limit WIP - choose a small number of uncertainties to test next to keep feedback fast.
- Inspect and adapt - revisit the map after new learning and update decisions and backlog ordering accordingly.
Misuses and fake-agile patterns
Empathy Map is often misused as a workshop output that is never validated. This creates false confidence, reinforces solution bias, and produces backlog items that look plausible but do not improve outcomes.
- Generic personas - looks like mapping “everyone” or “the average user”; it hides trade-offs and weakens signals; choose a specific segment and scenario that is narrow enough to learn quickly.
- Assumptions presented as facts - looks like confident statements with no source; it drives the wrong work and increases rework; tag assumptions and test the riskiest ones first.
- Solution-first mapping - looks like features written into quadrants; it skips understanding and narrows options too early; capture needs and drivers first, then explore solutions separately.
- One-and-done artifact - looks like creating the map once and never revisiting it; it freezes learning; update it after research and after experiments, and remove assumptions that no longer hold.
- Performative workshops - looks like lots of sticky notes with no decisions; it creates activity without learning; timebox tightly, bring evidence, and end with a small set of experiments and owners.
Empathy Map is a collaborative canvas that captures what a user says, thinks, does, and feels to align teams on needs and decisions during product discovery