Empathy Map Canvas by Jack León
The empathy map, developed by Dave Gray, founder of XPLANE, takes user personas to a whole new level. It puts you in the shoes of your users.
How to use the Empathy Map Canvas
This is best done in a collaborative environment with a cross-functional team and a variety of backgrounds. Frankly, it can be a little tiresome to do on your own, and you're likely to cut corners as a result 🙂 Ideally this exercise is facilitated by someone who has experience running workshops.
Step 1. The Goal
The Goal consists of 2 parts, numbered 1 and 2 on the canvas.Number 1, the description of a person representing your user, their role, and the specific situation that you are interested in helping with.Number 2, what they're trying to do. This is could be a part of a job, or a decision they need to make. It is important to articulate what success looks like for your user.This part is normally led by a Product Owner or a UX lead or analyst.Make sure everyone understands who the user is, what the user is trying to do, and the context within which the behavior is being performed.
Step 2. Around the Head
Now go around the outside of “The Big Head” following the numbers from 3 through to 6. Everyone grabs a bunch of sticky notes and joins in, trying to imagine the world from the user’s perspective.Everyone should spend around 5 minutes on each area; SEE, SAY, DO and HEAR. A great way to run this part of the exercise is using the working together alone technique. Everyone is given time to come up with their own ideas, followed by a quick tidy-up. The tidy-up phase is optional and might consist of a quick deduplication, a brief discussion if any notes are not clear, and sorting of the notes if relevant. Do this for each section from 2 to 6.
Step 3. Inside the Head
Now we are going inside the head of our user. Before you do, the facilitator should take 5 minutes to quickly summarise all the sticky notes in sections 1 through to 6. This will give everyone time to internalize and expand their empathy for the user.Section 7 has 3 areas, Pains, Gains, and others. As the canvas states, Pains are things that are worrying our user, Gains are things our user wants and others is an area to put notes which are hard to classify but feel important.Again, have the team work together alone, giving everyone 8-10 minutes on section 7. After that, the facilitator will optionally organize the sticky notes by deduplicating and sorting if required.
Conclusion
The exercise is now over, and the facilitator might decide to summarise and request clarification where notes are not clear.The Empathy Map Canvas is an indispensable part of Design Thinking, along with Persona Design and User Journey Mapping. Using these artifacts to shape proposition design ensures the team is developing customer-centric solutions.
This template was created by Jack León.
Get started with this template right now.
Product Development Roadmap Template
Works best for:
Product Management, Software Development
Product development roadmaps cover everything your team needs to achieve when delivering a product from concept to market launch. Your product development roadmap is also a team alignment tool that offers guidance and leadership to help your team focus on balancing product innovation and meeting your customer’s needs. Investing time in creating a roadmap focused on your product development phases helps your team communicate a vision to business leaders, designers, developers, project managers, marketers, and anyone else who influences meeting team goals.
Job Map Template
Works best for:
Design, Desk Research, Mapping
Want to truly understand your consumers’ mindset? Take a look at things from their perspective — by identifying the “jobs” they need to accomplish and exploring what would make them “hire” or “fire” a product or service like yours. Ideal for UX researchers, job mapping is a staged process that gives you that POV by breaking the “jobs” down step by step, so you can ultimately offer something unique, useful, and different from your competitors. This template makes it easy to create a detailed, comprehensive job map.
User Empathy Map
Works best for:
Market Research, Research & Design
User Empathy Map template helps you visualize user experiences and needs. It’s an essential tool for teams looking to design products that resonate with their users. Use this template to build empathy and improve user satisfaction.
Storyboard Template
Works best for:
Design Thinking
While storyboard is typically associated with planning out scenes for a movie or TV show, it’s been widely adopted throughout the business world. A storyboard is a sequence of illustrations that are used to develop a story. You can use the Storyboarding template anytime you’d like to really put yourself in a customer or user’s position and understand how they think, feel, and act. This tactic can be especially useful when you know there’s a problem or inefficiency with an existing process. You can storyboard existing processes or workflows and plan how you would like them to look in the future.
Empathy Map by Lucie Agolini
Works best for:
Research & Design, Market Research
The Empathy Map template offers a straightforward way to visualize user insights. By focusing on what users think, feel, say, and do, you can develop a deeper understanding of their needs. This template is perfect for improving user experiences and driving customer satisfaction.
Prune the Product Tree Template
Works best for:
Design, Desk Research, Product Management
Prune the Product Tree (also known as the product tree game or the product tree prioritization framework) is a visual tool that helps product managers organize and prioritize product feature requests. The tree represents a product roadmap and helps your team think about how to grow and shape your product or service by gamifying feedback-gathering from customers and stakeholders. A typical product tree has four symbolic features: the trunk, which represents the existing product features your team is building; the branches, each of which represents a product or system function; roots, which are technical requirements or infrastructure; and leaves, which are new ideas for product features.