Interview Script

作者 phuryn8607e3b07781無授權條款26K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫3 週前更新

Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections. Follows The Mom Test principles — no leading questions, no pitching, focus on past behavior. Use when preparing for user interviews, creating interview guides, or planning discovery research.

AI 產生的概覽

產生結構化的客戶訪談腳本,包含 JTBD 問題、追問技巧與記錄範本。

功能
產出以 markdown 撰寫的訪談指南,分為開場、暖場、JTBD 核心探索、追問技巧與收尾等段落。它遵循 The Mom Test 原則,例如詢問過往行為、避免引導性問題與推銷。另附記錄範本,用來整理受訪者的任務、痛點、期望結果與後續追蹤。
適用情境
適合準備客戶或使用者訪談、撰寫訪談指南或規劃探索性研究時使用。適合需要針對特定產品領域、人物誌或研究目標客製可重複使用腳本的團隊。
執行需求
不需要腳本或特殊工具,僅以指令形式運作。代理可讀取使用者提供的檔案,如人物誌、假設清單、產品簡報或先前的訪談紀錄,輸出會存成 markdown。

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?
  2. 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)
  3. Customize the script: Adapt questions to the specific product area, persona, and research objectives. Add or remove sections based on the interview length available.

  4. 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

來源與署名

來源:phuryn/pm-skills位於pm-product-discovery/skills/interview-script提交8607e3b

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架