Decision Matrix
Create a weighted matrix to evaluate complex decisions objectively.
Develops: Critical Thinking
The ability to analyze information objectively and make reasoned judgments
Learn More- 1
List your options
- 2
Identify criteria that matter
- 3
Weight each criterion
- 4
Score each option
- 5
Calculate and reflect on results
Continue Reading
Get full access to Decision Matrix and 20+ other proven skill-building techniques.
Why This Works
The Science Behind Empathy Mapping
Empathy Mapping is a collaborative visualization tool used to articulate what we know about a particular type of user or stakeholder. Originally developed by XPLANE as part of the design thinking toolkit, it has become a fundamental practice in user experience design, product development, and customer experience strategy.
Why It Works:
Scientific Support:
Historical Context:
Empathy mapping emerged from the design thinking movement popularized by IDEO and Stanford d.school in the 1990s and 2000s. David Kelley, Tim Brown, and other design pioneers adapted ethnographic and anthropological methods for business contexts.
The technique builds on:
Empathy maps are now used for:
Key Insight: Most business failures stem not from technical incompetence but from misunderstanding user needs. Empathy mapping prevents this by forcing teams to articulate, examine, and validate their understanding of the people they serve.
Step-by-Step Examples
E-commerce User Experience Redesign
Problem Definition
Analytics show 70% of users add items to cart but don't complete purchase. Business team assumes price is the issue.
Data Collection
Team conducts user interviews, reviews support tickets, watches user testing sessions, and analyzes customer feedback.
Empathy Map Creation
Collaborative session creates empathy map for typical user 'Sarah, busy mom shopping during lunch break.' Key findings: She's rushed, skeptical about security, feels guilty about spending, and frustrated by complicated forms.
Insight Generation
The team realizes price isn't the primary issue. Key insights: Security concerns are paramount, time pressure is high, creating account is a barrier, hidden costs feel deceptive.
Solution Design
Redesign includes guest checkout, prominent security badges, shipping calculator in cart, one-page checkout, clear return policy above fold. Cart abandonment drops to 35%.
💡 Without the empathy map, the team would have focused on pricing strategies. The structured empathy exercise revealed friction points they hadn't considered.
Conflict Resolution in Team Settings
Problem Identification
Product team feels engineering is slow and resistant to change. Engineering feels product is unrealistic and disorganized. Communication has broken down.
Empathy Mapping Workshop
Facilitator has each team create empathy maps for the other team. Then they create maps for their own team and compare.
Product Team Discovers About Engineering
Engineering feels overwhelmed by constant changes, unappreciated for technical work, and anxious about system stability. They're not being difficult - they're protecting quality.
Engineering Team Discovers About Product
Product feels frustrated by slow cycles, pressured by sales commitments and customer demands. They're not being unrealistic - they're responding to market needs.
Resolution
Teams realize they're aligned in wanting good outcomes but disconnected in process understanding. They implement joint planning, shared roadmap, and better communication protocols.
💡 Empathy mapping revealed that both teams felt misunderstood and pressured. Creating space to articulate each other's perspectives transformed conflict into collaboration.
Healthcare Patient Experience
Challenge
Patients frequently miss appointments, don't follow treatment plans, and report low satisfaction. Staff assumes patients are non-compliant.
Empathy Investigation
Shadowing, interviews, and patient journey mapping reveal complex barriers. Team creates empathy maps for different patient personas.
Patient's Reality Revealed
Patient can't afford medications, feels judged by providers, confused by medical jargon, intimidated by clinical setting, and lonely in managing condition. Non-adherence isn't resistance - it's overwhelmed capacity.
Service Redesign
Changes: online scheduling, telemedicine options, cost estimates upfront, teach-back method for instructions, community health worker support, non-judgmental communication training.
Outcomes
Show rates increase from 65% to 85%, patient satisfaction scores improve, treatment adherence increases. Staff realizes 'non-compliance' was actually systems failure.
💡 Empathy mapping shifted attribution from patient characteristics to system design. This reframing enabled solutions that addressed actual barriers rather than blaming patients.
Common Pitfalls to Avoid
Mistake 1: Projection Bias
Projecting your own thoughts, feelings, and reactions onto users rather than discovering their actual perspectives. This often takes the form of 'If I were the user, I would...' Counteract by basing maps on real data and observations, not imagination.
Mistake 2: Surface-Level Analysis
Stating obvious or superficial observations rather than digging deeper. Instead of 'user wants to buy things,' explore the underlying motivations, anxieties, and contexts that shape their decision-making. Ask 'why' repeatedly to go deeper.
Mistake 3: Ignoring Context and Environment
Focusing only on the individual user while ignoring the systems, environments, and constraints that shape their experience. A complete empathy map considers physical space, social context, time pressures, and environmental factors.
Mistake 4: Confusing Sympathy with Empathy
Sympathy is feeling for someone ('I feel bad for them'); empathy is understanding with someone ('I understand their experience'). Empathy maps should reflect understanding of their perspective, not your emotional response to their situation.
Mistake 5: Skipping Validation
Creating empathy maps based on assumptions and never testing whether they're accurate. Always validate empathy maps through direct user research, observation, or feedback. Treat them as hypotheses to be tested, not conclusions.
Mistake 6: Overgeneralization
Creating empathy maps for 'the user' as if all users are identical. Different user segments may have dramatically different experiences. Create multiple maps for different personas rather than one generic map.
Mistake 7: Neglecting Non-Verbal and Emotional Dimensions
Focusing only on what users explicitly say while missing what they don't say, their body language, tone, and emotional subtext. Much of user experience is communicated non-verbally or through what's left unsaid.