スキル一覧に戻る
Coowoolf

causal-interview-protocol

by Coowoolf

105 Product Management Skills extracted from Lenny's Podcast - For use with Claude Code / Cursor / Windsurf

1🍴 0📅 2026年1月24日
GitHubで見るManusで実行

SKILL.md


name: Causal Interview Protocol description: A JTBD interviewing technique to reconstruct the customer's timeline and uncover causal mechanisms behind a purchase. Resembles criminal investigation—penetrate surface-level answers to find the struggling moment.

The Causal Interview Protocol

"It's criminal and intelligence interrogation that feels like therapy because most people don't actually know why they bought." — Bob Moesta

What It Is

A specific interviewing technique designed to reconstruct the customer's timeline and uncover the causal mechanisms behind a purchase, resembling a criminal investigation or therapy session rather than a standard survey.

When To Use

  • During customer discovery
  • Validating zero-to-one product concepts
  • Understanding why a product is being "hired"
  • When survey data seems unreliable or shallow

The Protocol

┌──────────────────────────────────────────────────────┐
│  STEP 1: RECRUIT                                     │
│  → Interview ONLY people who already switched        │
│  → Recent behavior > Hypothetical intent             │
├──────────────────────────────────────────────────────┤
│  STEP 2: RECONSTRUCT TIMELINE                        │
│  → Work backwards from purchase moment               │
│  → "Walk me through when you first thought about..." │
├──────────────────────────────────────────────────────┤
│  STEP 3: PENETRATE LAYERS                            │
│  → Layer 1: Pablum (polite surface answers)          │
│  → Layer 2: Fantasy/Nightmare (hypothetical fears)   │
│  → Layer 3: Reality (actual causal mechanism)        │
├──────────────────────────────────────────────────────┤
│  STEP 4: CLUSTER CAUSAL PATHWAYS                     │
│  → Group by WHY they switched, not WHO they are      │
│  → Ignore demographics initially                     │
└──────────────────────────────────────────────────────┘

Core Principles

1. Interview Only Actual Switchers

People who have already made the progress (purchased/switched), not prospects.

2. No Discussion Guide

Follow the story and the energy. Don't force a script.

3. Penetrate the Pablum

Get past polite surface answers to the real story.

4. Cluster by Causality

Group interviews by causal pathways, not demographic segments.

5. Find the Struggling Moment

Listen for what triggered the search.

Key Questions

❌ AVOID: "Why did you buy this?"
   (Invites post-hoc rationalization)

✅ USE: "Walk me through what happened..."
   "What was going on in your life when you first thought about this?"
   "Tell me about the moment you decided to actually purchase..."
   "What did you try before this?"

Common Mistakes

❌ Asking "Why?" repeatedly (invites rationalization)

❌ Believing customers' hypothetical claims ("I would buy this")

❌ Segmenting by demographics instead of causal pathways

Real-World Example

Discovering why people buy Snickers (meal replacement/masticaton for energy) vs. Milky Way (emotional reward/melting texture), leading to completely different competitive sets.


Source: Bob Moesta, Co-creator of Jobs-to-be-Done, Lenny's Podcast

スコア

総合スコア

55/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

0/5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です