phuryn/pm-skills

interview-script

Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/phuryn/pm-skills --skill interview-script

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Customer Interview Script

Create a structured interview script that surfaces real insights, not just opinions. Follows "The Mom Test" principles — ask about their life, not your idea.

Domain Context

Customer interviews are one source in Stage 1 (Explore) of continuous discovery. Other sources: stakeholder interviews, usage analytics, data analytics, surveys, market trends, SEO/SEM analysis. The PM needs direct access to users, stakeholders, engineers, and designers — "without proxies." The Product Trio (PM + Designer + Engineer — Teresa Torres) should work together on discovery, not just the PM alone.

Context

You are preparing a customer interview script for research on $ARGUMENTS.

If the user provides files (personas, hypothesis lists, product briefs, or previous interview notes), read them first.

Instructions

  1. Clarify research objectives:
  • What specific questions does the team need answered?
  • What decisions will this research inform?
  • What assumptions need validation?
  1. Create the interview script with these sections:

Opening (2-3 min)

  • Introduce yourself and the purpose (learning, not selling)
  • Set expectations: "There are no right or wrong answers. We're here to learn from your experience."
  • Ask permission to record (if applicable)
  • Confirm time available

Warm-Up: Context & Background (5 min)

  • "Tell me about your role and what a typical day/week looks like."
  • "How long have you been doing [activity related to the product area]?"
  • Goal: Build rapport and understand their context

Core Exploration: Jobs to Be Done (15-20 min)

Current situation and behavior (past tense, specific instances):

  • "Walk me through the last time you [did the thing we're exploring]. What happened?"
  • "What tools or methods did you use?"
  • "How long did it take? Who else was involved?"

Pain points and frustrations (observe, don't lead):

  • "What was the hardest part about that?"
  • "If you could wave a magic wand, what would change?"
  • "What have you tried to solve this? What happened?"

Desired outcomes (their words, not yours):

  • "What does 'good' look like for you in this area?"
  • "How would you know if this was working well?"

Willingness to pay / priority (skin in the game):

  • "How much time/money do you currently spend on this?"
  • "Have you looked for a better solution? What did you find?"
  • "What would you give up to have this solved?"

Probing Techniques

Use these when you hit an interesting thread:

  • "Tell me more about that" — opens up any topic
  • "Why?" (asked gently, 2-3 times) — gets to root causes
  • "Can you give me a specific example?" — moves from opinions to facts
  • "What happened next?" — follows the story
  • "How did that make you feel?" — captures emotional intensity

The Mom Test Rules

  • Ask about their life, not your idea
  • Ask about the past, not the future ("Would you use X?" is useless)
  • Talk less, listen more — aim for 80/20 split
  • Never pitch during the interview
  • Look for strong emotions — they signal real pain or delight
  • Compliments are noise — "That sounds cool!" tells you nothing

Wrap-Up (3-5 min)

  • "Is there anything I didn't ask that you think is important?"
  • "Who else should I talk to about this?"
  • Thank them for their time
  • Share next steps (if any)
  1. Customize the script: Adapt questions to the specific product area, persona, and research objectives. Add or remove sections based on the interview length available.
  1. Include a note-taking template:
   Participant: [Name / ID]
   Date: [Date]
   Key Jobs: [What they're trying to accomplish]
   Current Solution: [What they use today]
   Biggest Pain: [Their #1 frustration]
   Desired Outcome: [What success looks like]
   Willingness to Pay: [How much they invest / would invest]
   Surprise Finding: [Something unexpected]
   Follow-up: [Next steps]

Save as markdown. Include both the script and the note-taking template.


Further Reading

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
phuryn
コミュニティ

strategy-red-team

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

1時間の導入数
4
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

ansoff-matrix

Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日