@c0x12c/ai-toolkit 1.15.0

package/frameworks/06-jobs-to-be-done.md

@@ -0,0 +1,358 @@
+# Jobs to be Done (JTBD) Framework
+
+## Overview
+Jobs to be Done is a framework for understanding customer motivations and needs by focusing on the "job" customers are trying to accomplish rather than demographics or product features. Pioneered by Clayton Christensen and further developed by Tony Ulwick and others, JTBD shifts focus from what customers buy to why they buy it. The core insight: people don't buy products, they hire them to do a job.
+
+## When to Use
+- Understanding true customer motivations
+- Identifying innovation opportunities
+- Solving product-market fit challenges
+- Competitive analysis and positioning
+- Feature prioritization decisions
+- Market segmentation strategies
+- Creating breakthrough innovations
+
+## Core Concepts
+
+### What is a "Job"?
+A Job is the progress that a customer is trying to make in a particular circumstance. It has three dimensions:
+
+1. **Functional Job**: The practical task to accomplish
+2. **Emotional Job**: How the customer wants to feel
+3. **Social Job**: How the customer wants to be perceived
+
+### Job Statement Structure
+"When [situation], I want to [motivation], so I can [expected outcome]."
+
+Example: "When I'm running late for work, I want to grab breakfast quickly, so I can eat during my commute without making a mess."
+
+## The JTBD Process
+
+### Step 1: Identify Jobs
+
+**Observation Techniques**:
+1. **Ethnographic Research**: Watch customers in their environment
+2. **Journey Mapping**: Map the entire process
+3. **Contextual Inquiry**: Understand circumstances
+4. **Diary Studies**: Track behaviors over time
+
+**Interview Techniques**:
+1. **Timeline Interviews**: Reconstruct purchase journey
+2. **Switch Interviews**: Why did they switch solutions?
+3. **Forces of Progress**: What pushed/pulled them?
+4. **Job Story Mining**: Uncover underlying jobs
+
+### Step 2: Deconstruct Jobs
+
+**Job Map Components**:
+1. **Define**: Determine objectives and plan approach
+2. **Locate**: Gather items and information needed
+3. **Prepare**: Set up the environment
+4. **Confirm**: Verify readiness to perform job
+5. **Execute**: Perform the job
+6. **Monitor**: Assess progress
+7. **Modify**: Make alterations
+8. **Conclude**: Finish the job
+
+**Outcome Statements**:
+Format: [Direction] + [Metric] + [Object] + [Contextual Clarifier]
+
+Example: "Minimize the time it takes to find parking near the destination"
+
+### Step 3: Quantify Importance and Satisfaction
+
+**Outcome-Driven Innovation (ODI) Metrics**:
+- **Importance**: How important is this outcome? (1-5 scale)
+- **Satisfaction**: How satisfied are you currently? (1-5 scale)
+- **Opportunity Score**: Importance + (Importance - Satisfaction)
+
+**Opportunity Algorithm**:
+- Score > 15: Extreme opportunity
+- Score 12-15: High opportunity
+- Score 8-12: Medium opportunity
+- Score < 8: Low opportunity
+
+### Step 4: Discover Opportunities
+
+**Underserved Outcomes**: High importance, low satisfaction
+**Overserved Outcomes**: Low importance, high satisfaction
+**Table Stakes**: High importance, high satisfaction
+**Irrelevant**: Low importance, varied satisfaction
+
+### Step 5: Position and Innovate
+
+**Innovation Strategies**:
+1. **Improve Underserved Outcomes**: Direct innovation
+2. **Reduce Overserving**: Cut costs/features
+3. **Discover Non-Consumers**: New market creation
+4. **Change the Basis of Competition**: Reframe the job
+
+## JTBD Interview Techniques
+
+### The Timeline Interview
+
+**Setup**: "Take me back to when you first started thinking about [buying/switching]..."
+
+**Key Questions**:
+1. When did you first think about solving this problem?
+2. What triggered that thought?
+3. What did you do next?
+4. Who else was involved?
+5. What alternatives did you consider?
+6. What concerns did you have?
+7. What finally made you decide?
+
+### The Forces of Progress
+
+**Push Forces** (Problems with current solution):
+- What's not working?
+- What frustrations exist?
+- What triggered the search?
+
+**Pull Forces** (Attraction to new solution):
+- What caught your attention?
+- What did you hope to achieve?
+- What excited you?
+
+**Anxieties** (Concerns about new solution):
+- What worried you?
+- What could go wrong?
+- What did you fear losing?
+
+**Habits** (Inertia keeping them in place):
+- What's comfortable about status quo?
+- What would be hard to change?
+- What routines would be disrupted?
+
+### Finding Emotional and Social Jobs
+
+**Emotional Job Questions**:
+- How do you want to feel when using this?
+- What emotions are you trying to avoid?
+- What would make you feel successful?
+
+**Social Job Questions**:
+- How do you want others to perceive you?
+- What would others think if they saw you using this?
+- How does this reflect on your identity?
+
+## JTBD Canvas
+
+### Components:
+1. **Job Performer**: Who's trying to get the job done?
+2. **Job Context**: When/where does the job arise?
+3. **Job Statement**: The core functional job
+4. **Success Criteria**: How is success measured?
+5. **Obstacles**: What makes the job difficult?
+6. **Current Solutions**: What's hired today?
+7. **Emotional Aspects**: Desired feelings
+8. **Social Aspects**: Desired perceptions
+
+## Common Jobs Across Industries
+
+### B2C Examples
+
+**Food & Beverage**:
+- "Help me stay energized throughout my workday"
+- "Enable me to share a memorable meal with loved ones"
+- "Allow me to eat healthy without spending hours cooking"
+
+**Transportation**:
+- "Get me to my destination feeling productive"
+- "Help me transport my family safely and comfortably"
+- "Enable me to make a good impression when I arrive"
+
+**Entertainment**:
+- "Help me unwind after a stressful day"
+- "Give me something to talk about with friends"
+- "Make me feel connected to a community"
+
+### B2B Examples
+
+**Software**:
+- "Help me make data-driven decisions quickly"
+- "Enable my team to collaborate without friction"
+- "Ensure I never lose critical business data"
+
+**Consulting**:
+- "Help me look competent in front of my board"
+- "Enable me to transform my organization efficiently"
+- "Reduce the risk of major strategic decisions"
+
+## JTBD vs Other Frameworks
+
+### vs Personas
+- **Personas**: Focus on who the customer is
+- **JTBD**: Focus on what the customer is trying to do
+- **Use Together**: Personas hiring for different jobs
+
+### vs User Stories
+- **User Stories**: Feature-focused ("As a user, I want...")
+- **JTBD**: Outcome-focused ("When situation, I want progress")
+- **Use Together**: JTBD informs better user stories
+
+### vs Design Thinking
+- **Design Thinking**: Broad exploration process
+- **JTBD**: Specific lens for understanding needs
+- **Use Together**: JTBD within design thinking process
+
+## Innovation Using JTBD
+
+### New Market Creation
+Find people who have a job but:
+- Can't afford current solutions
+- Lack skills for current solutions
+- Lack access to current solutions
+
+Example: Minute Clinic for basic healthcare
+
+### Disruptive Innovation
+Target overserved customers:
+- Simpler solution
+- Lower cost
+- "Good enough" performance
+
+Example: Google Docs vs Microsoft Office
+
+### Sustaining Innovation
+Better serve core jobs:
+- Improve important outcomes
+- Integrate related jobs
+- Remove barriers
+
+Example: iPhone integrating multiple devices
+
+## JTBD Metrics
+
+### Leading Indicators
+- Job completion rate
+- Time to complete job
+- Effort required
+- Error rate
+- Satisfaction scores
+
+### Business Metrics
+- Market share among job performers
+- Pricing power
+- Customer lifetime value
+- Word-of-mouth referrals
+- Competitive win rate
+
+## Common Mistakes
+
+1. **Focusing on Activities, Not Outcomes**
+   - Wrong: "I want to use a spreadsheet"
+   - Right: "I want to understand my finances"
+
+2. **Being Too Specific or Too Broad**
+   - Too Specific: "Check email on iPhone"
+   - Too Broad: "Communicate"
+   - Just Right: "Stay connected while mobile"
+
+3. **Confusing Jobs with Solutions**
+   - Solution: "I want a faster car"
+   - Job: "Get to destinations quickly"
+
+4. **Ignoring Emotional/Social Dimensions**
+   - Only focusing on functional jobs
+   - Missing critical decision factors
+
+5. **Leading the Witness**
+   - Suggesting jobs rather than discovering
+   - Confirming biases
+
+## Tools and Resources
+
+### Interview Tools
+- **Calendly**: Schedule interviews
+- **Otter.ai**: Transcription
+- **Miro/Mural**: Journey mapping
+- **Dovetail**: Qualitative analysis
+
+### Analysis Tools
+- **Opportunity Calculator**: Score outcomes
+- **Job Map Templates**: Structure analysis
+- **Forces Diagram**: Visualize switch forces
+
+### Books
+- "Competing Against Luck" - Clayton Christensen
+- "Jobs to be Done" - Anthony Ulwick
+- "When Coffee and Kale Compete" - Alan Klement
+- "Intercom on Jobs to be Done"
+
+## JTBD in Practice
+
+### Case Study: Milkshake Marketing
+
+**The Challenge**: Fast food chain wanted to increase milkshake sales
+
+**Traditional Approach**: Better flavors, prices, sizes based on demographics
+
+**JTBD Approach**: 
+- Discovered morning commuters were biggest buyers
+- Job: "Help me stay occupied during boring commute"
+- Competing against: Bagels, bananas, boredom
+- Solution: Thicker shakes, chunks of fruit
+
+**Result**: Sales increased without changing core product
+
+### Case Study: Harvard Business School
+
+**The Challenge**: Online education threatening traditional MBA
+
+**JTBD Discovery**:
+- Functional: Gain business knowledge
+- Emotional: Feel confident in business situations
+- Social: Join elite business network
+
+**Innovation**: Hybrid programs combining online efficiency with networking
+
+## Quick Start Guide
+
+### Week 1: Job Discovery
+1. Pick a product/market to study
+2. Recruit 5-10 recent purchasers
+3. Conduct timeline interviews
+4. Map the forces of progress
+
+### Week 2: Job Analysis
+1. Synthesize interview findings
+2. Write job statements
+3. Map the job process
+4. Identify outcomes
+
+### Week 3: Opportunity Identification
+1. Survey importance/satisfaction
+2. Calculate opportunity scores
+3. Identify underserved outcomes
+4. Brainstorm solutions
+
+### Week 4: Solution Development
+1. Prototype solutions for top opportunities
+2. Test with job performers
+3. Measure outcome improvement
+4. Iterate based on feedback
+
+## Integration Checklist
+
+### Product Development
+- [ ] Job stories in backlog
+- [ ] Features mapped to outcomes
+- [ ] Success metrics = job completion
+
+### Marketing
+- [ ] Messaging addresses job progress
+- [ ] Segments based on jobs not demographics
+- [ ] Case studies show job success
+
+### Sales
+- [ ] Discovery uncovers jobs
+- [ ] Proposals address outcomes
+- [ ] ROI based on job value
+
+### Strategy
+- [ ] Market definition by job
+- [ ] Competitive analysis by job performance
+- [ ] Innovation pipeline addresses unmet outcomes
+
+The Jobs to be Done framework fundamentally changes how we think about customers and competition. By focusing on the progress people are trying to make, rather than the products they buy, JTBD reveals opportunities for innovation that demographic analysis misses. The key is to stop asking "What would customers like?" and start asking "What are customers trying to get done?"