---
# === IDENTITY ===
id: business/customer-research/jobs-to-be-done-interview-methodology/2026
canonical_question: "How do I run JTBD interviews — structured technique for uncovering true buying motivations?"
aliases:
  - "jobs to be done interview technique"
  - "JTBD switch interview methodology"
  - "how to uncover customer buying motivations with JTBD"
entity_type: execution_recipe
domain: business > customer-research > jobs-to-be-done interview methodology
region: global
jurisdiction: global
temporal_scope: 2024-2026

# === VERIFICATION ===
last_verified: 2026-03-11
confidence: 0.90
version: 1.0
first_published: 2026-03-11

# === TEMPORAL VALIDITY ===
temporal_validity:
  status: evolving
  last_breaking_change: null
  next_review: 2026-09-07
  change_sensitivity: medium

# === CONSTRAINTS ===
constraints:
  - "JTBD interviews must focus on actual purchase decisions — only interview people who recently bought or switched (within 90 days ideally)"
  - "The interview must uncover all four forces: push (current pain), pull (new solution appeal), anxiety (fear of change), habit (comfort with status quo)"
  - "Never ask 'Why did you buy X?' directly — reconstruct the timeline instead to uncover causal factors"
  - "Minimum 10 switch interviews to identify reliable patterns — fewer produces anecdotes, not insights"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "User needs general customer discovery questions, not purchase-motivation analysis"
    use_instead: "business/customer-research/customer-interview-guide-template/2026"
  - condition: "User needs demographic/firmographic targeting criteria"
    use_instead: "business/customer-research/ideal-customer-profile-framework/2026"

# === AGENT HINTS ===
inputs_needed:
  - key: product_stage
    question: "What stage is the product?"
    type: choice
    options: ["Pre-launch (analyzing competitor switches)", "Launched (analyzing own customer switches)", "Mature (analyzing churn/expansion)"]
  - key: purchase_type
    question: "What type of purchase decision?"
    type: choice
    options: ["B2B software purchase", "B2C product purchase", "B2B service engagement", "Subscription/SaaS"]
  - key: interview_count
    question: "How many switch interviews can you conduct?"
    type: choice
    options: ["5-10", "10-20", "20+"]

# === EXECUTION METADATA ===
execution:
  required_inputs:
    - name: "List of recent buyers/switchers"
      source: "CRM, customer success, or competitor research"
      format: "Contact list with purchase/switch date"
    - name: "Product/category context"
      source: "Founder / product team"
      format: "Description of the product category and competitive landscape"
  outputs:
    - name: "JTBD Force Diagram"
      format: "JSON + visual diagram"
      description: "Four-forces analysis (push, pull, anxiety, habit) with evidence from switch interviews"
    - name: "Job Stories"
      format: "Structured text"
      description: "When [situation], I want to [motivation], so I can [expected outcome] statements with evidence"
    - name: "Switch Timeline Map"
      format: "JSON"
      description: "Reconstructed decision timeline from first thought to purchase to first use"
  tools_required:
    - name: "Zoom / Google Meet"
      purpose: "Video call interviews with recording"
      tier: free
      cost: "$0 (Google Meet) to $13.33/mo (Zoom Pro)"
      alternatives: ["Phone calls", "In-person meetings"]
    - name: "Otter.ai / Rev"
      purpose: "Interview transcription"
      tier: free
      cost: "$0 (300 min/mo) to $8.33/mo"
      alternatives: ["Zoom transcription", "manual notes"]
    - name: "Miro / FigJam"
      purpose: "Force diagram visualization and timeline mapping"
      tier: free
      cost: "$0 (free tier)"
      alternatives: ["Whimsical", "draw.io"]
  credentials_needed:
    - service: "Zoom"
      type: "Account login"
      where_to_get: "https://zoom.us/signup"
      free_tier_limits: "40-minute meetings"
  estimated_duration: "2-4 weeks (10-20 interviews at 45-60 min each + analysis)"
  estimated_cost: "$0 (DIY) to $3,000 (recruited participants + professional transcription)"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/business/customer-research/jobs-to-be-done-interview-methodology/2026"
suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-11)"

# === RELATED UNITS ===
related_kos:
  depends_on:
    - id: business/customer-research/buyer-persona-development-methodology/2026
      label: "Persona profiles to identify interview targets"
  feeds_into:
    - id: business/customer-research/buyer-journey-mapping/2026
      label: "Journey mapping enriched with JTBD insights"
  related_to:
    - id: business/customer-research/customer-interview-guide-template/2026
      label: "General interview guide for broader discovery"
  alternative_to: []

# === SOURCES ===
sources:
  - id: src1
    title: "Jobs to Be Done Theory"
    author: Christensen Institute
    url: https://www.christenseninstitute.org/theory/jobs-to-be-done/
    type: official_docs
    published: 2024-01-15
    reliability: authoritative
  - id: src2
    title: "Jobs-to-be-Done: A Comprehensive Guide"
    author: Strategyn (Tony Ulwick)
    url: https://strategyn.com/jobs-to-be-done/
    type: official_docs
    published: 2024-06-01
    reliability: authoritative
  - id: src3
    title: "Jobs to Be Done (JTBD) in UX Research"
    author: User Interviews
    url: https://www.userinterviews.com/ux-research-field-guide-chapter/jobs-to-be-done-jtbd-framework
    type: community_resource
    published: 2025-01-10
    reliability: high
  - id: src4
    title: "How to Prepare for Jobs To Be Done Interviews"
    author: Omniconvert
    url: https://www.omniconvert.com/blog/jobs-to-be-done-interviews/
    type: technical_blog
    published: 2024-09-15
    reliability: high
  - id: src5
    title: "Jobs to be Done 101: Your Interviewing Style Primer"
    author: dscout
    url: https://dscout.com/people-nerds/the-jobs-to-be-done-interviewing-style-understanding-who-users-are-trying-to-become
    type: technical_blog
    published: 2024-11-01
    reliability: high
  - id: src6
    title: "Jobs to Be Done Theory and Frameworks Explained"
    author: GoPractice
    url: https://gopractice.io/product/jobs-to-be-done-the-theory-and-the-frameworks/
    type: technical_blog
    published: 2024-08-20
    reliability: high
---

# Jobs-to-be-Done Interview Methodology

## Purpose

This recipe produces JTBD force diagrams, job stories, and switch timeline maps from structured interviews with recent buyers or switchers. The output reveals the true causal factors behind purchase decisions — not what customers say they want, but the functional, social, and emotional forces that actually drove their behavior. These insights inform product positioning, feature prioritization, competitive strategy, and messaging that resonates with real buying motivations.

## Prerequisites

- [ ] **List of 10-20 recent buyers or switchers** — people who purchased your product (or a competitor's) within the past 90 days
- [ ] **Product/category context** — understanding of the competitive landscape and alternatives
- [ ] **Video call + recording setup** — [Zoom](https://zoom.us) or Google Meet with transcription
- [ ] **Miro or whiteboard tool** — for force diagram visualization
- [ ] **2-4 weeks of calendar availability** — for conducting and analyzing interviews

## Constraints

- JTBD interviews must focus on actual purchase decisions — only interview people who recently bought or switched (within 90 days ideally) [src1]
- The interview must uncover all four forces: push, pull, anxiety, and habit [src5]
- Never ask "Why did you buy X?" directly — reconstruct the timeline instead [src4]
- Minimum 10 switch interviews to identify reliable patterns [src2]

## Tool Selection Decision

```
Which path?
├── Pre-launch (no customers yet)
│   └── PATH A: Competitor Switch Analysis — interview people who recently switched TO a competitor
├── Launched (have customers)
│   └── PATH B: Own Customer Switch Analysis — interview people who recently switched TO you
├── Analyzing churn
│   └── PATH C: Churn Switch Analysis — interview people who switched AWAY from you
└── Category creation (no direct competitors)
    └── PATH D: Workaround Analysis — interview people using makeshift solutions
```

| Path | Who to Interview | Key Question | Primary Output |
|------|-----------------|-------------|---------------|
| A: Competitor Switch | Recent competitor customers | "What were you using before?" | Competitive opportunity map |
| B: Own Customer Switch | Your recent customers | "Walk me through deciding to buy us" | Product-market fit validation |
| C: Churn Switch | Recently churned customers | "Walk me through deciding to leave" | Retention strategy |
| D: Workaround Analysis | People using spreadsheets/manual | "Show me how you handle this today" | Category creation messaging |

## Execution Flow

### Step 1: Understand the Four Forces Framework

**Duration**: 30 minutes
**Tool**: Study / reference

Before interviewing, internalize the four forces that govern every purchase decision:

```
THE FOUR FORCES OF PROGRESS

Forces pushing toward the new solution:
┌─────────────────────────────────────────┐
│ PUSH: Dissatisfaction with current state │
│ "I'm frustrated that..."                │
│ "It takes too long to..."               │
│ "We keep losing money because..."       │
└─────────────────────────────────────────┘
┌─────────────────────────────────────────┐
│ PULL: Attraction of the new solution    │
│ "I saw that [product] could..."         │
│ "My colleague said it helped them..."   │
│ "I imagined being able to..."           │
└─────────────────────────────────────────┘

Forces pushing against the new solution:
┌─────────────────────────────────────────┐
│ ANXIETY: Fear of the new solution       │
│ "What if it doesn't work?"              │
│ "Will my team actually adopt it?"       │
│ "Is it secure enough?"                  │
└─────────────────────────────────────────┘
┌─────────────────────────────────────────┐
│ HABIT: Comfort with current state       │
│ "What we have works well enough..."     │
│ "Switching costs seem high..."          │
│ "We've always done it this way..."      │
└─────────────────────────────────────────┘

Purchase happens when: Push + Pull > Anxiety + Habit
```

**Verify**: You can explain the four forces to a colleague without notes.
**If failed**: Re-read the original framework at [Christensen Institute](https://www.christenseninstitute.org/theory/jobs-to-be-done/) before proceeding.

### Step 2: Build the JTBD Switch Interview Script

**Duration**: 1-2 hours
**Tool**: Document editor

```markdown
## JTBD Switch Interview Script (45-60 minutes)

### Opening (3 minutes)
"Thanks for making time. I'm trying to understand how people make
decisions about [category]. I'll ask you to walk me through the story
of how you ended up choosing [product]. There are no right or wrong
answers — I just want to understand the journey."

### Timeline Reconstruction (30-35 minutes)
Goal: Walk backward from the purchase, reconstructing every step.

"Let's start with the moment you actually purchased/signed up.
Can you walk me through that day?"

Then work BACKWARD through these phases:

PHASE 1 — The Purchase Moment
- "When exactly did you make the final decision?"
- "Where were you? What were you doing?"
- "Was anyone else involved in that moment?"
- "What was the final trigger that made you commit?"

PHASE 2 — Active Evaluation
- "Before you committed, what alternatives did you consider?"
- "How did you compare them? What criteria mattered most?"
- "Did you do a trial or demo? What stood out?"
- "Was there a moment you almost chose something else? What happened?"

PHASE 3 — Passive Looking
- "When did you first start thinking about finding a new solution?"
- "What were you doing when the idea first crossed your mind?"
- "Did you immediately start looking, or did you sit on it? How long?"
- "What made you go from thinking about it to actually searching?"

PHASE 4 — First Thought / Trigger Event
- "Can you remember the very first time you thought 'something needs to change'?"
- "What happened that day? Was there a specific incident?"
- "Had you thought about it before that? What was different this time?"

### Four Forces Probing (10-15 minutes)

PUSH (current pain):
- "What was the most frustrating thing about your old way?"
- "What was the cost — in time, money, or stress — of the old approach?"
- "If nothing had changed, what would have happened?"

PULL (new solution appeal):
- "What excited you about the new approach?"
- "What did you imagine your life/work being like after switching?"
- "Was there a specific feature or promise that stood out?"

ANXIETY (fear of switching):
- "What almost stopped you from switching?"
- "What were your biggest concerns about the new solution?"
- "Did you have a backup plan if it didn't work?"

HABIT (attachment to status quo):
- "What did you like about your old way of doing things?"
- "What would you miss if the old way disappeared completely?"
- "Did anyone on your team resist the change? Why?"

### Functional, Social, Emotional Dimensions (5 minutes)
- "Beyond the practical benefits, how did the switch make you feel?"
- "Did anyone else notice or comment on the change?"
- "How did you explain the decision to [boss/partner/team]?"

### Closing (2 minutes)
- "Looking back, is there anything about the decision that surprised you?"
- "Would you make the same choice again? Why?"
- "What would make you consider switching again?"
```

**Verify**: Script covers all four forces and all four timeline phases.
**If failed**: Cross-check against the four forces framework in Step 1.

### Step 3: Conduct 10-20 Switch Interviews

**Duration**: 2-3 weeks
**Tool**: Zoom + Otter.ai

Key execution rules for JTBD interviews:

```markdown
## JTBD Interview Execution Rules

1. RECORD everything. Timeline reconstruction requires exact sequence.
2. Think like a documentary filmmaker, not a surveyor.
3. When they say "I just decided to switch," push deeper:
   "Tell me more. What happened right before that moment?"
4. Use the "Columbo technique" — play slightly confused:
   "I'm not sure I understand — help me see that moment."
5. Energy changes = gold. When they get animated, dig deeper.
6. Silence is a tool. After they answer, wait 5 seconds. They'll add detail.
7. Note EMOTIONS explicitly: frustrated, excited, anxious, relieved, proud.
8. Capture exact timeline: "Was that days before or weeks before the purchase?"
9. Ask about the social context: "Who else knew you were looking?"
10. End with: "What would make you switch away from your current choice?"
```

**Verify**: Each interview produces a clear timeline with all four forces identified.
**If failed**: If forces are unclear, schedule a 15-minute follow-up to probe the missing dimension.

### Step 4: Map the Four Forces from Each Interview

**Duration**: 1-2 hours per interview batch
**Tool**: Miro + spreadsheet

For each interview, extract and classify the four forces:

```json
{
  "interview_id": "JTBD-001",
  "interviewee_context": {
    "role": "VP Marketing",
    "company_size": "150 employees",
    "previous_solution": "Spreadsheets + manual process",
    "new_solution": "HubSpot Marketing Hub",
    "switch_date": "2026-01-15",
    "time_from_first_thought_to_purchase": "4 months"
  },
  "timeline": {
    "first_thought_trigger": "Board presentation — couldn't answer ROI question",
    "first_thought_date": "2025-09-01",
    "passive_looking_start": "2025-09-15",
    "active_evaluation_start": "2025-11-01",
    "purchase_trigger": "Year-end budget deadline + competitor demo impressed",
    "purchase_date": "2026-01-15"
  },
  "four_forces": {
    "push": [
      {"statement": "Couldn't prove marketing ROI to the board", "intensity": "critical", "functional": true, "emotional": true},
      {"statement": "Team spending 15 hours/week on manual reporting", "intensity": "high", "functional": true, "emotional": false}
    ],
    "pull": [
      {"statement": "Saw a demo showing real-time attribution dashboard", "intensity": "high", "functional": true, "emotional": true},
      {"statement": "Competitor CMO recommended it at a conference", "intensity": "medium", "functional": false, "emotional": true}
    ],
    "anxiety": [
      {"statement": "Worried team wouldn't adopt — had failed with Marketo before", "intensity": "high", "functional": true, "emotional": true},
      {"statement": "Concerned about data migration from existing tools", "intensity": "medium", "functional": true, "emotional": false}
    ],
    "habit": [
      {"statement": "Team was comfortable with spreadsheet workflow", "intensity": "medium", "functional": false, "emotional": true},
      {"statement": "Existing agency relationship built around current tools", "intensity": "low", "functional": true, "emotional": false}
    ]
  },
  "job_story": "When I'm presenting to the board and can't answer ROI questions, I want a system that automatically attributes revenue to campaigns, so I can prove marketing's value and secure next year's budget."
}
```

**Verify**: Each interview has at least 2 entries per force (8 minimum total).
**If failed**: Re-listen to the recording. Forces are often implicit — look for emotional language, hesitation, and excitement.

### Step 5: Synthesize Patterns Across Interviews

**Duration**: 4-6 hours
**Tool**: Spreadsheet + Miro

Aggregate across all interviews to find the dominant forces:

```markdown
## Cross-Interview Pattern Analysis

### Top Push Factors (what drives people away from status quo)
| Push Factor | Frequency | Avg Intensity | Example Quote |
|------------|-----------|---------------|--------------|
| Can't prove ROI | 8/12 (67%) | Critical | "My job is on the line if I can't show numbers" |
| Manual reporting waste | 7/12 (58%) | High | "15 hours a week just building spreadsheets" |
| Data silos | 5/12 (42%) | Medium | "Marketing and sales see different numbers" |

### Top Pull Factors (what attracts to new solution)
| Pull Factor | Frequency | Avg Intensity | Example Quote |
|------------|-----------|---------------|--------------|
| Real-time dashboards | 9/12 (75%) | High | "I could finally see what's working TODAY" |
| Peer recommendation | 6/12 (50%) | Medium | "Three other CMOs told me to switch" |
| Consolidation promise | 5/12 (42%) | Medium | "One tool instead of seven" |

### Top Anxieties (what almost prevented the switch)
| Anxiety | Frequency | Avg Intensity | How Overcome |
|---------|-----------|---------------|-------------|
| Team adoption failure | 10/12 (83%) | High | Free trial + champion program |
| Data migration risk | 7/12 (58%) | Medium | Vendor migration service |
| Contract lock-in | 4/12 (33%) | Medium | Month-to-month option |

### Top Habits (what keeps people in status quo)
| Habit | Frequency | Avg Intensity | What Broke It |
|-------|-----------|---------------|-------------|
| Comfortable with current tools | 8/12 (67%) | Medium | Trigger event (board pressure) |
| Switching cost perception | 6/12 (50%) | Medium | ROI calculation showing 4x return |
```

**Output files**:
- `jtbd-force-analysis.json` — Structured four-forces analysis with evidence
- `job-stories.md` — Validated job stories in "When... I want... So I can..." format
- `switch-timeline-map.json` — Aggregated timeline showing decision phases and durations
- `competitive-positioning-insights.md` — How to position against each force

## Output Schema

```json
{
  "output_type": "jtbd_analysis",
  "format": "JSON",
  "columns": [
    {"name": "total_interviews", "type": "number", "description": "Switch interviews completed", "required": true},
    {"name": "push_factors", "type": "array", "description": "Ranked dissatisfaction drivers with frequency and intensity", "required": true},
    {"name": "pull_factors", "type": "array", "description": "Ranked attraction factors with frequency and intensity", "required": true},
    {"name": "anxieties", "type": "array", "description": "Ranked switching fears with frequency and how they were overcome", "required": true},
    {"name": "habits", "type": "array", "description": "Ranked status quo attachments with frequency and what broke them", "required": true},
    {"name": "job_stories", "type": "array", "description": "When/Want/SoICan statements with interview evidence", "required": true},
    {"name": "avg_decision_timeline_days", "type": "number", "description": "Average days from first thought to purchase", "required": true},
    {"name": "trigger_events", "type": "array", "description": "Events that initiated the switch journey", "required": true}
  ],
  "expected_row_count": "1 per product/category analyzed",
  "sort_order": "force frequency descending",
  "deduplication_key": "product_category"
}
```

## Quality Benchmarks

| Quality Metric | Minimum Acceptable | Good | Excellent |
|---------------|-------------------|------|-----------|
| Switch interviews completed | >= 8 | >= 12 | >= 20 |
| All four forces identified per interview | >= 70% of interviews | >= 85% | >= 95% |
| Timeline fully reconstructed | >= 60% of interviews | >= 80% | >= 90% |
| Job stories validated (3+ interviews support) | >= 2 | >= 4 | >= 6 |
| Emotional dimensions captured | >= 50% of forces | >= 70% | >= 90% |

**If below minimum**: Continue interviewing. If timeline reconstruction is weak, extend interviews to 75 minutes and spend more time on Phase 4 (first thought).

## Error Handling

| Error | Likely Cause | Recovery Action |
|-------|-------------|----------------|
| Interviewee can't remember the decision timeline | Purchase was too long ago (> 6 months) | Recruit more recent switchers (< 90 days) |
| Only functional forces emerge, no emotional | Interviewer not probing feelings | Add explicit emotional questions: "How did that make you feel?" |
| All answers point to price as the driver | Surface-level answers masking real motivations | Probe deeper: "If price were the same, would you still have switched? Why?" |
| Interviewee rationalizes post-purchase | Common cognitive bias (choice-supportive bias) | Use timeline reconstruction to get pre-decision perspective |
| Pattern doesn't emerge after 10 interviews | Sample too diverse or category too broad | Segment by switch type (e.g., from spreadsheets vs. from competitor) |

## Cost Breakdown

| Component | Free Tier | Paid Tier | At Scale |
|-----------|-----------|-----------|----------|
| Video calls | Google Meet ($0) | Zoom Pro ($13.33/mo) | Zoom Business ($18.33/mo) |
| Transcription | Zoom auto ($0) | Otter.ai ($8.33/mo) | Rev ($1.50/min) |
| Participant recruitment | Own customers ($0) | Respondent.io ($150/person) | UserTesting ($300/person) |
| Analysis tools | Google Sheets ($0) | Miro ($8/mo) | Dovetail ($29/mo) |
| **Total (12 interviews)** | **$0** | **$800-2,000** | **$3,000-5,000** |

## Anti-Patterns

### Wrong: Asking "Why Did You Buy This?"
Direct "why" questions trigger post-hoc rationalization. Customers construct logical narratives that sound convincing but don't reflect the actual messy, emotional decision process. [src1]

### Correct: Reconstruct the Timeline
Walk backward from the purchase moment. "What happened right before you clicked buy?" → "And before that?" → "When was the first time you thought about changing?" Timeline reconstruction bypasses rationalization and reveals actual causal sequences.

### Wrong: Focusing Only on Functional Jobs
Treating JTBD as purely functional ("I need to get this task done faster") and ignoring social and emotional dimensions. Research shows emotional and social forces often outweigh functional ones in purchase decisions. [src5]

### Correct: Probe All Three Dimensions
For every force, ask: "What was the practical impact?" (functional), "How did that make you feel?" (emotional), "Did anyone else notice or care?" (social). The emotional story is often the real buying trigger.

### Wrong: Interviewing Non-Switchers
Asking people who haven't recently made a purchase decision about what they "would" do. People who haven't switched are governed by habit and anxiety — their hypothetical answers don't predict real behavior. [src4]

### Correct: Only Interview Recent Switchers
Recruit people who made an actual purchase or switch within the last 90 days. Their memory is fresh, their emotions are still accessible, and the causal factors are recoverable.

## When This Matters

Use this recipe when you need to understand the true motivations behind purchase decisions — not stated preferences, but the actual forces that drive switching behavior. Critical for product positioning, competitive strategy, and marketing messaging that addresses real anxieties and leverages real push/pull factors.

## Related Units

- [Customer Interview Guide Template](/business/customer-research/customer-interview-guide-template/2026)
- [Buyer Persona Development Methodology](/business/customer-research/buyer-persona-development-methodology/2026)
- [Buyer Journey Mapping](/business/customer-research/buyer-journey-mapping/2026)
- [Ideal Customer Profile Framework](/business/customer-research/ideal-customer-profile-framework/2026)