Latest / 5 Minute UX / Empathy Maps: Seeing Through Your User's Eyes
Transcript
- 0:08This lesson is Empathy Maps: Seeing Through Your User's Eyes.
- 0:11Let's get started.
- 0:18Imagine your team staring at scattered interview notes,
- 0:20completely unable to agree on what the user actually needs.
- 0:23Without a shared view, your design decisions inevitably
- 0:25drift away from real behaviors and emotions. This confusion
- 0:28happens because raw data remains unstructured and disconnected
- 0:30from the human experience. The solution is the Empathy Map,
- 0:33which transforms that chaos into a single, tangible visualization
- 0:36of the user's perspective. You will construct this map by
- 0:38categorizing research data into four distinct quadrants: Think,
- 0:41Feel, Say, and Do. This framework forces your team to
- 0:43move beyond assumptions and focus on specific, observed
- 0:46realities. By the end of this lesson, you will be able to
- 0:48construct a role empathy map that aligns your entire team. We
- 0:51will walk through identifying these four quadrants and
- 0:53applying the synthesis process to condense observations. You'll
- 0:56leave with a shareable artifact that keeps your design work
- 0:59firmly rooted in human needs.
- 1:05You've probably seen teams struggle to agree on what a user
- 1:08actually needs during a design session. Think back to when you
- 1:10gathered around a whiteboard, trying to make sense of
- 1:13scattered interview notes without a clear structure.
- 1:15That's exactly why we start by defining the workspace before we
- 1:18touch a single sticky note. You'll need a large surface
- 1:21area, like a physical wall or a digital canvas, divided into
- 1:23four distinct quadrants. These sections are specifically
- 1:26labeled Think, Feel, Say, and Do to organize your observations
- 1:29systematically. Grab your existing user research data,
- 1:31interview notes, or observations now, because you cannot populate
- 1:34these quadrants without that evidence. Every participant
- 1:37needs their own set of sticky notes and markers to record
- 1:39ideas independently. As you prepare, remember that the goal
- 1:42is to identify the four distinct quadrants: Think, Feel, Say, and
- 1:45Do. Once your materials are ready, you can begin applying
- 1:47the synthesis process to condense those observations into
- 1:50a shareable artifact.
- 1:57Start by defining the specific user role and context before you
- 1:59touch a single sticky note. This clear anchor ensures every
- 2:01observation you record remains relevant to the distinct tasks
- 2:04that specific persona faces. Without this definition, your
- 2:06team risks drifting into general assumptions rather than grounded
- 2:09insights. Once that role is locked in, your team populates
- 2:11the four distinct quadrants using existing research data.
- 2:13You'll need a large surface area, whether that is a physical
- 2:15whiteboard or a digital canvas, divided clearly into the four
- 2:18sections. Hand out markers and sticky notes so every
- 2:20participant can physically place their observations directly onto
- 2:22the map. Begin with the Think quadrant by documenting what is
- 2:25important to the user, their goals, and their internal
- 2:27thoughts. This section captures the silent mental landscape
- 2:29where the user weighs options and forms opinions before
- 2:32acting. Focus on their priorities and the internal
- 2:34logic they use to navigate your product or system. Move next to
- 2:36the Feel quadrant to capture the user's emotional states,
- 2:38frustrations, and anxieties during interaction. This is
- 2:40where you record the raw emotional data, such as moments
- 2:43of confusion or spikes of delight found in your interview
- 2:45notes. Understanding these feelings helps your team design
- 2:47for emotional needs, not just functional requirements. In the
- 2:50Say quadrant, you record exactly what the user explicitly states
- 2:52in interviews or feedback. This section is strictly for their
- 2:55own words, capturing direct quotes rather than your
- 2:57interpretation of their meaning. It provides the textual evidence
- 2:59that grounds your map in what the user actually communicated
- 3:01to you. Finally, list the user's observable actions and
- 3:04behaviors while using the system in the Do quadrant. These are
- 3:06the physical or digital interactions you witnessed, such
- 3:08as clicking a specific button or hesitating at a menu. This
- 3:11quadrant bridges the gap between what users claim they do and
- 3:13what they actually do. After the map is full, you must apply
- 3:15the synthesis process to condense observations into a
- 3:18shareable artifact. Gather the team to review all sticky notes,
- 3:20identify patterns, and remove any duplicate insights to create
- 3:22a single, cohesive output. This step transforms a cluttered
- 3:25board of individual ideas into a unified team understanding that
- 3:27everyone can rely on. The final result is a permanent, shareable
- 3:30artifact that serves as a continuous reminder of who you
- 3:32are designing for. This single output keeps the user's
- 3:34perspective visible throughout your design process, ensuring
- 3:37decisions remain centered on human needs. By following this
- 3:39sequence, you turn raw data into actionable guidance that drives
- 3:41your project forward.
- 3:48Let's say you have a whiteboard covered in sticky notes from
- 3:51your latest interview session. Your first job is to review
- 3:54those notes to identify patterns, remove duplicates, and
- 3:56condense the chaos into a single, cohesive output. This
- 3:59synthesis step turns scattered observations into a clear
- 4:01picture of the user. Watch out for a common pitfall where the
- 4:04team confuses what a user says versus what they think. If you
- 4:07mix these up, your map reflects your assumptions rather than
- 4:09observed behaviors, which ruins the accuracy of the artifact.
- 4:12You must distinguish between the two to keep your insights
- 4:15grounded in reality. If your map becomes cluttered with too
- 4:17many overlapping ideas, pause to group similar notes and vote on
- 4:20the most critical insights. This recovery strategy helps you
- 4:23focus on what truly matters before you finalize the design.
- 4:26By doing this, you ensure the final artifact drives better
- 4:28decisions.
- 4:34In your next project, schedule a thirty-minute workshop with your
- 4:36team to define one specific user role. This clear definition
- 4:39anchors the entire session, ensuring everyone focuses on the
- 4:42distinct tasks and challenges that person faces. Guide the
- 4:44team to populate the four quadrants of Think, Feel, Say,
- 4:47and Do using your existing research data. You must cite
- 4:49specific evidence for every sticky note placed, rather than
- 4:52filling the map with speculation or assumptions. Finally,
- 4:54transform those synthesized sticky notes into a permanent,
- 4:57shareable artifact that informs your next design decision. This
- 4:59single, cohesive output keeps your team aligned on real user
- 5:02needs. You now have a structured way to see through your user's
- 5:05eyes, turning raw observations into actionable design guidance.
- 5:10Welcome to The Take. I'm joined by a fellow practitioner and
- 5:13together we're going to dig into Empathy Maps: Seeing Through
- 5:16Your User's Eyes — what it means in practice and what's worth
- 5:19remembering.
- 5:21[HOST] That distinction between what users say and what they
- 5:24actually do is where most of my past projects have failed.
- 5:27[LEARNER] Absolutely, and I find the "Say" quadrant often becomes
- 5:30a dumping ground for our own interpretations disguised as
- 5:33quotes. [HOST] That happens when we stop listening for the raw
- 5:36data and start listening for the validation we wanna hear.
- 5:38[LEARNER] Exactly, but the real friction comes when we try to
- 5:41force the "Think" quadrant to match the "Do" quadrant. [HOST]
- 5:44You mean when the user claims they prioritize speed but then
- 5:47spends twenty minutes customizing their profile?
- 5:50[LEARNER] Yes, and that gap is where the real design
- 5:52opportunity lives, not in the comfortable assumptions we
- 5:55usually make. [HOST] It's tempting to smooth over those
- 5:58contradictions, but the map forces us to sit with that
- 6:01uncomfortable reality. [LEARNER] I wonder if AI tools might
- 6:03actually make this worse by auto-synthesizing those
- 6:06contradictions into a single, safe average. [HOST] That's a
- 6:09real risk if we let an algorithm tell us what the user feels
- 6:12instead of us wrestling with the sticky notes. [LEARNER] True,
- 6:15though I could see it helping us quickly sort through hundreds of
- 6:18interview transcripts to find those specific behavioral
- 6:21mismatches. [HOST] The tool can handle the sorting, but only a
- 6:24human team can decide why that mismatch matters for the product
- 6:27strategy. [LEARNER] So the artifact becomes a shared
- 6:30agreement on the ambiguity rather than a definitive answer
- 6:32sheet. [HOST] Precisely, and that shared agreement is the
- 6:35only thing that stops the team from drifting back into old
- 6:38habits later.