User Empathy Mapping Template

📄
user_empathy_mapping_template.md
Markdown • 38,020 bytes
💾 Download
---
title: "User Empathy Mapping Template"
methodology: "universal"
complexity: "advanced"
owner: "mirichard"
updated: "2026-10-08"
domain: "Stakeholder"
primary_principles: ["stakeholder-engagement", "systems-thinking"]
secondary_principles: ["evidence-based-decisions"]
principle_rationale: "Converts user research signals into a shared system view that strengthens stakeholder understanding and evidence-backed choices."
tags: ["design-thinking", "empathy-mapping", "user-research", "stakeholder-management"]
---

# User Empathy Mapping Template

## Overview
This template provides a structured approach to creating empathy maps that help teams understand users' thoughts, feelings, actions, and motivations. Empathy mapping is a core design thinking tool that transforms user research into actionable insights for product and project development.



## When to Use
- Use when interview or observation data exists and the team needs a single synthesis artifact for user needs, constraints, and motivations.
- Apply before prioritization when product, design, and delivery leads disagree on which user outcomes matter most.
- Run this when preparing discovery readouts that must convert qualitative research into actionable delivery hypotheses.

## When NOT to Use
- Do not use with fabricated or second-hand assumptions when no primary research evidence has been collected.
- Do not mistake one-way status updates for stakeholder understanding; use structured feedback loops instead (see [Stakeholder broadcast](../../../docs/principles/anti-patterns.md#stakeholder-broadcast)).
- Do not freeze the map as permanent truth when user behavior is changing across segments or journey stages.

## Pairs Well With
- [Design Thinking Workshop Template](design_thinking_workshop_template.md)
- [Customer Validation Framework](../lean-startup/customer-validation-framework.md)

Decision context model reference: 800-801-context-assessment-model.md
## Template Information
- **Methodology:** Design Thinking - Empathize Stage
- **Purpose:** Synthesize user research into empathy maps for deeper understanding
- **Audience:** UX Researchers, Product Managers, Design Teams, Project Managers
- **Duration:** 1-3 hours per empathy map
- **Prerequisites:** User research data (interviews, observations, surveys)

---

## Empathy Mapping Framework

### What is an Empathy Map?

An empathy map is a collaborative visualization used to articulate what we know about a particular type of user. It externalizes knowledge about users in order to create a shared understanding of user needs, and aid in decision making.

#### Four Quadrants of Traditional Empathy Map:
```
User Empathy Map

SAYS                     |  THINKS
Direct quotes and        |  Thoughts, beliefs, 
defining words          |  preoccupations
                        |
DOES                    |  FEELS  
Actions and behaviors   |  Emotions and feelings
```

#### Advanced Six-Segment Empathy Map:
```
Extended User Empathy Map

THINKS & FEELS          |  HEARS
Internal thoughts       |  What others say,
and emotions           |  influencing factors
                       |
SEES                   |  SAYS & DOES
Environment,           |  Public words
people, offerings      |  and actions
                       |
PAIN POINTS            |  GAINS
Frustrations,          |  Wants, needs,
obstacles, risks       |  success measures
```

---

## Pre-Mapping Preparation

### Research Data Collection

#### User Research Methods Alignment
```yaml
research_method_mapping:
  user_interviews:
    best_for: "Deep insights into thoughts, feelings, motivations"
    data_types: ["Direct quotes", "Emotional responses", "Personal stories"]
    empathy_map_contribution: "Strong coverage of all quadrants"
    
  observational_studies:
    best_for: "Understanding actual behaviors and contexts"
    data_types: ["Observed actions", "Environmental factors", "Usage patterns"]
    empathy_map_contribution: "Strong for DOES and SEES quadrants"
    
  surveys:
    best_for: "Quantifying attitudes and preferences at scale"
    data_types: ["Stated preferences", "Demographic data", "Rating scales"]
    empathy_map_contribution: "Supporting data for validation"
    
  diary_studies:
    best_for: "Understanding experiences over time"
    data_types: ["Daily experiences", "Emotional journeys", "Context changes"]
    empathy_map_contribution: "Rich temporal insights across all quadrants"
```

#### Data Organization Template
```
Research Data Organization Worksheet

User Segment: [Target user group]
Research Period: [Date range]
Research Methods Used: [List methods]
Number of Participants: [Count]

Raw Data Categories:

Direct Quotes (SAYS):
├── "[Quote 1 with context]"
├── "[Quote 2 with context]"
├── "[Quote 3 with context]"
└── "[Quote 4 with context]"

Observed Behaviors (DOES):
├── [Behavior 1: context and frequency]
├── [Behavior 2: context and frequency]
├── [Behavior 3: context and frequency]
└── [Behavior 4: context and frequency]

Emotional Indicators (FEELS):
├── [Emotion 1: trigger and expression]
├── [Emotion 2: trigger and expression]
├── [Emotion 3: trigger and expression]
└── [Emotion 4: trigger and expression]

Thoughts and Beliefs (THINKS):
├── [Belief 1: evidence and context]
├── [Belief 2: evidence and context]
├── [Belief 3: evidence and context]
└── [Belief 4: evidence and context]

Environmental Factors (SEES):
├── [Factor 1: influence on behavior]
├── [Factor 2: influence on behavior]
├── [Factor 3: influence on behavior]
└── [Factor 4: influence on behavior]

External Influences (HEARS):
├── [Influence 1: source and impact]
├── [Influence 2: source and impact]
├── [Influence 3: source and impact]
└── [Influence 4: source and impact]
```

---

## Individual Empathy Map Templates

### Basic Four-Quadrant Empathy Map

#### Template Structure
```
Empathy Map for: [User Name/Persona]
Context: [When/where this applies]
Based on: [Research sources]

┌─────────────────────────┬─────────────────────────┐
│         THINKS          │          FEELS          │
│                         │                         │
│ What occupies their     │ What emotions do        │
│ thoughts? What are      │ they experience?        │
│ their beliefs?          │ What matters to them?   │
│                         │                         │
│ • [Thought 1]           │ • [Emotion 1]           │
│ • [Thought 2]           │ • [Emotion 2]           │
│ • [Thought 3]           │ • [Emotion 3]           │
│ • [Thought 4]           │ • [Emotion 4]           │
│                         │                         │
├─────────────────────────┼─────────────────────────┤
│          SAYS           │          DOES           │
│                         │                         │
│ What do they say?       │ What actions do         │
│ Direct quotes and       │ they take? Observable   │
│ defining words          │ behaviors               │
│                         │                         │
│ • "[Quote 1]"           │ • [Action 1]            │
│ • "[Quote 2]"           │ • [Action 2]            │
│ • "[Quote 3]"           │ • [Action 3]            │
│ • "[Quote 4]"           │ • [Action 4]            │
│                         │                         │
└─────────────────────────┴─────────────────────────┘

PAIN POINTS:                    GAINS:
• [Frustration 1]              • [Motivation 1]
• [Obstacle 2]                 • [Success measure 2]
• [Risk 3]                     • [Desired outcome 3]
```

#### Detailed Quadrant Guidelines

**THINKS Quadrant:**
```yaml
thinks_quadrant_guide:
  definition: "What goes through the user's mind during the experience"
  
  questions_to_explore:
    - "What are their major preoccupations?"
    - "What worries consume their thinking?"
    - "What are their hopes and dreams?"
    - "What beliefs drive their decisions?"
    - "What assumptions do they make?"
    
  data_sources:
    - "Interview responses about attitudes"
    - "Responses to 'what if' scenarios"
    - "Explanations of decision-making"
    - "Statements about beliefs and values"
    
  example_insights:
    - "Believes technology should be intuitive"
    - "Worried about making mistakes in front of colleagues"
    - "Assumes expensive means better quality"
    - "Thinks current process is unnecessarily complex"
    
  common_mistakes:
    - "Confusing what they say with what they think"
    - "Including public statements rather than private thoughts"
    - "Making assumptions without evidence"
```

**FEELS Quadrant:**
```yaml
feels_quadrant_guide:
  definition: "Emotional states and feelings during the experience"
  
  questions_to_explore:
    - "What emotions are they experiencing?"
    - "What are their fears and anxieties?"
    - "What excites or energizes them?"
    - "What frustrates or annoys them?"
    - "How do emotions change throughout the experience?"
    
  emotion_categories:
    primary_emotions: ["Joy", "Sadness", "Anger", "Fear", "Surprise", "Disgust"]
    secondary_emotions: ["Anxiety", "Excitement", "Frustration", "Confidence", "Relief"]
    
  data_sources:
    - "Emotional expressions during interviews"
    - "Body language observations"
    - "Tone of voice changes"
    - "Facial expressions"
    - "Emotional reactions to scenarios"
    
  example_insights:
    - "Frustrated when things don't work as expected"
    - "Anxious about learning new systems"
    - "Excited about possibilities for improvement"
    - "Proud when helping colleagues succeed"
```

**SAYS Quadrant:**
```yaml
says_quadrant_guide:
  definition: "What users actually verbalize - direct quotes and public statements"
  
  capture_guidelines:
    - "Use exact quotes when possible"
    - "Include context for when/where said"
    - "Note tone and emphasis"
    - "Capture both positive and negative statements"
    
  quote_categories:
    pain_points: "Complaints and frustrations"
    aspirations: "Goals and desires"
    processes: "How they describe current workflows"
    relationships: "Interactions with others"
    
  data_sources:
    - "Direct interview quotes"
    - "Overheard conversations"
    - "Social media posts"
    - "Support ticket descriptions"
    - "Meeting comments"
    
  example_insights:
    - "'I wish this was easier to use'"
    - "'My biggest challenge is...'"
    - "'What I really need is...'"
    - "'This never works the way I expect'"
```

**DOES Quadrant:**
```yaml
does_quadrant_guide:
  definition: "Observable actions and behaviors"
  
  behavior_types:
    task_behaviors: "How they accomplish specific tasks"
    workaround_behaviors: "Adaptations and shortcuts they create"
    social_behaviors: "How they interact with others"
    information_behaviors: "How they seek and share information"
    
  observation_focus:
    - "What do they do before, during, and after key tasks?"
    - "What tools or resources do they use?"
    - "How do they handle errors or problems?"
    - "What patterns exist in their behavior?"
    
  data_sources:
    - "Direct observation"
    - "Task analysis"
    - "Screen recordings"
    - "Activity logs"
    - "Workflow documentation"
    
  example_insights:
    - "Checks email every 5 minutes during work"
    - "Always asks colleague before trying new features"
    - "Creates personal spreadsheets to track information"
    - "Uses mobile device for quick tasks"
```

### Extended Six-Segment Empathy Map

#### Advanced Template Structure
```
Extended Empathy Map for: [User Name/Persona]

┌─────────────────────────┬─────────────────────────┐
│      THINKS & FEELS     │         HEARS           │
│                         │                         │
│ Internal mental and     │ What they hear from     │
│ emotional state         │ others and environment  │
│                         │                         │
│ Thoughts:               │ From colleagues:        │
│ • [Private thought 1]   │ • [Colleague input 1]   │
│ • [Private thought 2]   │ • [Colleague input 2]   │
│                         │                         │
│ Feelings:               │ From management:        │
│ • [Emotion 1]           │ • [Management input 1]  │
│ • [Emotion 2]           │ • [Management input 2]  │
│                         │                         │
│                         │ From industry/media:    │
│                         │ • [External input 1]    │
│                         │ • [External input 2]    │
├─────────────────────────┼─────────────────────────┤
│          SEES           │      SAYS & DOES        │
│                         │                         │
│ What they see in        │ Public words and        │
│ their environment      │ observable actions      │
│                         │                         │
│ Physical environment:   │ Says publicly:          │
│ • [Visual element 1]    │ • "[Public statement 1]"│
│ • [Visual element 2]    │ • "[Public statement 2]"│
│                         │                         │
│ People around them:     │ Does publicly:          │
│ • [Person/role 1]       │ • [Observable action 1] │
│ • [Person/role 2]       │ • [Observable action 2] │
│                         │                         │
│ Offerings/solutions:    │ Uses/consumes:          │
│ • [Product/service 1]   │ • [Tool/resource 1]     │
│ • [Product/service 2]   │ • [Tool/resource 2]     │
└─────────────────────────┴─────────────────────────┘

┌─────────────────────────┬─────────────────────────┐
│       PAIN POINTS       │         GAINS           │
│                         │                         │
│ Frustrations, obstacles │ Wants, needs, measures  │
│ fears, and risks        │ of success              │
│                         │                         │
│ Frustrations:           │ Wants/Needs:            │
│ • [Frustration 1]       │ • [Desired outcome 1]   │
│ • [Frustration 2]       │ • [Desired outcome 2]   │
│                         │                         │
│ Obstacles:              │ Success measures:       │
│ • [Barrier 1]           │ • [Success metric 1]    │
│ • [Barrier 2]           │ • [Success metric 2]    │
│                         │                         │
│ Fears/Risks:            │ Motivations:            │
│ • [Fear 1]              │ • [Driving force 1]     │
│ • [Fear 2]              │ • [Driving force 2]     │
└─────────────────────────┴─────────────────────────┘
```

---

## Team-Based Empathy Mapping Process

### Collaborative Mapping Workshop

#### Workshop Structure (2-3 hours)
```yaml
empathy_mapping_workshop:
  phase_1_setup:
    duration: "15 minutes"
    activities:
      - "Present user research summary"
      - "Introduce empathy mapping concept"
      - "Set workshop ground rules"
      - "Form diverse working groups"
    
  phase_2_individual_review:
    duration: "20 minutes"
    activities:
      - "Each person reviews research data"
      - "Individuals write insights on sticky notes"
      - "Organize notes by empathy map quadrants"
      - "Prepare to share with group"
    
  phase_3_collaborative_mapping:
    duration: "60 minutes"
    activities:
      - "Share individual insights"
      - "Cluster similar insights together"
      - "Discuss differences and reconcile"
      - "Build consensus empathy map"
    
  phase_4_validation:
    duration: "30 minutes"
    activities:
      - "Review completed empathy map"
      - "Identify gaps or assumptions"
      - "Validate against original research"
      - "Note areas needing more research"
    
  phase_5_actionable_insights:
    duration: "45 minutes"
    activities:
      - "Extract key insights and patterns"
      - "Define implications for project"
      - "Create prioritized insight list"
      - "Plan next steps and research needs"
```

#### Facilitation Guidelines

**Materials Needed:**
```
Workshop Materials Checklist:
├── [ ] Large wall space or multiple whiteboards
├── [ ] Sticky notes (4 different colors for quadrants)
├── [ ] Markers (thick tip for visibility)
├── [ ] Dot stickers for voting/prioritization
├── [ ] Timer for keeping activities on track
├── [ ] Research summary handouts
├── [ ] Empathy map template (large format)
├── [ ] Camera for documenting results
└── [ ] Laptop for digital capture
```

**Facilitation Techniques:**
```yaml
facilitation_best_practices:
  encourage_participation:
    - "Use round-robin sharing to include all voices"
    - "Set time limits for individual contributions"
    - "Use 'silent sorting' before discussion"
    - "Ask quiet participants directly for input"
    
  manage_disagreements:
    - "Focus on evidence from research data"
    - "Capture different perspectives rather than forcing consensus"
    - "Use 'both/and' thinking instead of 'either/or'"
    - "Mark areas of uncertainty for follow-up research"
    
  maintain_energy:
    - "Keep activities moving with clear time boundaries"
    - "Use physical movement (posting notes, changing positions)"
    - "Celebrate insights and 'aha' moments"
    - "Take breaks every 45-60 minutes"
    
  capture_insights:
    - "Designate a scribe to document key insights"
    - "Take photos of work in progress"
    - "Record important quotes and discussions"
    - "Create action items as they emerge"
```

---

## Multiple User Empathy Maps

### Comparative Empathy Mapping

#### Multi-User Template
```
Comparative Empathy Map Analysis

User Group 1: [Primary Users]     User Group 2: [Secondary Users]

THINKS:                           THINKS:
• [Thought 1]                     • [Thought 1]
• [Thought 2]                     • [Thought 2]
• [Thought 3]                     • [Thought 3]

FEELS:                            FEELS:
• [Emotion 1]                     • [Emotion 1]
• [Emotion 2]                     • [Emotion 2]
• [Emotion 3]                     • [Emotion 3]

SAYS:                             SAYS:
• "[Quote 1]"                     • "[Quote 1]"
• "[Quote 2]"                     • "[Quote 2]"
• "[Quote 3]"                     • "[Quote 3]"

DOES:                             DOES:
• [Action 1]                      • [Action 1]
• [Action 2]                      • [Action 2]
• [Action 3]                      • [Action 3]

PAIN POINTS:                      PAIN POINTS:
• [Pain 1]                        • [Pain 1]
• [Pain 2]                        • [Pain 2]

GAINS:                            GAINS:
• [Gain 1]                        • [Gain 1]
• [Gain 2]                        • [Gain 2]

COMPARISON INSIGHTS:
Similarities:
├── [Shared insight 1]
├── [Shared insight 2]
└── [Shared insight 3]

Key Differences:
├── [Difference 1 and implications]
├── [Difference 2 and implications]
└── [Difference 3 and implications]

Design Implications:
├── [Implication 1]
├── [Implication 2]
└── [Implication 3]
```

### Journey-Based Empathy Mapping

#### Temporal Empathy Map Template
```yaml
journey_empathy_mapping:
  stage_1_awareness:
    thinks: ["What thoughts occur when first encountering problem/solution?"]
    feels: ["What emotions arise during discovery?"]
    says: ["What do they tell others about initial experience?"]
    does: ["What actions do they take to learn more?"]
    
  stage_2_consideration:
    thinks: ["What concerns and questions come up?"]
    feels: ["What emotions arise during evaluation?"]
    says: ["What do they ask or tell others?"]
    does: ["What comparison or research actions do they take?"]
    
  stage_3_trial:
    thinks: ["What expectations and assumptions do they have?"]
    feels: ["What emotions arise during first use?"]
    says: ["What feedback do they give during trial?"]
    does: ["How do they actually use the solution?"]
    
  stage_4_adoption:
    thinks: ["What beliefs form about ongoing value?"]
    feels: ["What emotions characterize regular use?"]
    says: ["What do they tell others about their experience?"]
    does: ["How do usage patterns evolve over time?"]
```

---

## Digital Empathy Mapping Tools

### Tool Comparison and Setup

#### Digital Tool Options
```yaml
digital_empathy_mapping_tools:
  miro:
    strengths: ["Excellent collaboration", "Great templates", "Easy sharing"]
    limitations: ["Learning curve", "Cost for teams", "Internet dependent"]
    best_for: "Large distributed teams, complex workshops"
    
  figma:
    strengths: ["Real-time collaboration", "Designer-friendly", "Version control"]
    limitations: ["More complex for non-designers", "Template setup needed"]
    best_for: "Design teams, integrated with other design work"
    
  mural:
    strengths: ["Facilitation features", "Guided activities", "Analytics"]
    limitations: ["Cost", "Can be overwhelming", "Learning curve"]
    best_for: "Professional facilitators, large organizations"
    
  conceptboard:
    strengths: ["Infinite canvas", "Good templates", "Presentation mode"]
    limitations: ["Less popular", "Limited integrations", "Learning curve"]
    best_for: "European teams, privacy-focused organizations"
    
  microsoft_whiteboard:
    strengths: ["Office 365 integration", "Familiar interface", "Voice notes"]
    limitations: ["Limited templates", "Basic functionality", "Platform dependent"]
    best_for: "Microsoft-heavy organizations, simple mapping"
```

#### Miro Template Setup Guide
```yaml
miro_empathy_map_setup:
  template_creation:
    step_1: "Create new board from empathy map template"
    step_2: "Customize quadrant labels and colors"
    step_3: "Add user information section"
    step_4: "Include instructions and legend"
    step_5: "Set up sticky note areas for each quadrant"
    
  collaboration_setup:
    sharing_settings: "Set to 'Can edit' for all participants"
    user_permissions: "Add team members before workshop"
    notification_settings: "Enable comments and mentions"
    
  facilitation_features:
    timer: "Use built-in timer for activities"
    voting: "Enable dot voting for prioritization"
    presentation_mode: "Use for sharing results"
    frames: "Create frames for different user segments"
    
  post_workshop:
    export_options: ["PDF for documentation", "PNG for presentations"]
    sharing: "Create public link for stakeholders"
    version_control: "Save versions before major changes"
```

---

## Insight Extraction and Analysis

### Pattern Recognition Framework

#### Cross-Quadrant Analysis
```yaml
pattern_analysis_framework:
  emotional_journey_mapping:
    positive_emotions: "What triggers positive feelings?"
    negative_emotions: "What causes frustration or anxiety?"
    emotional_transitions: "How do emotions change over time?"
    
  behavior_motivation_alignment:
    stated_vs_actual: "Differences between what they say and do"
    conscious_vs_unconscious: "Aware vs unaware behaviors"
    ideal_vs_real: "Aspirational vs actual behaviors"
    
  influence_network_analysis:
    internal_influences: "What they think and feel internally"
    external_influences: "What they hear from others"
    environmental_influences: "What they see in their context"
    
  pain_gain_correlation:
    pain_point_clustering: "Common themes in frustrations"
    gain_opportunity_mapping: "Desired outcomes and motivations"
    pain_gain_relationships: "How pains relate to desired gains"
```

#### Insight Prioritization Matrix
```
Empathy Map Insights Prioritization

High Impact, High Confidence:
├── [Insight 1: Clear evidence, major user impact]
├── [Insight 2: Strong patterns, significant opportunity]
└── [Insight 3: Multiple sources, addresses core need]

High Impact, Low Confidence:
├── [Insight 4: Important if true, needs validation]
├── [Insight 5: Could be transformative, requires research]
└── [Insight 6: Emerging pattern, worth exploring]

Low Impact, High Confidence:
├── [Insight 7: Clear but minor, good for incremental improvement]
├── [Insight 8: Well-supported but limited scope]
└── [Insight 9: Confirmed but not strategic]

Low Impact, Low Confidence:
├── [Insight 10: Unclear and minor, lowest priority]
├── [Insight 11: Weak evidence and limited impact]
└── [Insight 12: Assumption-based, needs validation]

Action Planning:
├── Immediate Action: Implement high impact, high confidence insights
├── Research Priority: Investigate high impact, low confidence insights
├── Quick Wins: Consider low impact, high confidence improvements
└── Parking Lot: Document low impact, low confidence insights for future
```

---

## Integration with Project Management

### Empathy Maps in PM Workflows

#### Project Phase Integration
```yaml
pm_integration_framework:
  project_initiation:
    empathy_map_role: "Inform project charter and scope definition"
    deliverables: ["User-centered project objectives", "Stakeholder empathy maps"]
    timeline: "Complete during stakeholder analysis phase"
    
  requirements_gathering:
    empathy_map_role: "Guide requirement prioritization and definition"
    deliverables: ["User-informed requirements", "Empathy-based acceptance criteria"]
    timeline: "Use to validate and refine requirements"
    
  solution_design:
    empathy_map_role: "Ensure solutions address real user needs"
    deliverables: ["User-centered design decisions", "Empathy-informed features"]
    timeline: "Reference throughout design phase"
    
  testing_validation:
    empathy_map_role: "Create realistic test scenarios and success criteria"
    deliverables: ["Empathy-based test cases", "User-centered success metrics"]
    timeline: "Inform test planning and execution"
```

#### Agile Integration Points
```yaml
agile_empathy_integration:
  user_story_development:
    empathy_input: "Use insights to write more authentic user stories"
    template_enhancement: "As a [user who thinks/feels X], I want [capability] so that [empathy-based benefit]"
    acceptance_criteria: "Include emotional and experiential success criteria"
    
  sprint_planning:
    empathy_review: "Review relevant empathy maps before sprint planning"
    story_prioritization: "Prioritize stories that address key pain points"
    definition_of_done: "Include user empathy validation criteria"
    
  sprint_review:
    empathy_validation: "Test delivered features against empathy map insights"
    user_feedback: "Collect feedback that updates empathy understanding"
    retrospective_input: "How well did we address user empathy insights?"
    
  product_backlog:
    empathy_driven_features: "Generate feature ideas from empathy map gaps"
    story_refinement: "Use empathy insights to add depth to stories"
    epic_development: "Create epics that address comprehensive user journeys"
```

### Stakeholder Empathy Mapping

#### Stakeholder-Specific Templates
```
Stakeholder Empathy Map: [Stakeholder Role]

Project Context: [Specific project and phase]
Stakeholder Influence: [High/Medium/Low]
Stakeholder Interest: [High/Medium/Low]

THINKS:                           FEELS:
Professional concerns:            Professional emotions:
• [Business worry 1]              • [Emotion about project risk]
• [Strategic consideration 2]     • [Feeling about resource allocation]
• [Market assumption 3]           • [Attitude toward change]

Personal concerns:                Personal emotions:
• [Career implication 1]          • [Personal stake in success]
• [Workload impact 2]            • [Confidence in team]
• [Relationship effect 3]         • [Stress about timeline]

SAYS:                            DOES:
In meetings:                     Observable actions:
• "[Quote about priorities]"      • [Meeting behavior 1]
• "[Statement about concerns]"    • [Decision pattern 2]
• "[Position on approach]"        • [Communication style 3]

Privately:                       Behind scenes:
• "[Informal feedback]"           • [Information seeking behavior]
• "[Concern shared confidentially]" • [Influence activity]
• "[Personal opinion]"            • [Resource allocation decisions]

PAIN POINTS:                     GAINS:
Project risks:                   Success outcomes:
• [Risk to business goals]        • [Desired business result]
• [Resource constraints]          • [Personal success measure]
• [Timeline pressures]            • [Organizational benefit]

Personal impacts:                Personal benefits:
• [Workload increase]            • [Career advancement]
• [Responsibility burden]         • [Recognition opportunity]
• [Change management stress]      • [Skill development]

INFLUENCE FACTORS:               COMMUNICATION PREFERENCES:
Who influences them:             How they prefer updates:
• [Peer influence 1]             • [Frequency preference]
• [Authority figure 2]           • [Format preference]
• [Market force 3]               • [Detail level preference]
```

---

## Validation and Updates

### Empathy Map Validation Framework

#### Validation Methods
```yaml
empathy_map_validation:
  primary_validation:
    method: "Return to original research participants"
    process: "Show empathy map and ask for feedback"
    questions: 
      - "How accurately does this represent your experience?"
      - "What's missing or incorrect?"
      - "What resonates most strongly?"
      - "What would you change or add?"
    
  secondary_validation:
    method: "Test with new participants from same user group"
    process: "Use empathy map to predict responses, then validate"
    questions:
      - "Do new participants exhibit predicted thoughts/feelings?"
      - "Are behaviors consistent with mapped actions?"
      - "Do pain points and gains align?"
    
  triangulation_validation:
    method: "Compare against other data sources"
    sources: ["Analytics data", "Support tickets", "Sales feedback", "Market research"]
    analysis: "Look for confirmation or contradiction of empathy map insights"
    
  stakeholder_validation:
    method: "Review with internal stakeholders who interact with users"
    participants: ["Customer service", "Sales team", "Account managers", "Support staff"]
    focus: "Validate against their direct user interaction experience"
```

#### Update Triggers and Process
```yaml
empathy_map_updates:
  update_triggers:
    scheduled_reviews: "Every 6 months or major product release"
    significant_changes: "Major feature launches, market shifts, user feedback"
    research_findings: "New user research that contradicts current map"
    performance_data: "Analytics that suggest different user behaviors"
    
  update_process:
    step_1: "Review trigger event and new data"
    step_2: "Identify specific map elements that need updating"
    step_3: "Gather team to review proposed changes"
    step_4: "Update map with new insights"
    step_5: "Validate changes with users if possible"
    step_6: "Communicate updates to project team"
    step_7: "Update related project artifacts"
    
  version_control:
    naming_convention: "[User Group]_EmpathyMap_v[X.X]_[Date]"
    change_log: "Document what changed and why"
    archive_old_versions: "Keep for historical reference"
    stakeholder_notification: "Alert relevant team members to changes"
```

---

## Advanced Empathy Mapping Techniques

### Behavioral Persona Integration

#### Empathy Map + Persona Hybrid
```yaml
empathy_persona_integration:
  demographic_context:
    basic_info: "Age, role, experience level, context"
    background: "Education, career path, personal situation"
    technology_comfort: "Digital literacy and tool preferences"
    
  behavioral_patterns:
    decision_making_style: "How they evaluate options and make choices"
    information_processing: "How they consume and synthesize information"
    social_influences: "Who and what influences their decisions"
    risk_tolerance: "Comfort with change and new approaches"
    
  contextual_factors:
    work_environment: "Physical and cultural work setting"
    time_constraints: "When and how long they have for tasks"
    resource_availability: "What tools, support, and budget they have"
    performance_pressures: "What they're measured on and accountable for"
    
  empathy_integration:
    persona_informed_empathy: "Use persona details to deepen empathy insights"
    empathy_informed_persona: "Use empathy insights to make persona more realistic"
    validation_alignment: "Ensure both persona and empathy map are consistent"
```

### Cultural and Contextual Empathy Mapping

#### Cross-Cultural Empathy Considerations
```yaml
cultural_empathy_framework:
  cultural_dimensions:
    communication_style: "Direct vs indirect, high vs low context"
    hierarchy_orientation: "Power distance and authority relationships"
    individualism_collectivism: "Individual vs group decision making"
    uncertainty_avoidance: "Comfort with ambiguity and risk"
    
  contextual_variations:
    geographical_differences: "Regional variations in same culture"
    generational_factors: "Age-related differences in attitudes and behaviors"
    industry_culture: "Sector-specific norms and expectations"
    organizational_culture: "Company-specific values and practices"
    
  adaptation_strategies:
    local_research: "Include local team members in research and mapping"
    cultural_validation: "Validate insights with cultural experts"
    contextual_testing: "Test solutions in specific cultural contexts"
    iterative_refinement: "Continuously update based on cultural learning"
```

---

## Success Metrics and ROI

### Empathy Mapping Impact Measurement

#### Short-term Metrics (1-3 months)
```yaml
short_term_impact_metrics:
  team_alignment:
    metric: "Stakeholder alignment on user needs"
    measurement: "Survey scores before/after empathy mapping"
    target: "20% improvement in alignment scores"
    
  decision_quality:
    metric: "User-centered decision making frequency"
    measurement: "Count of decisions explicitly referencing user insights"
    target: "80% of feature decisions include empathy map references"
    
  research_efficiency:
    metric: "Time to synthesize user research"
    measurement: "Hours required to extract actionable insights"
    target: "30% reduction in research synthesis time"
    
  insight_generation:
    metric: "Number of actionable user insights identified"
    measurement: "Count of insights leading to specific actions"
    target: "5-10 actionable insights per empathy mapping session"
```

#### Long-term Metrics (3-12 months)
```yaml
long_term_impact_metrics:
  user_satisfaction:
    metric: "User satisfaction with delivered solutions"
    measurement: "User satisfaction surveys and NPS scores"
    target: "15% improvement in user satisfaction"
    
  feature_adoption:
    metric: "Adoption rate of empathy-informed features"
    measurement: "Usage analytics for features based on empathy insights"
    target: "25% higher adoption than features without empathy input"
    
  development_efficiency:
    metric: "Reduction in feature rework and iterations"
    measurement: "Number of major feature changes post-launch"
    target: "40% reduction in post-launch feature modifications"
    
  business_impact:
    metric: "Business metrics improvement"
    measurement: "Revenue, retention, conversion rates"
    target: "10% improvement in key business metrics"
```

---

## Related Templates and Integration Points

### Template Ecosystem Connections
- [Design Thinking Workshop Template](./design_thinking_workshop_template.md) - Complete workshop framework
- [Innovation Project Template](../../../organizational-frameworks/innovation-management/innovation_project_template.md) - Innovation project management
- [User Story Template](../../../domains/uncertainty/role-based-toolkits/product-owner/user-story-template.md) - Agile user story integration
- [Stakeholder Register Template](../../../domains/stakeholder/project-lifecycle/01-initiation/stakeholder-analysis/stakeholder-register-template.md) - Stakeholder management
- [Design Thinking Walkthrough Example](../../../examples/design-thinking/design-thinking-walkthrough.md) - Worked end-to-end example

---

## Version History
| Version | Date | Changes | Author |
|---------|------|---------|--------|
| 1.0 | [Date] | Initial User Empathy Mapping template | [Author] |

---

*This template is part of the PM Tools Templates library. For more information and additional templates, visit [repository root](../../../README.md).*