Empathy map: how to use it without ending up inventing your customer

The empathy map —also called an empathy map— is a template for organizing what you know (and what you think you know) about a customer or user: what they think, what they feel, what they see, what they hear, what they say, what they do, what frustrates them, and what they hope to gain. It serves to turn loose observations into actionable hypotheses about how to speak to them, what to create for them, and what to avoid.

On paper it's a simple tool. In practice, almost all empathy maps made in companies have the same flaw: they're filled in a room with sticky notes, without any real customer nearby, based on what the team thinks about the target persona. The result is a document that looks strategic but only reflects the team's own biases. That's why this article doesn't stop at describing the quadrants; it focuses on how to populate it with real signal and translate it into decisions.

The six quadrants that matter

There are versions with four, six, and eight cells. The useful version has six:

1. What they think and feel

What they really worry about and sometimes wouldn't say out loud. Aspirations, fears, internal frustrations, doubts they haven't yet put into words.

2. What they see

Their environment: what the competition posts, what their peers do, what references they get from the market, what they look at when comparing.

3. What they hear

Who influences them: bosses, team, professional community, podcasts, industry press. What narrative dominates their industry right now.

4. What they say and do

How they describe the problem when talking with their peers (literal language), what decisions they're already making, what tools they use today.

5. Pains and efforts

What they struggle with, what they try and fails them, what inefficient routines they keep, what blocks them from solving the problem.

6. Outcomes and gains

What they consider "this worked," what metric will judge them, what recognition they expect, what would be freed up in their day-to-day if the problem disappeared.

If your map doesn't answer all six in detail, it's incomplete and will produce generic messages.

The main trap: filling it in by consensus

The most expensive mistake: three people from the team in a room, each contributing what they think about the customer, and everyone nodding along. What comes out of that isn't empathy: it's a documented stereotype. And the worst part is that it looks rigorous because it's in a nice template.

An honest empathy map cites sources. Each statement comes from one of these places:

• Interviews with real customers (at least 5-7, ideally 10).
• Recorded or transcribed sales calls — where the customer describes their problem in their own words.
• Support tickets — the place where real frustrations appear unfiltered.
• Reviews and public conversations — including the competition's.
• Product usage data — what they actually do, not what they say they do.
• Search Console searches — the literal language they use to reach you.

If no quadrant can cite at least two of these sources, the map is fiction.

How to populate it with real signal

A process that works, in this order:

1. Start with the "says and does" quadrant — it's the easiest to populate with verifiable data (transcripts, tickets, messages).
2. Identify the literal language the customer uses. If they say "we waste time coordinating," don't translate it to "operational inefficiency." That translation is exactly where landing-page copy breaks.
3. Continue with pains and gains — building on what you already wrote above. This prevents jumps to unverified hypotheses.
4. Then tackle thinks/feels and hears — these are the most interpretive; it's wise to do them with solid prior data.
5. Explicitly flag unverified hypotheses. If something is the team's opinion, label it as a "hypothesis to validate." Next quarter you come back and check it.

The "so what" rule

An empathy map without derived decisions is decoration. Each quadrant has to produce an operational response:

• If they fear losing time → the main message should be speed, not quality.
• If they hesitate over trust → the service page needs proof (cases, metrics, guarantees).
• If they don't understand the process → educational content or a guided demo is missing.
• If they compare with a specific competitor → you need an explicit comparison page.
• If their boss will judge them by a specific metric → the case study should open with that metric, not with your product.

Without that translation, everything written on sticky notes stays on sticky notes.

Common mistakes

• Filling it in once and filing it away. The customer changes, the market changes, the product changes. An old map produces outdated messages.
• Making a single map for several different personas. If you sell to CMOs and to freelancers, that's two maps, not one made by compromise.
• Confusing buyer and user. In many B2B contexts, whoever signs isn't whoever uses. You need a map for each role on the buying committee.
• Not connecting it to the creative brief. If the content team doesn't see it when starting a piece, it affects nothing.
• Taking the team's language and attributing it to the customer. It's the subtlest bias and the most expensive.

The empathy map and creative operations

An empathy map only works if it travels from the strategic document to daily operations. The content team has to see it every time it starts a piece. The product team has to cross-reference it when prioritizing the roadmap. Sales has to lean on it when working through objections. If it lives as an isolated PDF in Drive, it's not a tool: it's a symbolic gesture.

That's why it fits directly into the creative operations cluster: the map feeds the editorial calendar (which pieces to create and for whom), brand management (what tone and language to use), and the creative KPIs (what result we expect for each audience). Without a common operating system, the insights don't get applied.

At Polimake, that logic lives across three surfaces of the same product: Studio so that each brief links to the current map, Studio to produce pieces anchored in the customer's literal language, and Media as the repository where the map itself —along with research and brand guides— is available to the whole team.

When to review it

Doing it once isn't enough. Three clear signs that it's time to update:

1. New objections aren't in the map. If sales runs into resistance you didn't anticipate, a quadrant is missing.
2. The customer's language has changed. Search Console searches or demo transcripts use terms that no longer appear in your copy.
3. You've launched a new product or changed markets. It's practically a different person; don't force them into the old map.

A healthy empathy map is reviewed at least once a year, and whenever a piece of market data contradicts what it says.

Related concepts

• Commercial research
• Commercial research techniques
• Target in marketing
• Targeting
• Market segmentation
• Video brief

---

This piece is part of the Polimake glossary and the cluster on creative operations. If you lead content or brand strategy, also read editorial calendar and brand management.