User research often results in a mountain of data that is difficult to synthesize. Transcripts, heatmaps, and survey results are valuable, but they frequently fail to bridge the gap between "what the data says" and "how the user actually feels." An empathy map template serves as the vital link in this process. It is a collaborative visualization tool used to articulate what a team knows about a specific type of user. It shifts the focus from demographic spreadsheets to a shared human understanding, ensuring that product decisions are rooted in the user's reality rather than internal assumptions.

The primary goal of an empathy map is to create a common ground for design teams, product managers, and stakeholders. By organizing user insights into specific quadrants—what they say, think, do, and feel—teams can identify where their knowledge is thin and where their product might be failing to meet emotional or functional needs.

Understanding the Four Core Quadrants of an Empathy Map

A standard empathy map template is divided into four quadrants with the user or persona at the center. Each quadrant represents a different facet of the user's experience during their interaction with a product or service.

What the User Says

The "Says" quadrant contains direct quotes and verbatim statements. This is the most straightforward section because it relies on explicit data gathered during user interviews or focus groups. When filling out this section, it is crucial to use the user's own language rather than paraphrasing it into corporate jargon.

For instance, if a user says, "I'm always worried I'll click the wrong button and delete my work," that exact sentence belongs here. In our sessions, we have found that keeping these quotes raw helps maintain the emotional weight of the feedback during later design phases. Common entries in this quadrant include:

  • "I want something that just works without a manual."
  • "Why is the pricing so hidden on the website?"
  • "The mobile app feels much slower than the desktop version."

What the User Thinks

The "Thinks" quadrant is more nuanced. It represents the user's internal monologue—the things they might not be comfortable saying out loud. Capturing this requires "reading between the lines" of an interview. A user might say the UI looks "fine," but their hesitation or facial expression might suggest they find it outdated.

In a recent project involving a financial management tool, we noticed users often paused before clicking "Submit" on a transaction. While they didn't say they were scared, we recorded their "Think" as: "Is this transaction reversible if I made a mistake?" Identifying these unspoken anxieties is often where the most significant product improvements are born.

What the User Does

This quadrant focuses on observable behaviors. What physical actions does the user take? How do they interact with the interface? This data usually comes from usability testing, screen recordings, or field observations.

It is important to note the specific sequence of actions. For example:

  • The user refreshes the page three times when the loader takes more than two seconds.
  • The user ignores the primary CTA and instead searches for a "Help" link.
  • The user opens a separate calculator app to verify the numbers on your dashboard. These behaviors often reveal gaps in the product's functionality that the user has learned to work around.

What the User Feels

The "Feels" quadrant captures the user's emotional state. Is the user frustrated, excited, confused, or relieved? Emotions are usually described with adjectives and are often tied to specific "Pains" or "Gains."

When we facilitate empathy mapping workshops, we encourage teams to use a "feeling wheel" to get more specific than just "happy" or "sad." Is the user overwhelmed by the number of options, or are they anxious about security? Understanding the specific shade of emotion allows designers to adjust the tone of the copy, the color palette, and the overall flow to better align with the user's psychological state.

Expanding the Empathy Map Canvas

While the original four-quadrant model is highly effective, modern design thinking often utilizes an expanded "Empathy Map Canvas." This version adds context regarding the user's environment and their ultimate goals.

What the User Sees

The "Sees" section looks at the user's surroundings. What is competing for their attention? What are their colleagues using? What do they see on social media regarding this problem space? In a B2B context, this might include the cluttered spreadsheets they have to use daily or the sleek advertisements of a competitor.

What the User Hears

This section focuses on how the environment influences the user through communication. What are their friends or bosses saying? What do influencers or trade publications claim about the "best" way to solve their problem? If a user "hears" from their IT department that cloud-based tools are risky, that hearsay will color their entire experience with your SaaS product.

Pains and Gains

Many teams add two horizontal sections at the bottom of the map:

  • Pains: These are the obstacles, frustrations, and risks the user faces.
  • Gains: These are the goals, hopes, and definitions of success. By explicitly calling these out, the empathy map transforms from a purely descriptive tool into a strategic one. It highlights exactly what the product needs to "fix" (Pains) and what it needs to "amplify" (Gains).

How to Conduct a Collaborative Empathy Mapping Workshop

Creating an empathy map should never be a solo activity performed by a single product manager. Its greatest value lies in the alignment it creates across cross-functional teams. Here is a practical framework for running a 90-minute workshop.

Phase 1: Preparation and Data Gathering

Before the meeting, ensure you have a specific persona or user segment in mind. Empathy mapping "all users" results in a generic, useless document. You need actual data—interview transcripts, support tickets, or ethnographic notes.

In our experience, bringing raw data to the workshop prevents the session from devolving into a "guessing game." If you don't have enough data to fill a quadrant (often the "Thinks" or "Feels" sections), it is a clear indicator that your team needs to pause and conduct more primary research.

Phase 2: Individual Brainstorming (10-15 Minutes)

Give every participant a stack of sticky notes (or access to a digital whiteboard). For the first 15 minutes, have everyone work in silence. They should write down one observation per sticky note and place it in the corresponding quadrant. Silence is important here to avoid "groupthink," where the most senior person in the room dictates the narrative.

Phase 3: Cluster and Discuss (30-40 Minutes)

Once the board is filled with notes, the facilitator should lead the team in grouping similar observations. This is the "synthesis" phase. As you move notes around, discuss the why behind them.

One of the most powerful moments in these workshops occurs when a developer realizes that a feature they thought was "simple" is actually a major "Pain" for the user. This shared realization is what builds true empathy.

Phase 4: Identify Contradictions

This is the most advanced and valuable part of the exercise. Look for instances where what a user Says contradicts what they Do.

For example, a user might say that security is their top priority, but they do click "Remember Password" on a public computer. These contradictions are "innovation gold mines." They signal that the current solution is either too difficult to use or doesn't align with the user's actual habits. Designing for what people actually do rather than what they say they do is the hallmark of a world-class product.

Why Your Team Needs an Empathy Map Template Right Now

In the fast-paced world of software development, it is tempting to skip empathy mapping and move straight to wireframing. However, this often leads to "feature bloat"—building things that are technically impressive but emotionally resonant with no one.

Removing Internal Bias

Every team member brings their own biases to a project. Engineers might focus on technical feasibility; marketers might focus on personas' purchasing power. An empathy map forces everyone to step out of their professional silos and view the world through the eyes of the person using the software.

Revealing Knowledge Gaps

When a team tries to fill out an empathy map and realizes they have nothing to put in the "Feels" quadrant, it exposes a lack of depth in their user research. It prevents the team from moving forward with a half-baked understanding of the user.

Building Stakeholder Buy-in

It is much easier to convince a stakeholder to change a product direction when you can point to a collective map of user frustrations. It moves the conversation from "I think we should change this" to "Our users feel overwhelmed by this specific step, and here is the evidence."

Common Pitfalls to Avoid in Empathy Mapping

While the tool is simple, its execution can often go wrong.

  • Mapping a "Generic" User: Trying to map "The Customer" is a mistake. Map "The First-Time Small Business Owner" or "The Experienced IT Administrator." The more specific the persona, the more actionable the map.
  • Confusing Empathy Maps with Personas: A persona is a broad archetype (Who are they?). An empathy map is a snapshot of an experience (What are they going through right now?). Use personas to define the "Who" and empathy maps to define the "How."
  • Leaving the Map to Rot: An empathy map is a living document. As you release new features or gather more data, the user's "Feels" and "Does" will change. Revisit the map at the start of every major product cycle.

Real-World Example: Enterprise SaaS Procurement Lead

To illustrate how this looks in practice, let's look at a hypothetical empathy map for an IT Procurement Lead evaluating a new cybersecurity tool.

  • Says: "We need SOC 2 compliance before we even talk." "Your UI looks cleaner than the competitors."
  • Thinks: "If I recommend this and we get breached, it’s my job on the line." "I hope the implementation doesn't take six months like the last one."
  • Does: Forwards the security questionnaire to the legal team immediately. Compares three different pricing spreadsheets side-by-side.
  • Feels: Anxious about the personal risk of a bad decision. Overwhelmed by the number of vendors in the market.

By mapping this out, the product team realizes that "Ease of Implementation" and "Personal Risk Mitigation" are just as important as "Feature Set." They might decide to create a "Risk Mitigation Guide" as part of their sales collateral—a decision they never would have made by looking at feature requests alone.

Frequently Asked Questions

What is the difference between an empathy map and a journey map?

While both are UX tools, they serve different purposes. An empathy map is a "snapshot" of a user's mind at a specific point in time or in a general context. A journey map is a chronological "timeline" of a user's experience as they complete a specific task. Usually, you create an empathy map first to understand the user's mindset, then use that to inform the emotional highs and lows of the journey map.

How many people should be involved in an empathy mapping session?

The ideal group size is 3 to 6 people. You want enough diversity to get different perspectives (e.g., a designer, a developer, a customer success rep, and a product manager), but not so many people that the discussion becomes unmanageable.

What if we have no access to real users?

If you absolutely cannot talk to real users, you can create a "provisional" empathy map based on the knowledge of those who interact with users most, such as sales or support teams. However, this should always be treated as a set of hypotheses that must be validated with real user data as soon as possible.

Can empathy maps be used for marketing?

Absolutely. Marketers use empathy maps to understand the emotional triggers and barriers to purchase. By knowing what a potential customer "hears" from their peers or what they "think" when they see a price tag, marketers can craft much more effective messaging that speaks directly to the user's internal monologue.

Conclusion

An empathy map template is more than just a document; it is a catalyst for cultural change within a product team. By shifting the focus from "what we can build" to "who we are building for," it ensures that the resulting products are not just functional, but truly meaningful to the people who use them. Whether you are a startup founder or a UX veteran at a Fortune 500 company, taking the time to map out the says, thinks, does, and feels of your audience is the surest way to build products that resonate deeply and stand the test of time.