Day#45: The practical guide to empathy maps; 10-minute user personas (part 1)

Day#45: The practical guide to empathy maps; 10-minute user personas (part 1)

The website I found the information on, has a few interesting articles that i will be doing a number of posts on in the future. For now lets dive into empathy maps,

Where do empathy maps come in

  • Visualize user needs
  • A starting point on user knowledge
  • Quick to put together, so less resources needed and can be reiterated when more data is collected

When to use an empathy map

  • Most useful at the beginning of the design process
  • After initial user research
  • I found the below so informative and to the point, I just copied and pasted the quote, I often see it on certain jobs. The company wants to solve every problem under the sun and doesn’t zone in and focus on what’s most important to their client

“Product strategy is about solving problems, and empathy maps shed light on which problems to solve, and how. This also makes them a great tool for redesigns as well.”

Empathy map format

  • Common templates for UX empathy maps are mapped out in 4 quadrants
  • These 4 quadrants outline the users internal experience, it will always contain thoughts, feelings and actions of the user
  • The diagram in the article which I really encourage you to take a look at has the following categories; tasks, feelings, influences, pain points and over all goals

Common variants noted in the article include

  • Sights: Where the users eye goes
  • Quotes: Things the user says
  • Influences: If they have heard information pertaining to the service/experience of the application

I personally love having a template it helps me focus on the task at hand, in an interview scenario with a participant I want to know that I am sticking to all important criteria and templates like this can help you gain valuable data to use later. There is a second part of this article so check it out tomorrow!

Bye for now!

Leave a Reply

Your email address will not be published. Required fields are marked *