Creating an empathy map involves four steps: identify the target users and research objectives, gather data and fill out the six sections, share and discuss findings to reach consensus, and use the identified needs to inform product or service adjustments. The key is not to fill every box, but to ground the map in user interviews, feedback, and observations. This helps the team avoid mistaking its assumptions for customers’ actual circumstances.
Identify the target users, then prepare material for discussion
Before you begin, answer two questions: “Which group of people do we want to understand?” and “Which of their needs do we want to explore?” According to Welly’s guide, teams should gather information from questionnaires, interviews, or customer satisfaction surveys in advance and share it with everyone participating in the discussion.
When interviewing and observing users, look beyond what they say to understand their needs, backgrounds, values, and motivations. For example, the guide’s hypothetical laptop development case focuses on business professionals who frequently travel with their laptops. The usage scenario is working between visits to different clients. This is more specific than simply writing “business professionals” and gives the team a common scenario to discuss.
Use six sections to understand users’ circumstances
This approach follows the six-section version in Welly’s guide. You can draw the map on a whiteboard and write information about the target users in the center. A facilitator can then ask questions while participants write their input on sticky notes and place them in the corresponding sections:
- Think and feel: What are users thinking? What is their experience like?
- Hear: What information do they receive? What do they hear others say?
- See: What do they usually notice? What do they see in the market?
- Say and do: What do they say? What actions do they take?
- Pains: What obstacles do they encounter? What worries or angers them?
- Gains: What do they want? What do they need to gain?
These questions help participants organize data, not invent answers. Seeing things from users’ perspectives still requires observation and an understanding of the target audience.
Group similar information, then identify pain points and expectations
Once the sticky notes are in place, group similar information together. In the hypothetical example above, “tabs take too long to open” and “startup takes too long” are grouped under “insufficient laptop performance.” The team then uses these categories to discuss what constraints users face and what improvements they hope for.
The resulting concept is a lightweight, portable laptop with moderate performance and long battery life, designed to meet basic work, battery, and portability needs. This is a product concept based on a hypothetical scenario; it does not mean that all business travelers have the same needs.
Share findings and reach consensus to inform adjustments
After completing the sections, the facilitator can guide participants as they take turns sharing, review the overall findings together, and work toward consensus. The completed map can inform product design, service adjustments, or improvements to operational strategy. The team should continue to validate and revise the map to refine its customer profile, rather than treating the first version as definitive.
Empathy maps: perspectives from across the web
When is an empathy map useful?
An empathy map can be useful when a team wants to take a fresh look at its customers, develop a more detailed persona, or map customers' behaviors and reactions during interviews. When developing a new product or service, it can also help the team analyze the target audience's needs and potential difficulties. However, it is a tool to support understanding and discussion, not a substitute for knowing your customers.
Can empathy maps and personas be used together?
Yes. An empathy map can help a team develop a persona by encouraging discussion of users' feelings, behaviors, difficulties, and needs. This helps the team understand customers more deeply. Both tools can help teams understand users, but the findings should still be based on data about the target audience rather than imagination alone.
After organizing user data, how can you move on to defining the problem?
Start with three questions: What kind of person is the user? What do they need? What motivates that need? Then try to define the problem in one concise sentence. This method comes from the “Define” stage of design thinking and can also serve as a follow-up exercise after completing an empathy map. Base the problem definition on the available data rather than drawing unsupported conclusions about users.
References
- 設計思考是什麼?使用者為本的設計思考5步驟!業界必學設計思維welly.tw · 2023-03-13T00:43:00.889Z — Discusses: After organizing user data, how can you move on to defining the problem?
- 同理心地圖是什麼?同理心地圖製作教學、範例一次看!welly.tw · 2024-07-19T07:08:09.020Z — Discusses: When is an empathy map useful?; Can empathy maps and personas be used together?
