Empathy Maps: Seeing Through Your User's Eyes

Learn to synthesize user research into a powerful visual tool that captures what users think, feel, say, and do. You will master the four-quadrant framework to align your team on user challenges and drive human-centered design decisions. Learning Objective: By the end of this lesson, learners will be able to construct a role empathy map by categorizing user research data into the four quadrants of Think, Feel, Say, and Do. Transcript The Empathy Map Challenge Imagine your team staring at scattered interview notes, completely unable to agree on what the user actually needs. Without a shared view, your design decisions inevitably drift away from real behaviors and emotions. This confusion happens because raw data remains unstructured and disconnected from the human experience. The solution is the Empathy Map, which transforms that chaos into a single, tangible visualization of the user's perspective. You will construct this map by categorizing research data into four distinct quadrants: Think, Feel, Say, and Do. This framework forces your team to move beyond assumptions and focus on specific, observed realities. By the end of this lesson, you will be able to construct a role empathy map that aligns your entire team. We will walk through identifying these four quadrants and applying the synthesis process to condense observations. You'll leave with a shareable artifact that keeps your design work firmly rooted in human needs. Key Points: Scenario: A design team struggles to agree on user needs because raw interview notes are scattered and unstructured. Problem: Without a shared view, design decisions drift away from actual user behaviors and emotions. Solution: The Empathy Map transforms raw data into a single, tangible visualization of the user's perspective. Setting Up the Workshop You've probably seen teams struggle to agree on what a user actually needs during a design session. Think back to when you gathered around a whiteboard, trying to make sense of scattered interview notes without a clear structure. That's exactly why we start by defining the workspace before we touch a single sticky note. You'll need a large surface area, like a physical wall or a digital canvas, divided into four distinct quadrants. These sections are specifically labeled Think, Feel, Say, and Do to organize your observations systematically. Grab your existing user research data, interview notes, or observations now, because you cannot populate these quadrants without that evidence. Every participant needs their own set of sticky notes and markers to record ideas independently. As you prepare, remember that the goal is to identify the four distinct quadrants: Think, Feel, Say, and Do. Once your materials are ready, you can begin applying the synthesis process to condense those observations into a shareable artifact. Key Points: Materials needed: A large surface (whiteboard or digital canvas) divided into four quadrants. Tools required: Sticky notes and markers for every participant to record ideas. Prerequisites: Gather existing user research data, interview notes, or observations before starting. Populating the Four Quadrants Start by defining the specific user role and context before you touch a single sticky note. This clear anchor ensures every observation you record remains relevant to the distinct tasks that specific persona faces. Without this definition, your team risks drifting into general assumptions rather than grounded insights. Once that role is locked in, your team populates the four distinct quadrants using existing research data. You'll need a large surface area, whether that is a physical whiteboard or a digital canvas, divided clearly into the four sections. Hand out markers and sticky notes so every participant can physically place their observations directly onto the map. Begin with the Think quadrant by documenting what is important to the user, their goals, and their internal thoughts. This section captures the silent mental landscape where the user weighs options and forms opinions before acting. Focus on their priorities and the internal logic they use to navigate your product or system. Move next to the Feel quadrant to capture the user's emotional states, frustrations, and anxieties during interaction. This is where you record the raw emotional data, such as moments of confusion or spikes of delight found in your interview notes. Understanding these feelings helps your team design for emotional needs, not just functional requirements. In the Say quadrant, you record exactly what the user explicitly states in interviews or feedback. This section is strictly for their own words, capturing direct quotes rather than your interpretation of their meaning. It provides the textual evidence that grounds your map in what the user actually communicated to you. Finally, list the user's observable actions and behaviors while using the system in the Do quadrant. These are the physical or digital interactions you witnessed, such as clicking a specific button or hesitating at a menu. This quadrant bridges the gap between what users claim they do and what they actually do. After the map is full, you must apply the synthesis process to condense observations into a shareable artifact. Gather the team to review all sticky notes, identify patterns, and remove any duplicate insights to create a single, cohesive output. This step transforms a cluttered board of individual ideas into a unified team understanding that everyone can rely on. The final result is a permanent, shareable artifact that serves as a continuous reminder of who you are designing for. This single output keeps the user's perspective visible throughout your design process, ensuring decisions remain centered on human needs. By following this sequence, you turn raw data into actionable guidance that drives your project forward. Key Points: Think: Document what is important to the user, their goals, and their internal thoughts. Feel: Capture the user's emotional states, frustrations, and anxieties during interaction. Say: Record exactly what the user explicitly states in interviews or feedback. Do: List the user's observable actions and behaviors while using the system. Synthesizing and Avoiding Pitfalls Let's say you have a whiteboard covered in sticky notes from your latest interview session. Your first job is to review those notes to identify patterns, remove duplicates, and condense the chaos into a single, cohesive output. This synthesis step turns scattered observations into a clear picture of the user. Watch out for a common pitfall where the team confuses what a user says versus what they think. If you mix these up, your map reflects your assumptions rather than observed behaviors, which ruins the accuracy of the artifact. You must distinguish between the two to keep your insights grounded in reality. If your map becomes cluttered with too many overlapping ideas, pause to group similar notes and vote on the most critical insights. This recovery strategy helps you focus on what truly matters before you finalize the design. By doing this, you ensure the final artifact drives better decisions. Key Points: Synthesis: Review sticky notes to identify patterns, remove duplicates, and condense into a single cohesive output. Pitfall Alert: Distinguish between what a user 'says' versus what they 'think' to avoid assumptions. Recovery Strategy: If the map is cluttered, group similar notes and vote on the most critical insights. Your Next Action In your next project, schedule a thirty-minute workshop with your team to define one specific user role. This clear definition anchors the entire session, ensuring everyone focuses on the distinct tasks and challenges that person faces. Guide the team to populate the four quadrants of Think, Feel, Say, and Do using your existing research data. You must cite specific evidence for every sticky note placed, rather than filling the map with speculation or assumptions. Finally, transform those synthesized sticky notes into a permanent, shareable artifact that informs your next design decision. This single, cohesive output keeps your team aligned on real user needs. You now have a structured way to see through your user's eyes, turning raw observations into actionable design guidance. Key Points: Action: Schedule a 30-minute workshop with your team to define one specific user role. Task: Guide the team to populate the four quadrants using your existing research data. Outcome: Transform the final sticky notes into a permanent, shareable artifact to inform your next design decision.