Empathy Map

1. What Is Empathy Map?

The Empathy Map is a structured, visual framework used to capture what a customer (or user) thinks, feels, says, and does in a particular context—plus their pains and gains. It helps teams build a shared, evidence-based understanding of customers’ mindsets and motivations so they can design better journeys, communications, services, and products.

In the Customer, Service, CRM, and CX domain, empathy mapping is a practical way to translate disparate inputs—interviews, support transcripts, survey verbatims, analytics—into a concise, human portrait that clarifies why customers behave as they do. The map becomes a bridge between research and action: it informs messaging, content, onboarding, service scripts, and product decisions with a tangible customer perspective.

Consultants and in-house teams use Empathy Maps to align stakeholders, sharpen personas, prioritize pain points, and generate testable hypotheses. It’s lightweight enough for a single episode (e.g., “activate my card”), and robust enough to guide a multi-quarter CX program when paired with journey mapping and service blueprinting.

2. Origin and Background

Origin: The Empathy Map was created by Dave Gray of XPLANE and popularized through the book “Gamestorming” (2010). It has since been updated and adapted by design and innovation communities.

Why it was created: Teams needed a simple, visual method to synthesize qualitative insights into a shared understanding of users—without lengthy research decks. The Empathy Map makes tacit knowledge explicit and actionable, anchoring design and communications in the customer’s world.

Diffusion: Empathy mapping spread rapidly via design thinking, UX, and service design practices. It’s now a staple in workshops, CX programs, and product discovery rituals—and widely taught in business schools and corporate academies. Variants exist (e.g., adding “Pains/Gains,” “Sees/Hears”), but the intent remains consistent: create empathy that informs better decisions.

3. How Empathy Map Works

The map is a canvas divided into sections that capture different aspects of a person’s experience. Two widely used versions are:

• Classic four-quadrant: Says, Thinks, Does, Feels.
• Extended six-field: Says, Thinks, Does, Feels, Pains, Gains (often the preferred version for CX and service work).

The core sections

• Says: Direct quotes and paraphrases from customers (interviews, surveys, calls). What do they tell us? Capture exact language to inform messaging tone and keywords.
• Thinks: Thoughts customers may not voice—assumptions, worries, mental models. These often explain hesitation or churn.
• Does: Observable behaviors and steps taken (clicks, calls, workarounds). Tie to analytics where possible.
• Feels: Emotions at key moments (confidence, anxiety, frustration, relief). Emotion often explains effort and loyalty.
• Pains: Frictions, risks, and barriers (time, cost, complexity, compliance). What they want to avoid.
• Gains: Desired outcomes, benefits, and value drivers (speed, control, recognition, certainty). What success looks like to them.

Optional context prompts

• Sees: Environmental cues and comparisons (competitor claims, peer behaviors, reviews) that shape expectations.
• Hears: Influences from colleagues, managers, family, creators, or customer communities.
• Goals and constraints: What they need to accomplish and what limits them (policies, budget, skills).

The output is a concise, persona-specific artifact for a defined situation—e.g., “newly onboarded HR admin setting up payroll”—that surfaces patterns and tensions. Teams then convert those patterns into design criteria, content briefs, and experiment hypotheses.

4. When to Use Empathy Map

Empathy mapping is most useful when you need to quickly synthesize qualitative insights and align teams on what really matters to a customer in a specific moment.

• Use cases:
  • Before journey mapping or service blueprinting to ground the work in customer reality.
  • To refine personas with behavioral and emotional depth (beyond demographics or firmographics).
  • To inform messaging and content strategy—tone, vocabulary, proof points, and objections.
  • During product discovery or onboarding redesign, where emotions and workarounds shape adoption.
  • In service transformation to reduce effort and repeat contact by addressing root anxieties.
• Company types:
  • B2C: Retail, healthcare, financial services, travel—where expectations and emotions drive loyalty.
  • B2B: SaaS and services with multi-stakeholder buying groups; map different roles (economic buyer, admin/user) and their distinct pains/gains.
  • SMB/startups: Fast, low-cost way to ground decisions without over-researching.
  • Enterprise/global: Creates a shared language across regions and functions; localize maps where context diverges.

Time and data requirements: A focused empathy map can be created in a half-day workshop using recent interviews, transcripts, and analytics for a single persona and context. A more rigorous effort—new research, segmentation alignment, and validation—takes 2–4 weeks.

When it’s especially powerful: When teams disagree on “what customers want,” when messaging underperforms, or when adoption and satisfaction lag despite feature completeness.

When it’s not a good fit: When you need market sizing, econometric budget optimization, or causal inference. Empathy maps don’t replace quantitative segmentation or financial modeling; they complement them.

5. How to Apply Empathy Map: Step-by-Step

1. Define scope and the person-in-context

   Specify exactly who you’re mapping (persona/role) and the situation or episode (e.g., “First-time small business owner applying for a loan online”). Clarity here prevents vague generalizations.

2. Assemble inputs

   Gather recent customer interviews, survey verbatims, call/chat transcripts, support tickets, reviews, social/community threads, and behavioral analytics. Pull 10–20 representative quotes and 5–10 key metrics to ground the session.

3. Choose your canvas

   Select the 6-field version (Says, Thinks, Does, Feels, Pains, Gains) for CX work; optionally add “Sees/Hears” prompts. Print large or use a digital whiteboard for remote teams.

4. Run a fast, structured mapping session

   Invite a cross-functional group (CX, product, marketing, service, sales). Time-box 45–60 minutes. Populate each section with evidence-backed notes:

   • Start with Says (quotes), then Does (behaviors) to anchor in observable data.
   • Add Thinks/Feels (inferred from language, pauses, emotions).
   • Consolidate Pains/Gains as explicit problem/benefit statements.
   • Cluster similar notes and label themes.

   Use different colors for evidence vs. assumptions; assumptions become hypotheses to test.

5. Synthesize tensions and insights

   Identify 3–5 tensions (e.g., “Wants control but fears making an irreversible mistake”). Convert them into insight statements: “When X, they feel Y because Z; therefore they need A.” These become design and messaging criteria.

6. Translate insights to decisions

   For each insight, agree on:

   • Messaging/content implications: Tone, vocabulary, proof points, required assets (e.g., setup checklists, ROI calculators).
   • Experience changes: UI copy, onboarding steps, guidance, proactive alerts, human handoffs.
   • Service scripts/policies: What to acknowledge, how to reassure, where to streamline approvals.
7. Formulate hypotheses and tests

   Write testable statements (e.g., “If we add a 2-minute explainer addressing [top fear], trial-to-activation will increase by 15%”). Define success metrics (conversion, CES, repeat contacts) and a 2–4 week test plan.

8. Integrate into CRM and operating rhythm

   Tag insights in your CRM/knowledge base. Update talk tracks, macros, and content libraries. Add empathy-driven checkpoints to briefs (e.g., “Which ‘Feels’ and ‘Pains’ does this asset address?”). Review quarterly.

9. Validate and refresh

   After experiments, revisit the map. Replace assumptions with evidence, add new quotes, remove outdated items. Maintain version control by persona and context.

6. Example: Empathy Map in Action

Company: A $200M ARR B2B HR tech SaaS focused on mid-market customers.

Problem: New-account admins were slow to complete payroll setup, driving high support volumes and delayed time-to-value. NPS in the first 30 days lagged the benchmark by 9 points; repeat contacts centered on tax configuration and data imports.

Approach: The team built an empathy map for the “HR/Payroll Admin (first 14 days),” using 18 interview transcripts, 400 tagged support tickets, and onboarding analytics.

• Says: “I’m afraid I’ll mess up taxes,” “I don’t have time to watch long videos,” “Just give me the exact steps for my state.”
• Thinks: “If I get this wrong, it’s my fault,” “Our data is messier than average,” “Vendors oversimplify.”
• Does: Googles state-specific tax rules, starts import then abandons, opens multiple support chats.
• Feels: Anxious at tax setup, relieved after first successful payroll, frustrated by jargon.
• Pains: Fear of compliance errors, unclear prerequisites, time pressure, jargon-heavy help articles.
• Gains: Certainty (checklist complete), speed (finish in under an hour), confidence (verification steps), tailored guidance.

Decisions and experiments:

• Rewrote onboarding content with plain language and a state-specific wizard; added a 3-minute “first payroll” explainer.
• Introduced a “confidence check” banner before run—auto-validate top five error conditions.
• Updated support macros to first acknowledge fear, then provide a tailored micro-checklist; offered optional 15-minute concierge slot for at-risk accounts.

Outcomes (8 weeks): Time-to-first-payroll decreased from median 12 days to 7; first-30-day repeat contacts −23%; onboarding CES improved by 0.6 points; early-cohort NPS +8 points. Support cost per new account fell 14%. The empathy map was updated with new quotes and used to brief a webinar series.

7. Strengths and Limitations

Strengths

• Human clarity: Captures motivations and emotions that raw analytics miss—why behavior happens.
• Alignment tool: Creates a shared, evidence-backed customer view across CX, product, marketing, and service.
• Actionable synthesis: Turns unstructured VOC into design criteria, messaging implications, and testable hypotheses.
• Lightweight and fast: Useful early in discovery and repeatedly during delivery; easy to refresh as contexts change.

Limitations

• Qualitative bias risk: Without representative inputs, maps can reflect loud anecdotes or internal assumptions.
• Not a segment or model: It doesn’t replace quantitative segmentation, JTBD analysis, or financial prioritization.
• Static snapshot risk: Emotions and pains shift with environment; maps need regular updates to stay relevant.
• Context-specific: One persona may need multiple maps for different episodes; reusing a single map across contexts can mislead.

8. Common Pitfalls (and How to Avoid Them)

• Projecting your own views

  What goes wrong: The map mirrors internal opinions. Avoid: Start with real quotes and behaviors; color-code assumptions and convert them into hypotheses.

• Mapping a generic persona, not a situation

  What goes wrong: Vague, un-actionable insights. Avoid: Always define the context (“who, when, doing what”) before mapping.

• Skipping evidence triangulation

  What goes wrong: Overreacting to one story. Avoid: Triangulate interviews with tickets, analytics, and surveys.

• Overstuffing the map

  What goes wrong: No clear priorities. Avoid: Synthesize 3–5 core tensions; push detail to appendices.

• Not translating to decisions

  What goes wrong: “Wall art” that doesn’t change outcomes. Avoid: Require each insight to yield a messaging or experience change and a test plan.

• Conflating “Thinks” and “Feels” with “Says”

  What goes wrong: Lost nuance in emotions vs. statements. Avoid: Keep quotes in “Says,” infer emotions in “Feels,” and validate with new research.

• Using one map for multiple roles

  What goes wrong: Mixed signals from buyers vs. users. Avoid: Create separate maps for each role (e.g., economic buyer, admin, end user).

• Never refreshing

  What goes wrong: Stale maps miss new pains (policy changes, platform updates). Avoid: Schedule quarterly reviews; update with new evidence.

9. How Empathy Map Relates to Other Frameworks

• Customer Journey Mapping: Empathy maps deepen the “why” behind behaviors at each stage. Use them first to inform journey maps, then update maps as journeys change.
• Service Blueprinting: Blueprinting operationalizes delivery (frontstage/backstage, SLAs). Empathy maps inform scripts, content, and policies that address customer pains and emotions identified.
• Jobs To Be Done (JTBD): JTBD defines functional and emotional “jobs.” Empathy maps add texture—language, fears, and desires—that translate jobs into messaging and UX.
• Personas and Segmentation: Personas define “who” at a macro level; empathy maps capture “what it’s like to be them” in a given moment. Use together for targeting and design.
• HEART/AARRR and CX metrics: Metric frameworks track outcomes. Empathy maps suggest what to change to move those metrics (reduce effort, increase adoption, improve happiness).
• Messaging House/Value Proposition: Use empathy maps to choose tone, proof points, and objection handling that resonate with real customer language.

Choice guidance: Start with research inputs, build an empathy map to synthesize customer perspective, design journeys and blueprints to operationalize improvements, and measure with HEART/AARRR and CX metrics. Use messaging frameworks to convert insights into communications.

10. Key Takeaways

• The Empathy Map distills what customers say, think, do, and feel—plus pains and gains—into an actionable, shared understanding.
• It is fastest and most valuable when scoped to a specific person-in-context (e.g., “new customer activating service”).
• Ground the map in evidence; color-code assumptions and turn them into testable hypotheses tied to KPIs.
• Use the map to drive concrete changes in messaging, content, onboarding, and service scripts—then validate and refresh.
• Empathy maps complement (not replace) journey maps, service blueprints, JTBD, and quantitative segmentation.

11. FAQs About Empathy Map

Is the Empathy Map still relevant with today’s AI and data-rich CX?
Yes. Data shows what happened; empathy mapping explains why. It converts VOC and behavioral signals into human truths that guide design, messaging, and policy. Many teams now feed AI-summarized transcripts into empathy mapping for speed, then validate with targeted research.

How is an Empathy Map different from a persona?
A persona describes “who” at a macro level (role, context, goals). An empathy map captures the lived experience of that persona in a specific situation—what they say/think/feel/do, and their pains/gains—making it directly actionable for design and communication.

How many people should be in an empathy mapping session?
Aim for 6–10 cross-functional participants (CX, product, marketing, service). Fewer than 4 reduces diversity; more than 12 slows synthesis. You can run multiple parallel groups and synthesize outputs.

How long does it take to build one?
With existing inputs, a solid map takes 60–90 minutes to draft and another 60 minutes to synthesize insights and decisions. If you need fresh research, plan 2–4 weeks for interviews, analysis, and validation.

Can this work in B2B buying groups?
Absolutely. Create separate maps for each role (economic buyer, technical evaluator, admin, end user) and for key episodes (vendor selection, onboarding, renewal). The differences in pains/gains across roles often explain deal friction and adoption gaps.

What tools should we use?
Any collaborative whiteboard (physical or digital) works. The value comes from evidence and synthesis, not the tool. Store final maps in your CX/CRM knowledge base and link to relevant content, scripts, and dashboards for easy adoption.