Interview script skill
Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections.
by phuryn·MIT license·★ 26,557 Stars on the repo·GitHub ↗
npx degit phuryn/pm-skills/pm-product-discovery/skills/interview-script#main ~/.claude/skills/interview-scriptChecked ·commit main
Files of Interview script
Show the full text106 lines
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
Clarify research objectives:
- What specific questions does the team need answered?
- What decisions will this research inform?
- What assumptions need validation?
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)
Customize the script: Adapt questions to the specific product area, persona, and research objectives. Add or remove sections based on the interview length available.
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
| 1 | |
| 2 | name interview-script |
| 3 | description "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." |
| 4 | |
| 5 | |
| 6 | ## Customer Interview Script |
| 7 | |
| 8 | Create a structured interview script that surfaces real insights, not just opinions. Follows "The Mom Test" principles — ask about their life, not your idea. |
| 9 | |
| 10 | ### Domain Context |
| 11 | |
| 12 | 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. |
| 13 | |
| 14 | ### Context |
| 15 | |
| 16 | You are preparing a customer interview script for research on **$ARGUMENTS**. |
| 17 | |
| 18 | If the user provides files (personas, hypothesis lists, product briefs, or previous interview notes), read them first. |
| 19 | |
| 20 | ### Instructions |
| 21 | |
| 22 | **Clarify research objectives**: |
| 23 | What specific questions does the team need answered? |
| 24 | What decisions will this research inform? |
| 25 | What assumptions need validation? |
| 26 | |
| 27 | **Create the interview script** with these sections: |
| 28 | |
| 29 | ### Opening (2-3 min) |
| 30 | Introduce yourself and the purpose (learning, not selling) |
| 31 | Set expectations: "There are no right or wrong answers. We're here to learn from your experience." |
| 32 | Ask permission to record (if applicable) |
| 33 | Confirm time available |
| 34 | |
| 35 | ### Warm-Up: Context & Background (5 min) |
| 36 | "Tell me about your role and what a typical day/week looks like." |
| 37 | "How long have you been doing [activity related to the product area]?" |
| 38 | Goal: Build rapport and understand their context |
| 39 | |
| 40 | ### Core Exploration: Jobs to Be Done (15-20 min) |
| 41 | |
| 42 | **Current situation and behavior** (past tense, specific instances): |
| 43 | "Walk me through the last time you [did the thing we're exploring]. What happened?" |
| 44 | "What tools or methods did you use?" |
| 45 | "How long did it take? Who else was involved?" |
| 46 | |
| 47 | **Pain points and frustrations** (observe, don't lead): |
| 48 | "What was the hardest part about that?" |
| 49 | "If you could wave a magic wand, what would change?" |
| 50 | "What have you tried to solve this? What happened?" |
| 51 | |
| 52 | **Desired outcomes** (their words, not yours): |
| 53 | "What does 'good' look like for you in this area?" |
| 54 | "How would you know if this was working well?" |
| 55 | |
| 56 | **Willingness to pay / priority** (skin in the game): |
| 57 | "How much time/money do you currently spend on this?" |
| 58 | "Have you looked for a better solution? What did you find?" |
| 59 | "What would you give up to have this solved?" |
| 60 | |
| 61 | ### Probing Techniques |
| 62 | Use these when you hit an interesting thread: |
| 63 | **"Tell me more about that"** — opens up any topic |
| 64 | **"Why?"** (asked gently, 2-3 times) — gets to root causes |
| 65 | **"Can you give me a specific example?"** — moves from opinions to facts |
| 66 | **"What happened next?"** — follows the story |
| 67 | **"How did that make you feel?"** — captures emotional intensity |
| 68 | |
| 69 | ### The Mom Test Rules |
| 70 | Ask about **their life**, not your idea |
| 71 | Ask about **the past**, not the future ("Would you use X?" is useless) |
| 72 | **Talk less, listen more** — aim for 80/20 split |
| 73 | **Never pitch** during the interview |
| 74 | Look for **strong emotions** — they signal real pain or delight |
| 75 | **Compliments are noise** — "That sounds cool!" tells you nothing |
| 76 | |
| 77 | ### Wrap-Up (3-5 min) |
| 78 | "Is there anything I didn't ask that you think is important?" |
| 79 | "Who else should I talk to about this?" |
| 80 | Thank them for their time |
| 81 | Share next steps (if any) |
| 82 | |
| 83 | **Customize the script**: Adapt questions to the specific product area, persona, and research objectives. Add or remove sections based on the interview length available. |
| 84 | |
| 85 | **Include a note-taking template**: |
| 86 | |
| 87 | Participant: [Name / ID] |
| 88 | Date: [Date] |
| 89 | Key Jobs: [What they're trying to accomplish] |
| 90 | Current Solution: [What they use today] |
| 91 | Biggest Pain: [Their #1 frustration] |
| 92 | Desired Outcome: [What success looks like] |
| 93 | Willingness to Pay: [How much they invest / would invest] |
| 94 | Surprise Finding: [Something unexpected] |
| 95 | Follow-up: [Next steps] |
| 96 | |
| 97 | |
| 98 | Save as markdown. Include both the script and the note-taking template. |
| 99 | |
| 100 | |
| 101 | |
| 102 | ### Further Reading |
| 103 | |
| 104 | [User Interviews: The Ultimate Guide to Research Interviews] |
| 105 | [Continuous Product Discovery Masterclass (CPDM)] (video course) |
| 106 |
Discussion
Alternatives
Browse more free Claude skills or everything in Product.