Empathy map

Understanding your users through structured observation

An empathy map is a collaborative visualisation tool that captures what we know about a user's behaviours, thoughts, feelings, and motivations, helping teams develop deeper understanding and more human-centred solutions.

In our rush to solve problems and deliver solutions, it's surprisingly easy to lose sight of the people we're actually trying to help. We make assumptions based on our own experiences, rely on secondhand data, or simply project what we think users want rather than understanding what they actually need. This disconnect between intention and reality lies at the heart of countless failed products, services, and initiatives.

The empathy map offers an antidote to this common pitfall. By providing a structured framework for capturing and organising user insights, this powerful design thinking tool helps teams move beyond assumptions and develop genuine understanding of the people they serve. Whether you're designing a new product, improving a service, or simply trying to better understand your stakeholders, the empathy map transforms scattered observations into actionable insights.

What an empathy map reveals about your users

An empathy map is a visual framework that organises user research into four key quadrants: what users Say, Think, Do, and Feel. This structured approach helps teams synthesise observations, interviews, and research data into a coherent picture of user experience, motivations, and pain points.

The empathy map works by externalising assumptions and making them visible for team discussion and validation. Rather than keeping user insights locked in individual team members' heads, the empathy map creates a shared reference point that everyone can contribute to, challenge, and build upon.

Unlike personas, which present generalised user archetypes, an empathy map focuses on specific contexts and situations. It captures the nuanced reality of user experience in particular moments, helping teams understand not just who their users are, but how they experience specific challenges, opportunities, or interactions.

This granular focus makes the empathy map particularly valuable for identifying gaps between what users say they do and what they actually do, or between their expressed needs and their underlying motivations. These insights often reveal the most promising opportunities for innovation and improvement.

The evolution of empathy mapping in design practice

The empathy map emerged from the design thinking methodology developed at Stanford's d.school in the early 2000s, though its roots trace back to earlier user-centred design practices and ethnographic research methods. Dave Gray of XPLANE is widely credited with formalising the empathy map format that's now used across industries worldwide.

The tool gained prominence as design thinking spread beyond traditional design disciplines into business strategy, social innovation, and organisational development. Companies like IDEO and IBM incorporated empathy mapping into their design processes, demonstrating its value for understanding complex user needs in diverse contexts.

The empathy map's adoption accelerated during the digital transformation wave of the 2010s, as organisations recognised the need for more systematic approaches to user understanding. Unlike traditional market research methods that often relied on indirect feedback, the empathy map provided a framework for synthesising direct observation and qualitative insights.

Today, the empathy map has evolved beyond its original design thinking context to become a standard tool in customer experience, product management, marketing, and even internal organisational development. Its enduring popularity reflects its ability to make abstract user insights concrete and actionable for multidisciplinary teams.

When and where to deploy empathy mapping

Empathy mapping proves most valuable during the early stages of any user-centred project, particularly when teams need to align around user understanding or challenge existing assumptions. The empathy map excels in situations where you have qualitative research data - interview transcripts, observation notes, or feedback - that needs to be synthesised into actionable insights.

Product development teams frequently use empathy mapping during discovery phases to understand user pain points and unmet needs. Service design initiatives rely on empathy maps to capture the emotional journey users experience across different touchpoints and interactions.

The empathy map also serves as a powerful tool for stakeholder alignment, particularly when team members have different perspectives on user needs or priorities. By creating a shared visual representation of user experience, the empathy map helps teams move from opinion-based discussions to evidence-based decision-making.

Internal organisational applications include change management initiatives, where empathy mapping helps leaders understand employee experiences during transitions, and customer service improvements, where teams map the emotional journey of customers experiencing problems or seeking support.

Creating your empathy map: A systematic approach

Preparation: Gathering the raw material

Before diving into empathy map creation, ensure you have sufficient user research to work with. The empathy map is a synthesis tool, not a research method itself, so its effectiveness depends entirely on the quality and depth of your underlying user insights.

Ideal source material includes interview transcripts, observational notes, customer feedback, support tickets, or any other direct user input. Avoid relying solely on internal assumptions or secondhand reports - the empathy map's power comes from grounding insights in actual user evidence.

Assemble a diverse team representing different perspectives and expertise areas. The empathy map creation process benefits from multiple viewpoints, as different team members often notice different patterns or insights in the same user data.

Example: A healthcare app team preparing to create an empathy map might gather patient interview transcripts, observation notes from clinic visits, support ticket themes, and app usage analytics before beginning their mapping session.

Setting up your empathy map canvas

The traditional empathy map consists of four quadrants arranged around a central user representation. Label these quadrants clearly: "Says" (direct quotes and statements), "Thinks" (thoughts, beliefs, and assumptions), "Does" (actions and behaviours), and "Feels" (emotions and feelings).

Some teams add additional sections for "Pains" (frustrations, obstacles, and challenges) and "Gains" (motivations, goals, and desired outcomes) to capture insights that might not fit neatly into the four main quadrants.

Place a representation of your specific user or user scenario in the centre. This might be a photo, sketch, or simply a name and brief description. The key is maintaining focus on a specific person in a specific context rather than trying to map generic user types.

Example: Rather than mapping "busy professionals," focus on "Sarah, a working mother of two, trying to book a medical appointment during her lunch break while managing client calls."

Populating the "Says" quadrant

Begin with the "Says" quadrant, as direct quotes provide the most concrete foundation for your empathy map. Transfer actual user statements from your research, maintaining their original language rather than paraphrasing or interpreting.

Look for patterns in language use, recurring phrases, or specific terminology users employ. Pay attention to what users emphasise, repeat, or seem passionate about. Also note contradictions between different statements, as these often reveal important tensions or conflicting priorities.

Include both explicit statements about needs or problems and casual comments that might reveal underlying attitudes or assumptions. Sometimes the most valuable insights come from throwaway remarks or emotional reactions rather than direct responses to questions.

Example: In the healthcare app empathy map, the "Says" section might include quotes like "I never have time to call during office hours," "The waiting room is always packed," and "I wish I could just see what appointments are available."

Mapping what users think

The "Thinks" quadrant captures internal mental processes - the thoughts, concerns, and beliefs that users might not always articulate directly. This section requires more interpretation than the "Says" quadrant, as you're inferring cognitive processes from observed behaviours and stated concerns.

Look for evidence of underlying assumptions, decision-making criteria, or mental models users employ. Consider what users prioritise, what they worry about, and how they make sense of their situation or environment.

Pay attention to gaps between what users say and what they seem to think. These disconnects often reveal important insights about social desirability bias, unconscious motivations, or competing priorities that users struggle to articulate.

Example: While patients might say they want faster appointments, your empathy map might reveal they think "Good doctors must be busy, so quick availability might mean lower quality care."

Capturing user actions and behaviours

The "Does" quadrant documents observable behaviours, actions, and interactions. Focus on what users actually do rather than what they say they do, as these often differ significantly. Include both digital behaviours (clicks, searches, navigation patterns) and physical actions (body language, environmental interactions, workarounds).

Document the sequence of actions users take, noting where they pause, struggle, or deviate from expected paths. Pay particular attention to workarounds or adaptations users create to overcome obstacles or limitations in current solutions.

Consider the full context of user behaviour, including actions that happen before and after their direct interaction with your product or service. These contextual behaviours often reveal important insights about user needs and motivations.

Example: The empathy map might show that patients frequently start booking appointments online but abandon the process to call instead, suggesting usability issues or missing information in the digital experience.

Understanding emotional experiences

The "Feels" quadrant captures the emotional dimension of user experience - feelings, emotions, and affective responses throughout their journey. This section helps teams understand not just what users do, but how they feel about it.

Look for emotional patterns, triggers, and transitions. Note when users express frustration, excitement, confusion, relief, or any other emotional states. Pay attention to intensity levels and how emotions change throughout different parts of their experience.

Consider both expressed emotions (what users directly state) and observed emotions (what you notice through tone, body language, or behaviour). Sometimes users downplay negative emotions or struggle to articulate positive ones, making observation crucial.

Example: Patients might feel "anxious about wait times," "frustrated by phone systems," and "relieved when they finally connect with a real person," revealing the emotional rollercoaster of appointment booking.

Adding pains and gains for deeper insight

Many empathy map practitioners enhance the basic four-quadrant model by adding explicit sections for user pains and gains. This addition helps teams focus specifically on problem areas and motivation factors that drive user behaviour.

Pains include frustrations, obstacles, barriers, fears, and any negative aspects of the current experience. These often represent the most immediate opportunities for improvement or innovation.

Gains encompass goals, motivations, desired outcomes, and positive experiences users seek. Understanding what users hope to achieve helps teams design solutions that deliver genuine value rather than simply removing friction.

Example: Key pains might include "Uncertainty about appointment availability" and "Disruption to work schedule," whilst gains could include "Confidence in healthcare access" and "Seamless integration with daily routine."

Advantages and limitations of empathy mapping

Why empathy maps work so well

The empathy map's greatest strength lies in its ability to make abstract user insights tangible and actionable for teams. By organising scattered research findings into a clear visual format, the empathy map transforms overwhelming data into focused understanding that teams can actually use to drive decisions.

The collaborative nature of empathy map creation builds shared understanding across team members with different backgrounds and expertise. This alignment proves crucial for maintaining user focus throughout project development, as everyone works from the same foundational understanding of user needs and experiences.

Empathy mapping also excels at revealing gaps and contradictions in user understanding. When teams attempt to populate all four quadrants, they often discover areas where their knowledge is incomplete or assumptions are unfounded, highlighting priorities for additional research.

The visual format makes empathy maps particularly effective for communication with stakeholders who might not engage deeply with traditional research reports. The empathy map tells a story about user experience that's accessible to both technical and non-technical audiences.

Where empathy maps fall short

Despite their utility, empathy maps have notable limitations that teams should acknowledge. The tool works best with qualitative research data, but can struggle to incorporate quantitative insights or large-scale behavioural patterns effectively.

Empathy mapping requires interpretation and synthesis, which introduces potential bias or misrepresentation of user insights. Teams might unconsciously emphasise data that supports existing assumptions whilst downplaying contradictory evidence.

The empathy map format can also oversimplify complex user experiences that don't fit neatly into the four quadrant structure. Users facing multifaceted problems or operating in dynamic environments might resist clear categorisation into says/thinks/does/feels frameworks.

Finally, empathy maps represent snapshots of user experience at specific moments rather than capturing how needs and behaviours evolve over time. This limitation makes them less suitable for understanding long-term user journeys or changing circumstances.

Advanced empathy mapping techniques and considerations

Successful empathy mapping requires careful attention to several factors that significantly impact the tool's effectiveness. User selection proves crucial - the empathy map works best when focused on specific individuals in particular contexts rather than attempting to map general user types or broad demographics.

Consider creating multiple empathy maps for different user scenarios, contexts, or journey stages rather than trying to capture everything in a single map. This approach provides more nuanced insights whilst maintaining the tool's clarity and focus.

Research from the Nielsen Norman Group emphasises the importance of grounding empathy maps in actual user research rather than assumptions or brainstorming. The tool's credibility and utility depend entirely on the quality of underlying user insights.

Digital tools can enhance empathy mapping for remote teams or complex projects, but many practitioners prefer physical sticky notes and wall space for the tactile, collaborative experience they provide. Choose formats that best support your team's working style and project needs.

Regular empathy map updates help maintain user focus throughout project development. As teams gather additional research or user feedback, updating existing empathy maps ensures continued alignment with evolving user understanding.

Consider combining empathy mapping with other design thinking tools like journey mapping, persona development, or jobs-to-be-done frameworks. The empathy map provides foundational user understanding that enhances these complementary approaches.

Conclusion

The empathy map stands as one of design thinking's most practical and accessible tools, transforming abstract user research into concrete insights that teams can act upon. Its power lies not in complexity but in clarity - by organising user understanding into a simple visual framework, the empathy map helps teams maintain human focus throughout their work.

Whether you're developing new products, improving existing services, or simply trying to better understand your stakeholders, the empathy map provides a proven approach to user insight synthesis. It bridges the gap between research and action, ensuring that user understanding translates into user-centred solutions.

The empathy map's collaborative nature makes it particularly valuable for building shared understanding across diverse teams. When everyone works from the same empathy map, decisions become more consistent, solutions more coherent, and outcomes more aligned with genuine user needs.

Success with empathy mapping requires commitment to user research and honest synthesis of findings. The tool enhances good research but cannot compensate for poor user understanding. When grounded in solid research and applied thoughtfully, the empathy map becomes an invaluable asset for any team committed to creating genuinely user-centred solutions that address real human needs and experiences.