🚀 LEVEL UP TO SENIOR:Unlock 500+ Advanced Practical Challenges & Exercises.
🎓 COURSERA PARTNER:Earn professional Google, Meta, and IBM certificates to supercharge your resume.
HTML MASTER CLASS /// LEARN TAGS /// BUILD STRUCTURE /// SEMANTIC WEB /// HTML MASTER CLASS /// LEARN TAGS ///

Deep Understanding

Beyond the surface. Learn how to use empathy mapping to understand what users think, feel, say, and do to uncover hidden needs.

Total XP: 0|💻 management XP: 0

Skill Matrix

UNLOCK NODES BY LEARNING NEW TAGS.

Empathy

Technical Specification //

Inside the user's head.

🚀 LEVEL UP TO SENIOR:Unlock 500+ Advanced Practical Challenges & Exercises.
🎓 COURSERA PARTNER:Earn professional Google, Meta, and IBM certificates to supercharge your resume.

Empathy maps are the bridge between raw research data and actionable user personas.

1Synthesizing the Mess

After 10 user interviews, you have a lot of noise. Empathy maps help the team group findings into categories, making it easier to see patterns in how users experience the world.

2The Contradiction Finder

The magic happens when you see a user 'SAYS' they love a feature, but 'THINKS' it's too complicated to use every day. These contradictions are where the best innovation happens.

3Beyond the UI

Empathy maps look at the user's environment. What are they HEARING from their boss? What are they SEEING in the market? This 'Outside-In' perspective is vital for product strategy.

4Step-by-Step Breakdown

An Empathy Map is a collaborative tool used to gain a deeper insight into your customers. It's used during the Discovery phase to synthesize research.

The map is divided into four quadrants: what the user SAYS, DOES, THINKS, and FEELS. This helps highlight contradictions between words and actions.

At the bottom, we add 'PAIN' (frustrations, fears) and 'GAIN' (wants, needs, measures of success). This is where the product value is born.

In which quadrant would you place a user quote like 'I wish this app was faster'?

  • Thinks
  • Says
  • Does
  • Feels

Why is it important to capture what a user 'THINKS' even if they don't 'SAY' it?

  • To practice mind-reading
  • To uncover hidden fears or social pressures that users might be too polite or embarrassed to mention
  • To ignore what they say entirely
  • Because what users think is always 100% accurate

Level Up 🚀

Advanced cheat sheets, SEO tricks, and interview prep for this topic.

Browser Support

ChromeSupported

Fully supported.

FirefoxSupported

Fully supported.

SafariSupported

Fully supported.

EdgeSupported

Fully supported.

Accessibility (A11y)

1Represent Accessibility Needs Explicitly

When synthesizing interview data, capture accessibility-related pains (e.g., a user with low vision struggling to read small text) as their own 'Pain' entries instead of folding them into generic usability complaints, so they don't get lost when prioritizing.

// Pain quadrant entry: // "Struggles to read body text on the dashboard without zooming to 200%"

SEO Implications

  • 1

    Voice-of-Customer Language Feeds Content Strategy

    The exact phrases captured in the 'Says' quadrant are often the same language customers type into search engines. Feeding those verbatim quotes into marketing/SEO copy tends to match real search intent better than internal jargon.

Best Practices

Fill It In After Research, Not Before

An empathy map built from assumptions instead of real interview transcripts just launders bias into something that looks like data. Always populate quadrants from direct quotes and observed behavior.

Look for Says/Thinks Contradictions

The most valuable signal on the map is the gap between what a user says publicly and what they seem to think or feel privately — that gap is often where the real, unspoken problem lives.

Frequent Bugs

THE BUG

The team fills the 'Thinks' and 'Feels' quadrants with pure guesses because no one wants to admit the interviews didn't cover those questions.

THE FIX

Leave a quadrant empty or marked 'unknown' rather than fabricating it, and use that gap to plan follow-up research.

Real-World Examples

Empathy Map for a Churned User Segment

A subscription product is losing users after month 2. The team runs 8 exit interviews and builds an empathy map to synthesize the findings before deciding what to fix.

Says: "I just forgot I was paying for it"
Does: Opens the app once in week 1, never again
Thinks: "This isn't worth the mental effort to keep using"
Feels: Mild guilt, then indifference

Interview Prep

Pascual Vila

Pascual Vila

Frontend Instructor // Code Syllabus

Common Pitfalls & Errors

The Error //

Building the map from stakeholder opinions instead of actual user interviews

Wrong: "I bet users feel overwhelmed by the dashboard" (nobody was interviewed) Right: "3 of 8 interviewees said the dashboard felt overwhelming" (sourced from transcripts)

The Solution //

An empathy map is only as good as its source data. If it's filled in by the PM and designer guessing what users probably feel, it just encodes the team's existing biases with a nicer format.

The Error //

Treating it as a one-time artifact instead of a living reference

Wrong: Empathy map created in a workshop, filed away, never opened again Right: Empathy map pinned in the team space, updated after each new round of interviews

The Solution //

Teams often build an empathy map once during a kickoff workshop, then never look at it again. It should be revisited and updated as new research comes in, and referenced during design critique and prioritization.

Continue Learning