In the fast-paced world of product development, assumptions are dangerous. We often believe we understand our users because we’ve spoken to a few or used the product ourselves. But true product-market fit rarely emerges from assumptions—it comes from a deep, structured understanding of your users. That’s where Empathy Mapping comes in.
What Is Empathy Mapping?
Empathy Mapping is a simple, collaborative tool that helps teams understand and visualize what users think, feel, see, say, hear, and do. It’s an effective method for building empathy with your target audience and aligning teams around user needs and behaviors before you start building anything.
Developed by Dave Gray and widely adopted in design thinking and agile methodologies, the empathy map forces teams to step out of their internal lens and into the real world of the customer. The result? Better-informed decisions, better-designed products, and fewer surprises down the road.
Why Empathy Mapping Matters
Before investing time and money into design and development, you need to confirm you’re solving the right problem. Empathy Mapping:
- Uncovers unspoken needs that users may not articulate directly.
- Aligns teams around a shared understanding of the user.
- Guides prioritization by focusing on what matters most to your audience.
- Improves product usability by grounding ideas in reality.
It also shortens feedback loops—because you’re validating ideas early and often based on real user emotions and experiences, not gut feeling.
The Four Quadrants of an Empathy Map
Empathy Maps are usually divided into four main quadrants (some models include six), each focusing on a specific aspect of the user’s experience.
1. Says
What does the user literally say out loud in interviews or testing sessions?
“I wish this was faster.”
“I use this every day for my reports.”
These direct quotes help anchor the map in actual user dialogue and reveal perceptions and expectations.
2. Thinks
What is the user thinking privately? What might they not say aloud?
“This is frustrating, but I don’t want to look dumb.”
“Is this really the best tool for the job?”
This quadrant invites us to consider user motivations, doubts, and cognitive biases.
3. Does
What actions does the user take? What behaviors do we observe?
Clicks the “Back” button often.
Spends a lot of time searching for help.
This helps identify pain points in workflows or interactions.
4. Feels
What emotions does the user experience?
Anxious while waiting for a report to load.
Relieved after getting an alert confirmation.
Mapping these feelings helps identify moments of delight or frustration that may impact product adoption or churn.
(Sometimes two additional quadrants—“Hears” and “Sees”—are added to capture outside influence and environment.)
When and How to Use Empathy Mapping
Empathy Mapping is most useful early in the discovery phase, typically after user interviews or contextual inquiries. It’s often used in product design sprints or brainstorming sessions.
Here’s how you can create an empathy map with your team:
- Choose a specific user persona or user segment.
- Gather qualitative data through interviews, surveys, support tickets, or field observations.
- Create the map collaboratively on a whiteboard or virtual collaboration tool.
- Populate each quadrant based on real quotes and observations—not assumptions.
- Discuss and reflect: What surprises you? What patterns emerge? What gaps still exist?
By the end, your team will walk away with a clearer, shared understanding of what your user actually goes through—and why your solution needs to meet them where they are.
Common Pitfalls to Avoid
- Skipping research: If your map is based on assumptions, it can be misleading.
- Mapping too generally: Empathy maps should focus on a specific type of user with a specific goal.
- Treating it as a one-time exercise: User behavior evolves. So should your empathy maps.
Bringing Empathy to Product Decisions
Empathy Mapping isn’t just a UX tool—it’s a strategic lever. It can influence product positioning, feature prioritization, onboarding flows, and customer support approaches.
For example, if your users are overwhelmed when using your analytics dashboard, you might discover through the “Feels” quadrant that they’re intimidated by data. This insight could lead to simplified reporting, better onboarding, or even adding educational nudges—all of which improve engagement and retention.
Final Thought
In the age of data, we often focus on what users do but forget to understand why. Empathy Mapping fills that gap by humanizing the numbers and grounding innovation in real user emotion. Before you build another feature or revamp another screen, ask yourself:
“Do we truly know what our users are experiencing?”
If the answer is “not really,” it’s time to map it out.