An introduction to empathy maps and how they are used.
An empathy map is a way of visually organising research findings to easily determine what users are thinking and feeling. This makes it easier to discover areas of stress, doubt, or discomfort for users, helping you to understand their personal and emotional experiences while using your service.
In step 1.8, we learned that personas can be used to create the human connection, by reminding teams that we are building services to help people. This is what empathy means – understanding other people in terms of our shared human experiences – and an empathy map is all about visually representing this.
An empathy map helps you to:
organise and make sense of qualitative user research data from interviews, surveys, or session notes
find gaps in the research in the form of missing information, helping you to plan future research
easily share user data within the team, ensuring that everyone understands your users and their needs
capture the emotional and personal side of the user journey
An empathy map is made up of four sections containing information about what the user says, thinks, feels and does:
What the user says
This section should contain information that users have said or written in interviews, group sessions or in their responses to surveys or questionnaires.
Exact words should be used – quotes bring the voice of the user into the design process, so you can focus on their needs. In this section, you should include the most obvious or explicit statements of what users say they need or want, or success or problem areas.
What the user thinks
This section should contain information about what the user is thinking, but may not be saying out loud.
Users may worry about making a mistake or feel unsure about what to do next. These thoughts explain why the user behaves a certain way and can help teams understand where the service design might need to be clearer or offer more help. This information can be found out through asking the user open questions about what they are thinking such as “What did you think when you were doing this?” or “What did you think when that happened?”
What the user does
This section should contain information about what the user does during research sessions such as observations or usability testing.
User actions give important clues about how the service feels to them. Pauses or hesitations might indicate that they do not understand the process, while skipping steps or missing important information could show that the service design needs to be made clearer. Even small actions can show where the service works well or where it needs improvement.
What the user feels
This section should contain information about what the user feels.
Feelings shape every action the user takes – stress, calm, or confusion can change how a person moves through a task. Understanding how the user feels helps explain why they may stop or keep using the service.
As with user thoughts, this can be more difficult to find out, but you can directly ask users open questions such as “What did you feel about this?” or “How did you feel when you were doing that?” to get this information.
Empathy maps should always be based on data gathered from user research. If you are missing information, it means you need to do more research – you should never guess, assume or make things up.
Empathy maps and personas
As we learned in step 1.9, user stories can be written using user personas. We can do the same with empathy maps.
Building an empathy map for a persona creates more depth and detail by showing additional information about their thoughts, feelings and actions.
As a reminder, a persona is not a real person, but it represents a real group of users who share certain attitudes, behaviours and characteristics. An empathy map for a persona can help consolidate different user responses that share central themes to help effectively communicate lots of information about the represented user group.