CX Misconceptions
Why empathy maps rarely drive action
Half an empathy map is guesswork, so stakeholders file it away. Raw quotes, clips, and behavioral evidence persuade where quadrants cannot.
Empathy maps split a customer into quadrants: says, thinks, does, feels. But if a customer didn't say it or do it, you're guessing, and that assumption density is why the maps get filed away instead of changing decisions. Direct quotes, video clips, and cross-participant evidence do what the artifact cannot.
An empathy map divides a customer portrait into quadrants: what they say, think, do, and feel, sometimes adding what they see and hear. The problem sits in the middle of the template. "Says" and "does" can be observed. "Thinks" and "feels" cannot; they are guesses, usually made by a team in a conference room. So half the artifact is speculation formatted to look like knowledge, and everyone who reads it can sense that.
Why it matters to the business
Artifacts built on assumptions do not move money. Skeptical executives discount them, teams file them, and the research investment evaporates. The say-do gap makes even the observable half fragile: a study by the analytics firm 84.51 compared survey answers with loyalty-card records and found 75% of respondents misstated their own purchase behavior. The pattern shows up at industry scale, too. Gartner found 83% of organizations struggle to use journey maps to identify and prioritize CX efforts, and assumption-heavy artifacts of any kind share that fate. Maps persuade only when the evidence underneath is primary and visible: NN/g's survey of practitioners found the most successful mapping efforts were built on customer interviews, not brainstorms.
How to use it
- Bring direct quotes into decision meetings instead of paraphrased feelings.
- Show short video clips from research sessions; one real customer struggling beats any quadrant.
- Present themes with counts across participants ("seven of nine users hit this wall"), not composite portraits.
- If you must map, label every assumption as an assumption and convert each into a research question with an owner.
- Validate stated intent against behavioral data before it enters a roadmap discussion.
Where teams get it wrong
Teams treat the empathy map as the deliverable: run the workshop, fill the quadrants, hang the poster, done. The map was supposed to be a summary of evidence. Without underlying research it becomes a laundering device that turns guesses into something that looks like findings.
Ask your team
- For the customer portrait we're using, what did a real customer actually say or do to support each claim?
- When did raw research, a quote, a clip, or a recording, last appear in one of our decision meetings?
- Which items on our empathy map are validated, and which are still assumptions with no owner?
If the customer didn't say it or do it, you don't know it.
Apply this
Reading about why empathy maps rarely drive action is one thing. Seeing where it applies in your journey is the useful part.