Design Thinking Workshop Template

---
title: "Design Thinking Workshop Template"
methodology: "universal"
complexity: "advanced"
owner: "mirichard"
updated: "2026-10-08"
domain: "Delivery"
primary_principles: ["stakeholder-engagement", "collaborative-leadership"]
secondary_principles: ["adaptability", "value-focus"]
principle_rationale: "Facilitates collaborative problem framing with users and teams so workshop outputs drive adaptable value-focused delivery decisions."
tags: ["design-thinking", "workshop", "innovation", "human-centered-design"]
---

# Design Thinking Workshop Template

## Overview
This template provides a comprehensive framework for conducting design thinking workshops that integrate with project management practices. It combines human-centered design principles with structured project execution to drive innovation and solve complex problems.



## When to Use
- Run a cross-functional framing workshop when a problem is ambiguous and teams need a shared problem statement before committing delivery scope.
- Use this format when you need structured facilitation from empathy through prototype testing within a defined project window.
- Apply it when stakeholder alignment is weak and you need observable workshop outputs (insights, concepts, and next experiments).

## When NOT to Use
- Do not use as a substitute for delivery governance after execution has already started and committed controls are in place.
- Do not treat workshop artifacts as implementation evidence without contextual tailoring and accountable follow-through (see [Template as substitute for judgment](../../../docs/principles/anti-patterns.md#template-judgment)).
- Do not run this as a single-team exercise when the decision depends on customers, operations, and compliance inputs.

## Pairs Well With
- [User Empathy Mapping Template](user_empathy_mapping_template.md)
- [Experiment Design Template](../lean-startup/experiment-design-template.md)

Decision context model reference: 800-801-context-assessment-model.md
## Template Information
- **Methodology:** Design Thinking Integration
- **Purpose:** Facilitate human-centered problem solving and innovation
- **Audience:** Product Managers, UX Designers, Project Managers, Innovation Teams
- **Duration:** 2-5 days (depending on scope)
- **Prerequisites:** Problem statement defined, stakeholders identified

---

## Design Thinking Process Framework

### Five-Stage Design Thinking Process

#### Stage 1: Empathize 🤝
**Objective:** Understand the user and their needs
**Duration:** 1-2 days
**Key Activities:**
- User interviews
- Observational studies
- Stakeholder mapping
- Empathy mapping

#### Stage 2: Define 🎯
**Objective:** Frame the problem and define design challenge
**Duration:** 0.5-1 day
**Key Activities:**
- Problem statement creation
- Point of view development
- How might we questions
- Success criteria definition

#### Stage 3: Ideate 💡
**Objective:** Generate creative solutions
**Duration:** 1-2 days
**Key Activities:**
- Brainstorming sessions
- Mind mapping
- Worst possible idea
- Brainwriting

#### Stage 4: Prototype 🔧
**Objective:** Build to think and test ideas
**Duration:** 1-2 days
**Key Activities:**
- Rapid prototyping
- Storyboarding
- Role playing
- Digital mockups

#### Stage 5: Test 🧪
**Objective:** Validate solutions with users
**Duration:** 1-2 days
**Key Activities:**
- User testing
- Feedback collection
- Iteration planning
- Next steps definition

---

## Pre-Workshop Planning

### Workshop Planning Checklist

#### 6 Weeks Before Workshop:
```
Strategic Planning:
├── [ ] Define workshop objectives and success criteria
├── [ ] Identify key stakeholders and participants
├── [ ] Secure executive sponsorship and budget
├── [ ] Book venue and schedule facilitators
├── [ ] Create communication plan for participants
└── [ ] Define scope and constraints

Problem Definition:
├── [ ] Conduct stakeholder interviews
├── [ ] Review existing research and data
├── [ ] Define initial problem statement
├── [ ] Identify target user groups
├── [ ] Set measurable outcomes
└── [ ] Create context document for participants
```

#### 4 Weeks Before Workshop:
```
Participant Preparation:
├── [ ] Send save-the-dates and workshop overview
├── [ ] Distribute pre-work materials
├── [ ] Collect participant information and roles
├── [ ] Share relevant background materials
├── [ ] Confirm dietary requirements and accessibility needs
└── [ ] Set expectations for workshop outcomes

Research Preparation:
├── [ ] Gather existing user research
├── [ ] Prepare personas (if available)
├── [ ] Collect competitive analysis
├── [ ] Review market research and trends
├── [ ] Prepare industry insights
└── [ ] Create research synthesis
```

#### 2 Weeks Before Workshop:
```
Logistics and Materials:
├── [ ] Confirm venue setup and technology
├── [ ] Order workshop supplies (sticky notes, markers, etc.)
├── [ ] Prepare workshop templates and canvases
├── [ ] Set up collaboration tools (Miro, Figma, etc.)
├── [ ] Create participant welcome packet
├── [ ] Plan catering and break schedule
├── [ ] Prepare name tags and seating arrangement
└── [ ] Test all technology and backup plans

Final Preparations:
├── [ ] Send final agenda and logistics to participants
├── [ ] Confirm facilitator preparation and materials
├── [ ] Prepare opening presentation
├── [ ] Review and practice workshop facilitation
├── [ ] Prepare backup activities for each stage
└── [ ] Create documentation plan for workshop outputs
```

### Participant Selection Matrix

| Role | Why Include | Ideal Number | Key Contribution |
|------|-------------|--------------|------------------|
| Product Manager | Product vision and strategy | 1-2 | Business requirements, feasibility |
| UX/UI Designer | Design expertise | 2-3 | User experience, visual design |
| Developer/Engineer | Technical feasibility | 1-2 | Implementation insights, constraints |
| Business Stakeholder | Business requirements | 1-2 | Strategic alignment, resource approval |
| Customer/User Representative | User perspective | 2-3 | Real user needs, validation |
| Project Manager | Process facilitation | 1 | Timeline, resource management |
| Subject Matter Expert | Domain knowledge | 1-2 | Industry insights, compliance |

**Optimal Workshop Size:** 8-12 participants

---

## Stage 1: Empathize Templates

### User Interview Guide

#### Pre-Interview Preparation
```yaml
Interview Planning:
  objective: "Understand user needs, pain points, and motivations"
  duration: "45-60 minutes"
  format: "Semi-structured interview"
  tools: ["Recording device", "Interview guide", "Note-taking template"]
  
participant_criteria:
  primary_users: "Direct users of the product/service"
  secondary_users: "Indirect users or influencers"
  edge_cases: "Power users or users with unique needs"
  diversity: "Varied demographics, experience levels, use cases"
```

#### Interview Script Template
```
Opening (5 minutes):
├── Introduce yourself and the purpose of the interview
├── Explain how the information will be used
├── Ask for permission to record
├── Set expectations for duration and format
└── Begin with warmup questions

Background Questions (10 minutes):
├── Can you tell me about your role and responsibilities?
├── How long have you been in this position/using this type of solution?
├── What does a typical day/week look like for you?
├── What are your main goals and objectives?
└── What tools or systems do you currently use?

Current State Exploration (20 minutes):
├── Walk me through how you currently [perform specific task]
├── What works well in your current process?
├── What are the biggest challenges or frustrations you face?
├── Can you describe a recent time when things didn't go as planned?
├── What workarounds have you developed?
├── How do you measure success in this area?
└── What would make your life significantly easier?

Future State Vision (15 minutes):
├── If you could wave a magic wand, how would you solve this problem?
├── What would the ideal solution look like to you?
├── How would you know if a solution was working well?
├── What concerns would you have about changing the current approach?
├── Who else would be impacted by changes to this process?
└── What questions haven't I asked that I should have?

Closing (5 minutes):
├── Is there anything else you'd like to share?
├── Can I follow up if I have additional questions?
├── Would you be interested in seeing the results of this research?
└── Thank participant for their time and insights
```

### Empathy Map Template

#### Individual Empathy Map
```
User Empathy Map for: [User Name/Persona]

SAYS (Direct quotes)          |  THINKS (Thoughts, beliefs)
├── "I wish it was easier"    |  ├── Worried about efficiency
├── "This never works"        |  ├── Believes current system is broken
├── "I don't have time"       |  ├── Thinks there should be a better way
└── "It's too complicated"    |  └── Suspects others have same problems

DOES (Observable actions)     |  FEELS (Emotions, feelings)
├── Uses workarounds          |  ├── Frustrated with delays
├── Asks colleagues for help  |  ├── Anxious about deadlines
├── Avoids certain features   |  ├── Confident in their expertise
└── Creates personal systems  |  └── Hopeful for improvement

PAIN POINTS                   |  GAINS/MOTIVATIONS
├── Time-consuming processes  |  ├── Completing tasks efficiently
├── Lack of integration       |  ├── Recognition for good work
├── Unclear instructions      |  ├── Learning new skills
├── System unreliability      |  ├── Helping team succeed
└── Information silos         |  └── Making impact on organization
```

### Stakeholder Map Template

#### Stakeholder Influence-Interest Matrix
```yaml
stakeholder_mapping:
  high_influence_high_interest:
    - name: "Product Owner"
      role: "Decision maker"
      needs: ["Clear ROI", "Reduced risk", "Fast delivery"]
      communication: "Weekly updates, key decisions"
      
    - name: "End Users"
      role: "Primary beneficiary"
      needs: ["Ease of use", "Reliability", "Training"]
      communication: "User testing, feedback sessions"
      
  high_influence_low_interest:
    - name: "CEO/Executive Sponsor"
      role: "Strategic oversight"
      needs: ["Business impact", "Resource justification"]
      communication: "Monthly summaries, major milestones"
      
  low_influence_high_interest:
    - name: "Customer Support Team"
      role: "User advocate"
      needs: ["Reduced support burden", "Clear documentation"]
      communication: "Regular check-ins, training sessions"
      
  low_influence_low_interest:
    - name: "Compliance Team"
      role: "Regulatory oversight"
      needs: ["Compliance adherence", "Documentation"]
      communication: "As needed, formal reviews"
```

---

## Stage 2: Define Templates

### Problem Statement Canvas

#### Problem Definition Framework
```
Problem Statement Canvas

Current State:
├── What is happening now?
├── Who is affected?
├── What are the symptoms?
├── What evidence do we have?
└── What are the business impacts?

Root Cause Analysis:
├── Why is this happening? (5 Whys)
├── What are the contributing factors?
├── What systems or processes are involved?
├── What constraints exist?
└── What assumptions are we making?

Desired Future State:
├── What would success look like?
├── How would we measure improvement?
├── What capabilities would we need?
├── What would be different for users?
└── What business outcomes would we achieve?

Problem Statement:
"We have observed that [user group] 
is experiencing [problem/need] 
when trying to [accomplish goal/task], 
which is causing [negative impact].

A successful solution would allow [user group] 
to [achieve desired outcome] 
so that [business benefit]."

Success Criteria:
├── [ ] User satisfaction score > 4.5/5
├── [ ] Task completion time reduced by 30%
├── [ ] Error rate decreased by 50%
├── [ ] User adoption rate > 80% within 3 months
└── [ ] Business metric improvement [specific target]
```

### Point of View (POV) Statement Template

#### POV Development Worksheet
```yaml
point_of_view_development:
  user_persona:
    name: "[Primary User]"
    role: "[Job title/role]"
    context: "[Relevant background]"
    
  user_need:
    functional_need: "What they need to accomplish"
    emotional_need: "How they want to feel"
    social_need: "How they want to be perceived"
    
  insight:
    key_insight: "Surprising or meaningful discovery about the user"
    supporting_evidence: ["Interview quote", "Observed behavior", "Data point"]
    
  pov_statement:
    template: "[User] needs [need] because [insight]"
    example: "Busy project managers need a single dashboard to track project status because they spend too much time switching between tools and lose critical information in the process"
```

### How Might We (HMW) Question Generator

#### HMW Framework
```
How Might We Question Development

Based on POV: "[Your POV statement]"

Question Starters:
├── How might we make [process] more [adjective]?
├── How might we help [user] feel more [emotion]?
├── How might we remove barriers to [goal]?
├── How might we reimagine [current approach]?
├── How might we combine [X] and [Y] to create [Z]?
├── How might we use [technology/method] to improve [outcome]?
└── How might we prevent [problem] from occurring?

Generated HMW Questions:
1. How might we ________________________________?
2. How might we ________________________________?
3. How might we ________________________________?
4. How might we ________________________________?
5. How might we ________________________________?

Question Evaluation Criteria:
├── [ ] Is it broad enough to allow for creative solutions?
├── [ ] Is it specific enough to provide direction?
├── [ ] Does it assume a solution?
├── [ ] Does it inspire action?
└── [ ] Is it grounded in user needs?

Selected Focus Question:
"How might we ________________________________?"

Rationale for Selection:
_________________________________________________
_________________________________________________
```

---

## Stage 3: Ideate Templates

### Brainstorming Session Framework

#### Classic Brainstorming Setup
```yaml
brainstorming_session:
  preparation:
    duration: "45-60 minutes"
    participants: "5-8 people maximum"
    materials: ["Sticky notes", "Markers", "Timer", "Large wall space"]
    mindset: "Yes, and..." thinking
    
  rules:
    - "Defer judgment - no criticism"
    - "Strive for quantity over quality"
    - "Build on ideas of others"
    - "Stay focused on topic"
    - "Encourage wild ideas"
    - "Be visual when possible"
    
  process:
    warm_up: "5 minutes - practice round with fun topic"
    focus_question: "Present the HMW question clearly"
    individual_ideation: "5 minutes silent brainstorming"
    sharing_round_1: "10 minutes - share and post ideas"
    building_ideas: "15 minutes - build on posted ideas"
    new_directions: "10 minutes - completely new approaches"
    final_additions: "5 minutes - last ideas"
    
  facilitation_tips:
    - "Keep energy high"
    - "Encourage participation from everyone"
    - "Redirect if going off-topic"
    - "Celebrate unusual ideas"
    - "Capture everything visibly"
```

### Idea Clustering and Selection Matrix

#### Idea Organization Template
```
Idea Clustering Worksheet

Step 1: Idea Grouping
├── Group similar ideas together
├── Label each cluster with a theme
├── Identify any standalone ideas
└── Count ideas in each cluster

Cluster Categories:
1. [Cluster Name]: _____ ideas
   - Key concept: ________________
   - Representative ideas: ________
   
2. [Cluster Name]: _____ ideas
   - Key concept: ________________
   - Representative ideas: ________
   
3. [Cluster Name]: _____ ideas
   - Key concept: ________________
   - Representative ideas: ________

Step 2: Idea Evaluation Matrix

Evaluation Criteria (Weight 1-5):
├── User Impact: How much will this help users? (Weight: ___)
├── Feasibility: How realistic is implementation? (Weight: ___)
├── Innovation: How novel/creative is this approach? (Weight: ___)
├── Strategic Fit: How well does it align with business goals? (Weight: ___)
└── Resource Requirements: How much effort is needed? (Weight: ___)

Scoring Matrix (1-5 scale):
| Idea | User Impact | Feasibility | Innovation | Strategic Fit | Resources | Total Score |
|------|-------------|-------------|------------|---------------|-----------|-------------|
| A    |      4      |      3      |     5      |       4       |     2     |     18      |
| B    |      5      |      2      |     3      |       5       |     3     |     18      |
| C    |      3      |      5      |     2      |       3       |     4     |     17      |

Step 3: Selection Criteria
├── Top 3 highest scoring ideas
├── Mix of quick wins and breakthrough ideas
├── Diverse approaches to the problem
└── Ideas that can be prototyped quickly
```

### Alternative Ideation Methods

#### Method 1: Brainwriting 6-3-5
```
Brainwriting 6-3-5 Template

Setup:
├── 6 participants
├── Each person gets a worksheet
├── 3 ideas per round
├── 5 minutes per round
└── Pass worksheet to next person

Worksheet Template:
Round 1 (5 min) - Your ideas:
1. ________________________________
2. ________________________________
3. ________________________________

Round 2 (5 min) - Build on previous ideas:
1. ________________________________
2. ________________________________
3. ________________________________

[Continue for 6 rounds total]

Benefits:
├── Equal participation from all team members
├── Builds on ideas systematically
├── Reduces groupthink
└── Generates 108 ideas in 30 minutes
```

#### Method 2: Worst Possible Idea
```
Worst Possible Idea Exercise

Purpose: Break mental barriers and inspire creative thinking

Instructions:
1. "How might we create the worst possible solution to our problem?"
2. Spend 10 minutes generating terrible ideas
3. For each bad idea, ask "What would the opposite look like?"
4. Transform opposite ideas into viable solutions

Example:
Bad Idea: "Make the process take 10 times longer"
Opposite: "Make the process much faster"
Good Idea: "Automate routine steps to save time"

Worksheet:
| Worst Idea | Opposite | Potential Good Idea |
|------------|----------|-------------------|
|            |          |                   |
|            |          |                   |
|            |          |                   |
```

---

## Stage 4: Prototype Templates

### Rapid Prototyping Framework

#### Prototype Planning Canvas
```yaml
prototype_planning:
  objective:
    what_to_test: "Core assumption about the solution"
    target_users: "Who will interact with the prototype"
    key_questions: ["What do we want to learn?", "What might go wrong?"]
    
  prototype_type:
    fidelity_level: "Low/Medium/High"
    format: "Paper, Digital, Physical, Service"
    complexity: "Simple concept vs detailed interaction"
    
  resources_needed:
    time_allocation: "2-4 hours maximum"
    materials: ["Paper", "Sticky notes", "Digital tools"]
    skills_required: ["Sketching", "Digital design", "Facilitation"]
    team_members: "2-3 people maximum"
    
  success_criteria:
    learning_goals: "What insights do we want to gain?"
    user_feedback: "What responses indicate success?"
    iteration_plan: "How will we improve based on feedback?"
```

### Prototyping Method Selection Guide

#### Low-Fidelity Prototypes

**Paper Prototypes:**
```
When to Use:
├── Testing basic user flows
├── Exploring layout concepts
├── Limited time/resources
└── Early concept validation

Materials Needed:
├── Large sheets of paper (A3/A2)
├── Sticky notes for interactive elements
├── Markers and pens
├── Scissors and tape
└── Mobile/tablet frames (printed)

Process:
1. Sketch main screens or process steps
2. Use sticky notes for buttons and interactive elements
3. Create simple navigation flow
4. Test with users by "playing computer"
5. Document feedback and observations

Benefits:
├── Very fast to create (30-60 minutes)
├── Easy to modify during testing
├── Forces focus on core functionality
├── Low emotional attachment to design
└── Accessible to non-designers
```

**Storyboarding:**
```
Storyboard Template

Scene 1: Current State Problem
├── Setting: Where does the problem occur?
├── Character: Who experiences the problem?
├── Problem: What goes wrong?
├── Emotion: How does the character feel?
└── Thought bubble: What are they thinking?

Scene 2: Discovery of Solution
├── Trigger: What leads them to the solution?
├── First interaction: How do they encounter it?
├── Initial reaction: What's their first impression?
├── Action: What do they do?
└── Expectation: What do they hope will happen?

Scene 3: Using the Solution
├── Context: When/where do they use it?
├── Process: Step-by-step interaction
├── Support: What help is available?
├── Progress: How do they know it's working?
└── Outcome: What result do they achieve?

Scene 4: Success State
├── Accomplishment: What did they achieve?
├── Feeling: How do they feel now?
├── Sharing: Who do they tell about it?
├── Repeat: Will they use it again?
└── Recommendation: Would they recommend it?

Visual Elements:
├── Simple stick figures or basic illustrations
├── Speech bubbles for dialogue
├── Thought bubbles for internal thoughts
├── Arrows to show movement/progression
└── Emotional indicators (smiles, frowns, etc.)
```

#### Medium-Fidelity Prototypes

**Digital Wireframes:**
```yaml
digital_wireframe_template:
  tools:
    recommended: ["Figma", "Sketch", "Adobe XD", "Balsamiq"]
    free_options: ["Figma (free tier)", "Marvel", "InVision", "Draw.io"]
    
  components_to_include:
    navigation: "Primary and secondary navigation elements"
    content_areas: "Where key information will be displayed"
    interactive_elements: "Buttons, forms, links"
    feedback_indicators: "Loading states, error messages, success confirmations"
    
  fidelity_guidelines:
    layout: "Accurate positioning and sizing"
    content: "Realistic text length and image placeholders"
    functionality: "Key interactions should be clickable"
    styling: "Grayscale with minimal visual design"
    
  testing_approach:
    task_scenarios: "Specific goals for users to accomplish"
    think_aloud_protocol: "Ask users to verbalize their thoughts"
    observation_focus: "Where do users hesitate or get confused?"
    feedback_collection: "What do users expect to happen vs what happens?"
```

### Service Design Blueprinting

#### Service Blueprint Template
```
Service Blueprint for: [Service Name]

Customer Journey (Front Stage):
├── Awareness: How do customers discover the service?
├── Consideration: What factors influence their decision?
├── Onboarding: How do they get started?
├── Usage: What's their ongoing experience?
├── Support: When and how do they get help?
└── Advocacy: How do they share or recommend?

Line of Interaction
------------------------

Front Stage Actions (Visible to Customer):
├── Marketing materials and communications
├── Website or app interface
├── Customer service interactions
├── Physical touchpoints
├── Delivery or fulfillment
└── Follow-up communications

Line of Visibility
------------------------

Back Stage Actions (Invisible to Customer):
├── Content creation and management
├── Order processing and fulfillment
├── Quality assurance and testing
├── Data analysis and reporting
├── Staff training and development
└── Technology maintenance

Line of Internal Interaction
------------------------

Support Processes:
├── Technology infrastructure
├── Policies and procedures
├── Training and knowledge management
├── Vendor and partner management
├── Financial and legal compliance
└── Strategic planning and governance

Key Insights:
├── Pain points in customer journey
├── Moments of truth or critical interactions
├── Opportunities for improvement
├── Resource requirements and constraints
└── Success metrics and measurement points
```

---

## Stage 5: Test Templates

### User Testing Protocol

#### Testing Session Structure
```yaml
user_testing_session:
  pre_session_setup:
    duration: "60-90 minutes per participant"
    environment: "Comfortable, distraction-free space"
    technology: "Recording device, prototype, observation sheets"
    team_roles: ["Facilitator", "Note-taker", "Observer"]
    
  session_agenda:
    introduction: "5 minutes"
    background_questions: "10 minutes"
    prototype_testing: "40-60 minutes"
    post_test_discussion: "15 minutes"
    wrap_up: "5 minutes"
    
  testing_protocol:
    task_scenarios: "3-5 realistic scenarios"
    think_aloud_method: "Encourage continuous verbalization"
    minimal_intervention: "Only help when completely stuck"
    observation_focus: "Actions, emotions, comments, confusion points"
```

#### Task Scenario Template
```
Task Scenario [Number]: [Scenario Name]

Context Setting:
"Imagine you are [role/situation]. You need to [accomplish goal] because [motivation]. You have [time constraint/other constraints]."

Specific Task:
"Using this [prototype/system], please [specific action steps]."

Success Criteria:
├── [ ] User completes primary objective
├── [ ] User follows expected path (or finds acceptable alternative)
├── [ ] User expresses satisfaction with experience
├── [ ] User can explain what they accomplished
└── [ ] User would use this solution in real situation

Observation Points:
├── Where does the user start?
├── What do they try first?
├── Where do they hesitate or get confused?
├── What do they say while using it?
├── How do they recover from errors?
├── What do they expect vs what happens?
└── How do they react emotionally?

Follow-up Questions:
├── How did that experience compare to what you expected?
├── What was most confusing or frustrating?
├── What worked really well?
├── What would you change if you could?
├── How does this compare to your current approach?
└── Would you recommend this to others in your situation?
```

### Feedback Collection Framework

#### Structured Feedback Template
```
User Testing Feedback Summary

Participant Profile:
├── Role: ________________
├── Experience Level: ________________
├── Current Solutions Used: ________________
└── Testing Environment: ________________

Task Performance:
| Task | Completed? | Time | Errors | Help Needed | Satisfaction (1-5) |
|------|------------|------|--------|-------------|-------------------|
| 1    |            |      |        |             |                   |
| 2    |            |      |        |             |                   |
| 3    |            |      |        |             |                   |

Qualitative Feedback:
What Worked Well:
├── [Quote or observation]
├── [Quote or observation]
└── [Quote or observation]

Pain Points:
├── [Specific issue and impact]
├── [Specific issue and impact]
└── [Specific issue and impact]

Suggestions:
├── [User suggestion and context]
├── [User suggestion and context]
└── [User suggestion and context]

Emotional Response:
├── Initial Reaction: ________________
├── During Use: ________________
├── Final Impression: ________________
└── Likelihood to Recommend (1-10): ______

Key Insights:
├── [Insight about user behavior]
├── [Insight about solution effectiveness]
└── [Insight about market opportunity]
```

### Iteration Planning Template

#### Test Results Analysis Framework
```yaml
test_results_analysis:
  quantitative_results:
    task_completion_rates: "Percentage who completed each task"
    time_on_task: "Average time for each task"
    error_rates: "Number and types of errors"
    user_satisfaction_scores: "Average ratings"
    
  qualitative_insights:
    user_mental_models: "How users think about the problem"
    expectation_gaps: "Difference between expected and actual"
    emotional_responses: "How users felt during interaction"
    feature_priorities: "What users care about most"
    
  pattern_identification:
    common_pain_points: "Issues experienced by multiple users"
    successful_interactions: "What worked well consistently"
    user_segments: "Different types of users and their needs"
    edge_cases: "Unusual but important scenarios"
    
  priority_matrix:
    high_impact_easy_fix: "Quick wins to implement immediately"
    high_impact_hard_fix: "Important changes requiring significant effort"
    low_impact_easy_fix: "Nice-to-have improvements"
    low_impact_hard_fix: "Changes to defer or reconsider"
```

#### Next Steps Planning
```
Iteration Planning Worksheet

Based on Testing Results:

Immediate Changes (Next 1-2 days):
├── [ ] [Specific change and rationale]
├── [ ] [Specific change and rationale]
└── [ ] [Specific change and rationale]

Short-term Improvements (Next 1-2 weeks):
├── [ ] [Change description and success criteria]
├── [ ] [Change description and success criteria]
└── [ ] [Change description and success criteria]

Future Considerations (Next phase):
├── [ ] [Feature or change for later development]
├── [ ] [Feature or change for later development]
└── [ ] [Feature or change for later development]

Additional Research Needed:
├── [ ] [What we still need to learn]
├── [ ] [Who we need to talk to]
└── [ ] [What we need to test further]

Project Management Integration:
├── Sprint Planning: How will changes fit into development cycles?
├── Resource Allocation: What skills and time are needed?
├── Timeline Impact: How do changes affect project milestones?
├── Stakeholder Communication: Who needs to be informed?
└── Success Metrics: How will we measure improvement?
```

---

## Integration with Traditional PM Practices

### Design Thinking + Agile Integration

#### Sprint Integration Framework
```yaml
dt_agile_integration:
  sprint_0_preparation:
    activities: ["Empathy research", "Problem definition", "Initial ideation"]
    deliverables: ["User personas", "Problem statement", "HMW questions"]
    duration: "1-2 weeks before Sprint 1"
    
  sprint_planning_enhancement:
    user_story_refinement: "Include empathy insights in story creation"
    acceptance_criteria: "Add user experience criteria"
    definition_of_done: "Include user validation requirements"
    
  sprint_execution:
    daily_standups: "Include user feedback and insights"
    prototype_development: "Build testable increments"
    user_testing: "Test with real users during sprint"
    
  sprint_review_expansion:
    demo_to_users: "Include actual users in sprint review"
    feedback_collection: "Structured user feedback process"
    empathy_check: "Review how well solution meets user needs"
    
  retrospective_enhancement:
    user_impact_review: "Assess impact on user experience"
    design_process_review: "Evaluate design thinking integration"
    continuous_improvement: "Refine DT integration approach"
```

### Design Thinking + Traditional Integration

#### Project Phase Integration
```
Traditional Phase Integration with Design Thinking

Initiating Phase:
├── Traditional: Project Charter, Stakeholder Register
├── DT Enhancement: Empathy research, User journey mapping
├── Outcome: Human-centered project charter
└── Deliverable: User-informed project scope

Planning Phase:
├── Traditional: Project Management Plan, WBS
├── DT Enhancement: Problem definition, Ideation sessions
├── Outcome: Solution-focused project plan
└── Deliverable: Innovation-driven work breakdown

Executing Phase:
├── Traditional: Direct and manage project work
├── DT Enhancement: Prototype development, User testing
├── Outcome: User-validated project deliverables
└── Deliverable: Human-centered solution increments

Monitoring & Controlling:
├── Traditional: Performance monitoring, Change control
├── DT Enhancement: User feedback loops, Design iteration
├── Outcome: Adaptive project management
└── Deliverable: User-informed project adjustments

Closing Phase:
├── Traditional: Project closure, Lessons learned
├── DT Enhancement: Solution impact assessment, User adoption
├── Outcome: Human-centered project success evaluation
└── Deliverable: User satisfaction and adoption metrics
```

### Innovation Project Framework

#### Innovation Project Canvas
```
Innovation Project Canvas

Problem Space:
├── User Problem: What problem are we solving for users?
├── Business Problem: What business challenge are we addressing?
├── Market Opportunity: What's the potential impact and size?
└── Constraints: What limitations do we need to work within?

Solution Space:
├── Core Concept: What's the central idea or approach?
├── Unique Value: What makes this solution different/better?
├── Key Features: What are the essential capabilities?
└── Success Metrics: How will we measure success?

Implementation:
├── Development Approach: How will we build this?
├── Resource Requirements: What do we need to succeed?
├── Timeline: When will key milestones be reached?
├── Risk Mitigation: What could go wrong and how will we address it?
└── Go-to-Market: How will we launch and scale?

Validation:
├── Assumption Testing: What assumptions need validation?
├── User Research: How will we continue learning about users?
├── Market Testing: How will we validate market demand?
└── Iteration Plan: How will we improve based on feedback?
```

---

## Workshop Facilitation Guide

### Facilitator Preparation

#### Facilitator Competency Framework
```yaml
facilitator_skills:
  core_competencies:
    group_facilitation: "Guide group discussions and activities effectively"
    design_thinking_expertise: "Deep understanding of DT process and methods"
    active_listening: "Hear and synthesize diverse perspectives"
    creative_problem_solving: "Help groups break through mental barriers"
    
  behavioral_skills:
    neutrality: "Remain impartial and manage personal biases"
    energy_management: "Maintain group energy and engagement"
    conflict_resolution: "Address disagreements constructively"
    time_management: "Keep activities on track and productive"
    
  technical_skills:
    tool_proficiency: "Use collaboration tools and templates effectively"
    documentation: "Capture and organize workshop outputs"
    visual_facilitation: "Use drawings and diagrams to clarify ideas"
    adaptation: "Modify activities based on group needs"
```

#### Pre-Workshop Facilitator Checklist
```
Facilitator Preparation Checklist

Content Preparation:
├── [ ] Review participant backgrounds and needs
├── [ ] Customize activities for specific context
├── [ ] Prepare backup activities for each stage
├── [ ] Practice timing for all activities
├── [ ] Prepare opening and closing remarks
└── [ ] Review problem statement and success criteria

Material Preparation:
├── [ ] Test all technology and tools
├── [ ] Organize physical materials and supplies
├── [ ] Prepare templates and handouts
├── [ ] Set up workspace for optimal collaboration
├── [ ] Create name tags and seating arrangements
└── [ ] Prepare documentation tools

Mental Preparation:
├── [ ] Review group dynamics principles
├── [ ] Practice challenging scenario responses
├── [ ] Prepare energizing activities
├── [ ] Plan for different personality types
├── [ ] Set personal intentions for the workshop
└── [ ] Prepare for unexpected situations
```

### Managing Workshop Dynamics

#### Common Challenges and Solutions

**Challenge: Dominant Participants**
```
Symptoms:
├── One person speaking most of the time
├── Others becoming quiet or disengaged
├── Ideas coming from limited perspectives
└── Group energy becoming unbalanced

Interventions:
├── Use structured turn-taking methods
├── Implement silent brainstorming periods
├── Ask specific individuals for input
├── Break into smaller groups
├── Use anonymous idea collection
└── Set speaking time limits

Prevention:
├── Establish ground rules at the beginning
├── Use diverse activity formats
├── Rotate leadership roles
└── Create psychological safety for all voices
```

**Challenge: Low Energy or Engagement**
```
Symptoms:
├── Participants seem tired or distracted
├── Limited participation in activities
├── Minimal idea generation
└── Lack of enthusiasm for process

Interventions:
├── Take a movement or stretch break
├── Change physical environment or seating
├── Introduce a high-energy icebreaker
├── Share success stories or inspiration
├── Acknowledge progress made so far
└── Ask participants what they need

Prevention:
├── Plan regular breaks and movement
├── Vary activity types and energy levels
├── Provide adequate food and hydration
├── Check in regularly with participants
└── Celebrate small wins throughout
```

### Workshop Documentation Template

#### Real-Time Documentation Framework
```yaml
workshop_documentation:
  session_overview:
    date_time: "Workshop date and duration"
    participants: "List of attendees and roles"
    facilitators: "Facilitation team members"
    objectives: "Workshop goals and success criteria"
    
  stage_outputs:
    empathize:
      - "User interview insights"
      - "Empathy maps"
      - "Key user needs identified"
      
    define:
      - "Problem statement"
      - "Point of view"
      - "How might we questions"
      
    ideate:
      - "Ideas generated (count and themes)"
      - "Selected concepts"
      - "Evaluation criteria used"
      
    prototype:
      - "Prototype type and fidelity"
      - "Key features included"
      - "Assumptions being tested"
      
    test:
      - "User feedback summary"
      - "Insights and learnings"
      - "Next steps identified"
      
  action_items:
    immediate_next_steps: "Actions to take within 1 week"
    project_implications: "How insights affect project scope/plan"
    follow_up_research: "Additional research or testing needed"
    stakeholder_communication: "Who needs to be informed and when"
```

---

## Success Metrics and KPIs

### Workshop Success Measurement

#### Immediate Workshop Metrics
```yaml
workshop_success_metrics:
  engagement_metrics:
    participation_rate: "Percentage of active participation from attendees"
    idea_generation: "Number of ideas generated per participant"
    time_on_task: "Percentage of time spent in productive activities"
    energy_levels: "Participant energy ratings throughout workshop"
    
  outcome_metrics:
    insights_generated: "Number of meaningful user insights discovered"
    problem_clarity: "Clarity of problem statement (1-10 rating)"
    solution_concepts: "Number of viable solution concepts identified"
    consensus_level: "Team alignment on next steps (1-10 rating)"
    
  satisfaction_metrics:
    workshop_rating: "Overall workshop satisfaction (1-10)"
    facilitator_effectiveness: "Facilitation quality rating (1-10)"
    process_value: "Perceived value of design thinking process (1-10)"
    recommendation_likelihood: "Net Promoter Score for workshop experience"
```

#### Post-Workshop Impact Metrics

**Short-term (1-3 months):**
```
Implementation Metrics:
├── Prototype development speed
├── User testing frequency
├── Iteration cycles completed
├── Stakeholder engagement levels
└── Project scope clarity improvement

User-Centered Metrics:
├── User research activities conducted
├── User feedback integration rate
├── User satisfaction with prototypes
├── User needs validation success
└── User story quality improvement
```

**Long-term (3-12 months):**
```
Business Impact Metrics:
├── Project delivery success rate
├── User adoption rates
├── Customer satisfaction scores
├── Business objective achievement
├── Innovation pipeline strength
└── Team design thinking capability

Organizational Metrics:
├── Design thinking adoption across teams
├── Innovation project success rate
├── Cross-functional collaboration improvement
├── User-centered decision making frequency
└── Creative problem-solving capability
```

---

## Related Templates and Integration Points

### Template Ecosystem Integration
- [User Empathy Mapping Template](./user_empathy_mapping_template.md) - Detailed empathy mapping process
- [Innovation Project Management Template](../../../organizational-frameworks/innovation-management/innovation_project_template.md) - Innovation project lifecycle
- [User Story Template](../../../domains/uncertainty/role-based-toolkits/product-owner/user-story-template.md) - User story integration with DT insights
- [Hybrid Project Management Templates](../../../Hybrid/Templates/) - Combining DT with traditional PM
- [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 Design Thinking Workshop template | [Author] |

---

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