HTML MASTER CLASS /// LEARN TAGS /// BUILD STRUCTURE /// SEMANTIC WEB /// HTML MASTER CLASS /// LEARN TAGS ///

Beyond the Survey

Turning scattered research notes into a shared picture of the user.

⚡ Total XP: 0|💻 management XP: 0

Skill Matrix

UNLOCK NODES BY LEARNING NEW TAGS.

Select an unlocked node to view details root

🚀 LEVEL UP TO SENIOR:Unlock 500+ Advanced Practical Challenges & Exercises.

🎓 COURSERA PARTNER:Earn professional Google, Meta, and IBM certificates to supercharge your resume.

Interview transcripts pile up fast and nobody rereads them. An empathy map compresses a pile of raw research into one page the whole team will actually look at before a design review.

1Built From Research, Not Guesses

An empathy map is only as good as the research behind it. It should be filled in after interviews, usability sessions, or support-ticket review — never brainstormed cold in a conference room. If a quadrant is empty because you don't actually know, that's a signal to go talk to more users, not to invent a plausible-sounding note.

2One Map, One Persona, One Context

A common mistake is building a single empathy map for an entire user base. A map is sharper when scoped to one persona in one specific moment — 'a returning customer during checkout,' not 'our users' in general. Multiple maps for multiple contexts beat one map that tries to represent everyone and ends up representing no one.

3Step-by-Step Breakdown

Introduction. An empathy map is a simple four-quadrant canvas — Says, Thinks, Does, Feels — used to organize what you learned from user interviews and observation into one shared, visual snapshot of a specific persona in a specific situation.

The Four Quadrants. SAYS captures direct quotes from interviews. THINKS captures beliefs and worries the user may not say out loud. DOES captures observed actions and behaviors. FEELS captures the underlying emotional state — frustration, anxiety, confidence — driving the other three.

Says vs. Thinks: The Real Value. The map's biggest payoff is the gap between Says and Thinks. Users often say 'it's fine' in an interview while privately thinking 'I'll never use this again.' Spotting that gap is what separates surface-level feedback from an actual insight worth acting on.

Knowledge Check. During onboarding interviews, a user says 'the signup was okay' but you observed them abandon the form twice and retype their email three times. Which quadrant does that observed abandonment behavior belong in?

→DOES — it's an observed action, distinct from what the user verbally reported
→SAYS — because it happened during the interview session

Summary. An empathy map isn't a deliverable to file away — it's a working tool the whole team references during design and prioritization discussions, keeping decisions anchored to a real user's words, actions, and feelings instead of assumptions.

Pascual Vila

Frontend Instructor // Code Syllabus

Common Pitfalls & Errors

The Error //

Filling in the map from assumptions instead of real research

// Wrong
Thinks: "Users probably find our pricing page confusing." (never verified)

// Right
Thinks: "3 of 5 interviewed users paused on the pricing page and asked what 'seats' meant."

The Solution //

An empathy map built without interviews or observation is just the team's own biases dressed up as user insight. If a quadrant is a guess, either go get the data or explicitly mark it as an unvalidated hypothesis.

The Error //

Building one generic map for the entire user base

// Wrong
One empathy map titled "Our Users"

// Right
Separate maps: "First-time free-trial user during signup" and "Renewing customer during the cancellation flow"

The Solution //

A map meant to represent every user at once ends up too vague to act on. Scope each map to one persona in one specific situation — the more specific the context, the more useful the resulting insights.