---
# === IDENTITY ===
id: business/customer-validation/customer-discovery-interview-playbook/2026
canonical_question: "How do I run 20-40 customer discovery interviews — scripts, synthesis, constraint: 8/10 must describe problem unprompted?"
aliases:
  - "Customer discovery interview script and process"
  - "How to conduct Mom Test interviews at scale"
  - "Problem interview playbook with synthesis framework"
  - "JTBD customer interview process for startups"
entity_type: execution_recipe
domain: business > customer-validation > customer discovery interview playbook
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: stable
  last_breaking_change: null
  next_review: 2026-09-07
  change_sensitivity: low

# === CONSTRAINTS ===
constraints:
  - "Minimum 20 interviews required for pattern saturation — fewer produces unreliable signals"
  - "8 out of 10 interviewees must describe the target problem unprompted before problem is considered validated"
  - "Never pitch your solution during problem interviews — introducing your idea contaminates responses"
  - "All interviews must be recorded and transcribed for synthesis accuracy — memory alone produces confirmation bias"
  - "Interview-to-synthesis lag must not exceed 48 hours — delayed synthesis loses contextual nuance"
  - "Recruit from target ICP segments only — convenience samples from friends and family invalidate results"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "User already has validated problem and needs to test a specific solution"
    use_instead: "Search knowledgelib.io for solution validation interviews — no dedicated unit yet"
  - condition: "User needs to define ICP before interviewing"
    use_instead: "business/customer-research/ideal-customer-profile-framework/2026"
  - condition: "User needs a strategic overview of customer validation, not execution steps"
    use_instead: "Search knowledgelib.io for customer validation strategy — no dedicated unit yet"

# === AGENT HINTS ===
inputs_needed:
  - key: tool_preference
    question: "Which tool stack should be used for scheduling, recording, and synthesis?"
    type: choice
    options: ["Calendly + Zoom + Dovetail", "Google Forms + Meet + Sheets", "no preference — auto-select"]
  - key: technical_skill
    question: "What is the user's technical skill level?"
    type: choice
    options: ["non-technical (no-code only)", "semi-technical (can edit code)", "developer (can write code)"]
  - key: budget_for_tools
    question: "What's the tool/API budget?"
    type: choice
    options: ["free tier only", "up to $50/month", "up to $200/month", "no limit"]
  - key: interview_count
    question: "How many interviews are planned?"
    type: choice
    options: ["20 (minimum viable)", "30 (recommended)", "40 (high confidence)"]

# === EXECUTION METADATA ===
execution:
  required_inputs:
    - name: "ICP definition"
      source: "business/customer-research/icp-definition-framework/2026"
      format: "structured profile with demographics, firmographics, and behavioral criteria"
    - name: "Problem hypothesis"
      source: "business/startup-planning/startup-idea-structuring-template/2026"
      format: "1-2 sentence problem statement with assumed severity and frequency"
  outputs:
    - name: "Interview synthesis report"
      format: "structured document (Markdown or Google Doc)"
      description: "Pattern analysis across all interviews — validated problems ranked by frequency, severity, and willingness to pay, with verbatim quotes as evidence"
    - name: "Problem validation scorecard"
      format: "JSON or spreadsheet"
      description: "Go/no-go decision based on 8/10 unprompted problem mention threshold plus severity and frequency scores"
    - name: "Raw interview transcripts"
      format: "text files or Dovetail project"
      description: "Complete transcripts with timestamps, tagged by theme and problem cluster"
  tools_required:
    - name: "Scheduling tool"
      purpose: "Automate interview booking with prospects"
      tier: free
      cost: "$0 (free tier)"
      alternatives: ["Calendly", "Cal.com", "Google Calendar appointment slots"]
    - name: "Video conferencing"
      purpose: "Conduct and record remote interviews"
      tier: free
      cost: "$0 (free tier — 40 min limit on Zoom free)"
      alternatives: ["Zoom", "Google Meet", "Microsoft Teams"]
    - name: "Transcription service"
      purpose: "Convert interview recordings to searchable text"
      tier: free
      cost: "$0-10/month"
      alternatives: ["Otter.ai", "Zoom built-in transcription", "Google Meet transcription", "Dovetail"]
    - name: "Synthesis tool"
      purpose: "Tag, code, and analyze interview patterns"
      tier: paid
      cost: "$0 (spreadsheet) to $29/month (Dovetail)"
      alternatives: ["Dovetail", "Google Sheets", "Notion", "Miro"]
  credentials_needed:
    - service: "Calendly"
      type: "account (OAuth)"
      where_to_get: "https://calendly.com/signup"
      free_tier_limits: "1 event type, unlimited bookings"
    - service: "Zoom"
      type: "account (OAuth)"
      where_to_get: "https://zoom.us/signup"
      free_tier_limits: "40-minute meetings, unlimited 1:1 calls"
  estimated_duration: "3-6 weeks for 30 interviews (recruit week 1, interview weeks 2-4, synthesize week 4-5)"
  estimated_cost: "$0 (free tools) to $150/month (paid stack)"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/business/customer-validation/customer-discovery-interview-playbook/2026"
suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-11)"

# === RELATED UNITS ===
related_kos:
  depends_on:
    - id: "business/customer-research/ideal-customer-profile-framework/2026"
      label: "Building a scored ICP — firmographic/demographic criteria, behavioral signals, disqualifiers and a scoring rubric"
    - id: "business/startup-planning/startup-idea-structuring-template/2026"
      label: "Problem hypothesis to test during interviews"
  feeds_into:
    - id: "business/startup/mvp-scoping-framework/2026"
      label: "MVP scoping — feature prioritization, timeline estimation, and a locked 3-7 must-have scope document"
  related_to:
    - id: "business/market-research/competitive-landscape-mapping/2026"
      label: "Mapping a competitive landscape — direct competitors, indirect competitors, substitutes, potential entrants"
  alternative_to: []

# === SOURCES ===
sources:
  - id: src1
    title: "The Mom Test: How to talk to customers & learn if your business is a good idea when everyone is lying to you"
    author: Rob Fitzpatrick
    url: https://www.momtestbook.com
    type: book
    published: 2013-10-01
    reliability: authoritative
  - id: src2
    title: "Customer Interviews: How to Recruit, What to Ask, and How to Synthesize What You Learn"
    author: Teresa Torres
    url: https://www.producttalk.org/2022/12/customer-interviews/
    type: technical_blog
    published: 2022-12-01
    reliability: authoritative
  - id: src3
    title: "Continuous Discovery Habits"
    author: Teresa Torres
    url: https://www.producttalk.org/getting-started-with-discovery/
    type: book
    published: 2021-05-01
    reliability: authoritative
  - id: src4
    title: "Customer Interviews: How to Use the Jobs-to-Be-Done Framework"
    author: CXL
    url: https://cxl.com/blog/customer-interviews/
    type: technical_blog
    published: 2024-06-01
    reliability: high
  - id: src5
    title: "B2B Customer Discovery Interview Questions — A Master List"
    author: Etienne Garbugli
    url: https://leanb2bbook.com/blog/b2b-customer-discovery-interview-questions-the-master-list/
    type: technical_blog
    published: 2023-01-15
    reliability: high
  - id: src6
    title: "Customer Discovery Guide"
    author: JumpStart Inc. / Case Western Reserve
    url: https://www.jumpstartinc.org/wp-content/uploads/2018/01/Customer-Discover-Guide-01-02-18.pdf
    type: official_docs
    published: 2018-01-01
    reliability: high
  - id: src7
    title: "Analyze interviews and calls"
    author: Dovetail
    url: https://docs.dovetail.com/academy/analyze-interviews-and-calls
    type: official_docs
    published: 2025-01-01
    reliability: high
---

# Customer Discovery Interview Playbook

## Purpose

This recipe produces a validated problem hypothesis backed by 20-40 structured customer discovery interviews, a synthesis report with pattern analysis, and a go/no-go scorecard based on a clear threshold: at least 8 out of 10 interviewees must describe the target problem unprompted. The output replaces founder intuition with evidence-based problem validation that feeds directly into solution design and MVP scoping. [src1]

## Prerequisites
<!-- Agents: verify ALL prerequisites before executing. Missing prerequisites = failed execution. -->

- [ ] **ICP definition** available from business/customer-research — with firmographic and behavioral criteria specific enough to screen recruits
- [ ] **Problem hypothesis** — 1-2 sentence statement of the problem you believe exists, including assumed severity and frequency
- [ ] **Scheduling tool** — Calendly ([calendly.com/signup](https://calendly.com/signup)) or Cal.com account (free tier: 1 event type)
- [ ] **Video conferencing** — Zoom ([zoom.us/signup](https://zoom.us/signup)) or Google Meet account (free tier: 40-min meetings)
- [ ] **Recording consent language** — one-sentence disclosure to read at interview start (legal requirement in many jurisdictions)
- [ ] **Synthesis workspace** — Dovetail account, Google Sheet, or Notion database set up with tagging taxonomy

## Constraints
<!-- Hard rules. Agents: enforce throughout execution. Violating these = broken output or legal risk. -->

- Never mention your solution or product idea during problem interviews. Introducing your idea turns the interview into a pitch and contaminates responses. Ask about their life, not your idea. [src1]
- Record every interview with explicit consent. Memory-based notes miss 40-60% of actionable detail and introduce confirmation bias. [src2]
- Recruit from target ICP segments only. Friends, family, and convenience samples produce false validation. [src1]
- Synthesize within 48 hours of each interview batch. Delayed synthesis loses emotional context and non-verbal signals that inform severity coding. [src3]
- Stop adding interviews only after reaching pattern saturation — when 3 consecutive interviews reveal no new problem themes. Minimum 20, target 30. [src6]
- Validation threshold: 8/10 interviewees must describe the problem unprompted (without you naming it) before the problem is considered validated. Below this threshold, pivot or reframe.

## Tool Selection Decision

<!-- Agent selects the right tool path based on user inputs.
     Each path leads to a different execution flow below. -->

```
Which path?
├── User wants free tools AND simple workflow
│   └── PATH A: Free Lean — Google Calendar + Google Meet + Google Sheets
├── User wants free tools AND better synthesis
│   └── PATH B: Free Pro — Cal.com + Zoom (free) + Notion
├── User wants paid tools AND automated workflow
│   └── PATH C: Paid Standard — Calendly + Zoom Pro + Dovetail
└── User wants maximum efficiency AND scale beyond 40 interviews
    └── PATH D: Paid Scale — Calendly + Zoom + Dovetail + User Interviews (recruiting)
```

| Path | Tools | Cost | Speed (30 interviews) | Synthesis Quality |
|------|-------|------|-----------------------|-------------------|
| A: Free Lean | Google Calendar + Meet + Sheets | $0 | 4-6 weeks | Manual — adequate |
| B: Free Pro | Cal.com + Zoom free + Notion | $0 | 4-5 weeks | Structured — good |
| C: Paid Standard | Calendly + Zoom Pro + Dovetail | $45-75/mo | 3-4 weeks | AI-assisted — excellent |
| D: Paid Scale | Calendly + Zoom + Dovetail + User Interviews | $150-300/mo | 2-3 weeks | Automated — excellent |

## Execution Flow

### Step 1: Recruit Interviewees

**Duration**: 5-10 days
**Tool**: Scheduling tool + outreach channels

Recruit 35-50 candidates to yield 25-40 completed interviews (expect 30-40% no-show/decline rate). Recruit only from your ICP — never from friends, family, or people who owe you favors. [src1]

**Recruitment channels ranked by signal quality**:

```
Channel                          Signal Quality    Response Rate
────────────────────────────────────────────────────────────────
1. Warm intro via mutual contact    Highest           40-60%
2. LinkedIn personalized outreach   High              15-25%
3. Industry community/Slack/Reddit  High              10-20%
4. Cold email to ICP list           Medium            5-15%
5. Social media post (Twitter/X)    Medium            3-10%
6. Paid recruiting panel            Variable          80-95%
   (User Interviews, Respondent)
────────────────────────────────────────────────────────────────
```

**Outreach message template** (keep under 80 words):

```
Subject: Quick question about [their specific problem domain]

Hi [Name],

I'm researching how [ICP role] handles [problem domain].
I'm NOT selling anything — just learning.

Would you have 25 minutes for a conversation?
I'd love to hear about your experience with [topic].

[Calendly/scheduling link]

Happy to share what I learn across all conversations
as a thank-you.

[Your name]
```

**Verify**: 35+ candidates scheduled within 10 days. Track in a simple spreadsheet: name, company, role, ICP match score, scheduled date, status.
**If failed**: If under 20 scheduled after 7 days, add a second recruitment channel or offer a small incentive ($20-50 gift card).

### Step 2: Prepare Interview Script

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

Build a semi-structured script following Mom Test principles: ask about their life, not your idea. Focus on past behavior, not future intentions. Never ask hypothetical "would you" questions. [src1]

**Interview script structure** (25 minutes total):

```
OPENING (2 min):
─────────────────
"Thanks for making time. I'm researching [problem domain]
to understand the real challenges. There are no right or
wrong answers — I just want to learn about your experience.
Mind if I record for my notes? Everything stays confidential."

CONTEXT (3 min):
─────────────────
1. "Tell me about your role. What does a typical week look like?"
2. "Where does [problem domain] fit into your priorities?"

PROBLEM EXPLORATION (15 min):
─────────────────────────────
3. "Walk me through the last time you dealt with [broad topic area]."
   → Follow the story. Ask: "What happened next?"
   → Probe emotions: "How did that make you feel?"
   → Probe severity: "What was the impact on [their goal]?"

4. "What's the hardest part about [the process they described]?"
   → Let them name the problem. Do NOT name it for them.
   → If they name YOUR hypothesized problem unprompted: STRONG SIGNAL
   → If they name a different problem: note it — this is data

5. "How are you solving that today?"
   → Current solution reveals willingness to invest effort
   → "Cobbled-together" solutions = high pain signal

6. "What have you tried that didn't work?"
   → Failed attempts = evidence of active problem-seeking

7. "If you could wave a magic wand, what would change?"
   → Captures desired outcome (JTBD "so that I can...")

COMMITMENT TESTING (3 min):
───────────────────────────
8. "Who else on your team deals with this?"
   → Tests organizational scope + gets referral recruits

9. "Would you be open to a follow-up conversation
    when I have something more concrete to show?"
   → Measures genuine interest (time commitment signal)

CLOSE (2 min):
──────────────
"This was incredibly helpful. Is there anything I should
have asked but didn't?"
→ Often surfaces the most important insight of the interview
```

**Key rules for the interviewer**: [src1]
- Talk less than 30% of the time. Listen more than 70%.
- Never say your product idea. If they ask what you're building, deflect: "I'm still figuring that out — I want to understand the problem better first."
- When they give a compliment ("great idea!"), deflect and return to specifics: "Thanks — but tell me more about the last time this happened."
- Write down exact quotes, not paraphrases.

**Verify**: Script reviewed by at least one other person. Run one pilot interview with a non-ICP contact to test flow and timing.
**If failed**: If pilot runs over 30 minutes, cut questions. If conversation feels interrogative, add more "tell me about..." open-ended prompts.

### Step 3: Conduct Interviews

**Duration**: 2-4 weeks (2-3 interviews per day maximum)
**Tool**: Video conferencing + transcription
**Rate limit**: Maximum 3 interviews per day to avoid interviewer fatigue and ensure same-day note capture.

Run interviews following the script from Step 2. Adapt based on what you learn — if early interviews reveal a problem you did not hypothesize, add probing questions about it in subsequent interviews.

```
Per-interview checklist:
─────────────────────────
□ Recording consent given and acknowledged
□ Recording started (video + audio)
□ Note-taker present (or solo with recording)
□ Script available but NOT read verbatim
□ Timer visible — stay within 25-30 minutes
□ Exact quotes captured in notes (not paraphrases)
□ Commitment ask completed at end
□ 5-minute debrief immediately after:
  - What surprised me?
  - What problem did they describe unprompted?
  - Severity rating (1-5)
  - Would they be a design partner? (yes/no/maybe)
```

**After each interview, log in your tracking spreadsheet**:

```
Interview Tracking Log:
──────────────────────────────────────────────────────
| # | Name | Date | ICP Match | Problem Mentioned | Unprompted? | Severity | Current Solution | Commitment | Notes |
|---|------|------|-----------|-------------------|-------------|----------|-----------------|------------|-------|
| 1 | ...  | ...  | Y/N       | [exact quote]     | Y/N         | 1-5      | [what they use]  | Y/N        | ...   |
```

**Expected output**: After 10 interviews, you should see 2-3 problem themes emerging. After 20, the top problem should be clear. After 30, you should have reached saturation (no new themes in 3 consecutive interviews). [src6]
**Verify**: At least 80% of scheduled interviews completed. Tracking log fully populated for every interview.
**If failed**: If no-show rate exceeds 40%, send reminder messages 24 hours and 1 hour before. Consider rescheduling via the same booking link.

### Step 4: Synthesize Interview Data

**Duration**: 4-8 hours (batch after every 8-10 interviews)
**Tool**: Dovetail, Notion, or Google Sheets

Synthesis converts raw interview transcripts into structured patterns. Do this in batches of 8-10 interviews, not all at once at the end. [src2] [src7]

**Synthesis process**:

```
Step 4a: Tag and Code (per interview)
───────────────────────────────────────
1. Read/listen to full transcript
2. Highlight and tag every:
   - Problem statement (what hurts)
   - Severity indicator (how much it hurts)
   - Frequency indicator (how often it hurts)
   - Current solution (how they cope today)
   - Desired outcome (what "fixed" looks like)
   - Emotional signal (frustration, excitement, resignation)
3. Use consistent tag taxonomy across all interviews

Step 4b: Cluster into Themes (per batch)
─────────────────────────────────────────
1. Group tagged excerpts by problem theme
2. Name each cluster with a descriptive label
3. Count frequency: how many interviews mention this theme?
4. Rate average severity across interviews (1-5 scale)
5. Note whether mentions were prompted or unprompted

Step 4c: Build Evidence Table (running)
───────────────────────────────────────
| Problem Theme | Frequency (n/total) | Avg Severity | Unprompted Rate | Key Quotes | Current Solutions |
```

**Verify**: Every interview transcript has been fully tagged. No interview is unprocessed. Theme clusters are mutually exclusive (each excerpt belongs to exactly one cluster).
**If failed**: If themes overlap significantly, your taxonomy is too broad. Split overlapping themes into sub-themes and re-tag.

### Step 5: Score and Decide (Go/No-Go)

**Duration**: 1-2 hours
**Tool**: Spreadsheet or synthesis tool

Apply the validation scorecard to determine if the problem is validated, partially validated, or invalidated.

```
PROBLEM VALIDATION SCORECARD
═══════════════════════════════════════════════════════
Primary Problem Hypothesis: [state it]
Total Interviews Completed: ___

METRIC 1: Unprompted Problem Mention Rate
─────────────────────────────────────────
Interviewees who described this problem
without being asked about it specifically:  ___/___ = ___%

Threshold:  >= 80% (8/10) = VALIDATED
            60-79%        = PARTIALLY VALIDATED (needs reframing)
            < 60%         = NOT VALIDATED (pivot)

METRIC 2: Severity Score
────────────────────────
Average severity across interviews:  ___/5.0

Threshold:  >= 4.0 = High severity (strong signal)
            3.0-3.9 = Medium (viable but not urgent)
            < 3.0   = Low (nice-to-have, risky to build for)

METRIC 3: Active Solution Seeking
──────────────────────────────────
Interviewees currently using a workaround
or paying for a partial solution:  ___/___ = ___%

Threshold:  >= 60% = Strong (people invest effort to solve this)
            30-59% = Moderate (problem exists but not acute)
            < 30%  = Weak (they tolerate the problem)

METRIC 4: Commitment Signal
───────────────────────────
Interviewees who agreed to a follow-up
or offered to introduce colleagues:  ___/___ = ___%

Threshold:  >= 50% = Strong buying signal
            25-49% = Moderate interest
            < 25%  = Low engagement

OVERALL DECISION:
─────────────────
All 4 metrics at "validated/strong" level  → GO
Metric 1 validated + 2 of 3 others strong  → CONDITIONAL GO
Metric 1 not validated                      → NO GO (pivot or reframe)
Any single metric below minimum             → INVESTIGATE further
═══════════════════════════════════════════════════════
```

**Verify**: Scorecard uses actual tallied data from the tracking log, not impressions. Cross-check counts against raw log.
**If failed**: If Metric 1 is between 60-79%, conduct 10 more interviews with reframed problem language before making a final decision.

### Step 6: Produce Deliverables

**Duration**: 2-4 hours

Generate the final synthesis report and problem validation scorecard for downstream consumption.

```
Final Deliverables:
────────────────────
1. Problem Validation Scorecard (JSON or spreadsheet)
   - All 4 metrics with raw numbers
   - Go/no-go recommendation with reasoning

2. Synthesis Report (Markdown or Google Doc)
   - Executive summary (1 paragraph)
   - Top 3 validated problems ranked by frequency × severity
   - Per-problem evidence: frequency, severity, quotes,
     current solutions, desired outcomes
   - Unexpected findings (problems you didn't hypothesize)
   - Recommended next steps

3. Raw Data Archive
   - All transcripts (tagged)
   - Interview tracking log (complete)
   - Recruitment log with conversion rates

4. Design Partner List
   - Interviewees who agreed to follow-up
   - Sorted by engagement level and ICP fit
```

**Output files**:
- `interview-synthesis-report.md` — Primary synthesis document with evidence-backed findings
- `problem-validation-scorecard.json` — Machine-readable scorecard for pipeline consumption
- `interview-tracking-log.csv` — Complete log of all interviews with coded data
- `design-partners.csv` — Qualified follow-up candidates for solution interviews

## Output Schema

<!-- Exact format of the deliverable. Downstream agents and dashboard cards
     reference this schema to consume the output. -->

```json
{
  "output_type": "problem_validation_scorecard",
  "format": "JSON",
  "columns": [
    {"name": "problem_hypothesis", "type": "string", "description": "The problem statement being validated", "required": true},
    {"name": "total_interviews", "type": "number", "description": "Total completed interviews", "required": true},
    {"name": "unprompted_mention_rate", "type": "number", "description": "Fraction of interviewees who mentioned problem unprompted (0.0-1.0)", "required": true},
    {"name": "avg_severity", "type": "number", "description": "Average severity score across interviews (1.0-5.0)", "required": true},
    {"name": "active_solution_rate", "type": "number", "description": "Fraction using a workaround or paying for partial solution (0.0-1.0)", "required": true},
    {"name": "commitment_rate", "type": "number", "description": "Fraction who agreed to follow-up or made referral (0.0-1.0)", "required": true},
    {"name": "decision", "type": "string", "description": "GO, CONDITIONAL_GO, NO_GO, or INVESTIGATE", "required": true},
    {"name": "top_problems", "type": "array", "description": "Top 3 validated problems with frequency and severity", "required": true},
    {"name": "design_partners", "type": "number", "description": "Count of interviewees who agreed to follow-up", "required": false}
  ],
  "expected_row_count": "1",
  "sort_order": "N/A (single record)",
  "deduplication_key": "problem_hypothesis"
}
```

## Quality Benchmarks

<!-- How to evaluate if the output is good enough.
     Links to benchmark cards where applicable. -->

| Quality Metric | Minimum Acceptable | Good | Excellent |
|---------------|-------------------|------|-----------|
| Interviews completed | 20 | 30 | 40+ |
| Unprompted problem mention rate | >= 60% (partial) | >= 80% (validated) | >= 90% (strong) |
| Average severity score | >= 3.0/5.0 | >= 3.5/5.0 | >= 4.0/5.0 |
| Active solution seeking rate | >= 30% | >= 50% | >= 70% |
| Transcript tagging completeness | 80% of transcripts | 95% of transcripts | 100% of transcripts |
| Synthesis lag (hours after interview) | < 72 hours | < 48 hours | < 24 hours |

**If below minimum**: If fewer than 20 interviews completed, extend recruitment and continue. If unprompted mention rate is below 60% after 20 interviews, reframe the problem hypothesis and conduct 10 more interviews with the new framing.

## Error Handling

<!-- Common failures and recovery actions. Agents need this to handle
     execution errors without human intervention. -->

| Error | Likely Cause | Recovery Action |
|-------|-------------|----------------|
| High no-show rate (> 40%) | Weak outreach message or wrong channel | Rewrite outreach emphasizing value exchange ("I'll share cross-industry findings"), add calendar reminders at 24h and 1h |
| Interviewees give only compliments, no real problems | Questions too leading or solution was mentioned | Reset script to pure Mom Test questions, remove any solution hints, add more "tell me about the last time..." prompts [src1] |
| All interviewees describe different problems | ICP too broad or problem hypothesis too vague | Narrow ICP segment, pick one specific job-to-be-done, re-recruit from tighter segment [src4] |
| Interview transcripts missing or corrupt | Recording failed or consent not given | Always check recording is active at minute 1. Use backup note-taker. Re-interview critical contacts if recording lost |
| Synthesis themes are overlapping and unclear | Tag taxonomy too broad or inconsistent | Stop, rebuild taxonomy with mutual exclusivity, re-tag from transcript highlights |
| Interviewer talks more than 30% of the time | Script read verbatim or interviewer pitching | Practice active listening, use script as reference not script. Record and review own talk ratio after each interview [src1] |

## Cost Breakdown

<!-- Real cost analysis so agents can warn users before execution. -->

| Component | Free Tier | Paid Tier | At Scale |
|-----------|-----------|-----------|----------|
| Scheduling (Calendly/Cal.com) | $0 (1 event type) | $10/mo (multiple event types) | $16/mo (team) |
| Video conferencing (Zoom/Meet) | $0 (40-min limit) | $13/mo (Zoom Pro, no limit) | $20/mo (Business) |
| Transcription (Otter.ai/built-in) | $0 (300 min/mo) | $10/mo (1200 min) | $24/mo (6000 min) |
| Synthesis (Sheets/Dovetail) | $0 (Google Sheets) | $29/mo (Dovetail) | $49/mo (Dovetail team) |
| Participant incentives | $0 (value exchange) | $20-50/interview gift card | $50-100/interview |
| **Total for 30 interviews** | **$0** | **$62-112/mo + $0-1500 incentives** | **$109-159/mo + $1500-3000 incentives** |

## Anti-Patterns

### Wrong: Asking "Would you use a product that does X?"
Hypothetical questions produce hypothetical answers. People are terrible at predicting their own future behavior. Asking "would you buy this?" yields compliments and false positives that lead founders to build products nobody actually uses. This is the core insight of the Mom Test — even your mother will lie to you to be supportive. [src1]

### Correct: Ask about past behavior and current pain
Ask "Tell me about the last time you dealt with [problem domain]" and listen for the problem to emerge naturally. Past behavior is the best predictor of future behavior. If they describe your hypothesized problem without you naming it, that is a validated signal.

### Wrong: Stopping at 10-12 interviews because patterns "seem clear"
Early pattern recognition is often confirmation bias. The first 10 interviews tend to confirm your hypothesis because you unconsciously seek confirmation. True saturation requires hearing the same patterns from people you did not expect to agree. [src6]

### Correct: Continue until 3 consecutive interviews yield no new themes
The saturation rule: conduct at least 20 interviews, and continue until 3 in a row surface zero new problem themes. This typically happens between interview 25 and 35.

### Wrong: Synthesizing all interviews in one marathon session at the end
Batch synthesis at the end produces shallow analysis. You lose the contextual memory of tone, hesitation, and emphasis that informs severity coding. You also miss the opportunity to adapt your script based on emerging themes. [src2]

### Correct: Synthesize in batches of 8-10, within 48 hours
Process each batch while the conversations are fresh. Update your theme clusters and tracking log. Adjust questions for the next batch based on emerging patterns.

## When This Matters

Use this recipe when a founder or product team needs to validate that a real, severe, frequent problem exists before investing in building a solution. It produces structured evidence that replaces gut feeling with data. The output feeds directly into solution interview design, MVP scoping, and investor pitch evidence. Requires an ICP definition as input — without knowing who to interview, the process produces noise instead of signal.

## Related Units

- [ICP Definition Framework](/business/customer-research/icp-definition-framework/2026) — prerequisite: defines who to recruit for interviews
- [Startup Idea Structuring Template](/business/startup-planning/startup-idea-structuring-template/2026) — prerequisite: the problem hypothesis to validate
- [Solution Interview Methodology](/business/customer-validation/solution-interview-methodology/2026) — next step after problem validation confirmed
- [MVP Scoping Framework](/business/startup-planning/mvp-scoping-framework/2026) — downstream: uses validated problems to scope build
- [Competitive Landscape Analysis](/business/customer-research/competitive-landscape-analysis/2026) — related: existing solutions customers mention in interviews