Customer Interview Script

Interview script

by phuryn · MIT license · ★ 26,557 on GitHub · updated Sep 14

Interview script cover

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.

---
name: interview-script
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."
---

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

Overview

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

Manual install (npx, ZIP)
Claude Codenpx skills add phuryn/pm-skills --skill interview-script -g -a claude-code
Claude Code (degit)npx degit phuryn/pm-skills/pm-product-discovery/skills/interview-script#main ~/.claude/skills/interview-script
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md4.7 KB
Read SKILL.md here
phuryn/main1 file shown
SKILL.md
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
  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
1---
2name: interview-script
3description: "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 
8Create 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 
12Customer 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 
16You are preparing a customer interview script for research on **$ARGUMENTS**.
17 
18If the user provides files (personas, hypothesis lists, product briefs, or previous interview notes), read them first.
19 
20### Instructions
21 
221. **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 
272. **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 
833. **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 
854. **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 
98Save 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](https://www.productcompass.pm/p/interviewing-customers-the-ultimate)
105- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
106 
View all files on GitHub →

Details

Updated
Sep 14, 2026
License
MIT
Stars on the repo
★ 26,557
Checked
Source
phuryn/pm-skills ↗
Creator
phuryn · 69 listings
View creator

Similar skills

See all →
Skill360 Feedback Surveymohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub starsSkillExpert Knowledge Extractorinhouseseo/superseo-skills · by inhouseseoUse when extracting first-party expertise from a subject-matter expert before writing content. Produces a knowledge document of contrarian takes, specific examples, and surprising outcomes that AI can't fabricate.★ 353 GitHub starsSkillCreator Persona ResearcherTheMattBerman/scrollclaw · by TheMattBermanStart of the UGC pipeline for persona research, creator profiles, format selection, and scriptwriting. Use when the user is clearly asking for messaging work rather than broad full-pipeline orchestration.★ 71 GitHub starsSkillQuestionnaire Generatormattpocock/skills · by mattpocockTell us who you need answers from and what you're missing; get back a clean form you send them to fill in.★ 267k GitHub starsSkillIntent Interview Assistantaddyosmani/agent-skills · by addyosmaniExtracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.★ 98.7k GitHub starsSkillBehavioral Science for Marketingcoreyhaines31/marketingskills · by coreyhaines31When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context. For applying psychology to specific pages, see cro; for pricing tactics, see pricing; for copy framing, see copywriting.★ 51.1k GitHub stars

More from phuryn

SkillA/B Test Analyzerphuryn/pm-skills · by phurynAnalyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.★ 26.6k GitHub starsSkillFeature Request Prioritizerphuryn/pm-skills · by phurynAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.★ 26.6k GitHub starsSkillAnsoff Matrix Generatorphuryn/pm-skills · by phurynGenerate 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.★ 26.6k GitHub starsSkillAI Text Humanizerphuryn/work-humanizer · by phurynEdit AI-sounding text so it reads like a careful person wrote it, without changing what it says or commits to. Built for work writing where the wording matters: sales and marketing copy, support replies, HR and legal letters, emails, docs, release notes, posts, landing pages. Two modes. Rewrite: edit the text you are given. Interview: when a draft is AI-composed and thin, ask the writer 3-5 sharp questions and build the piece from their answers, in their words. Also writes from the writer's own notes or a voice-memo transcript. Calibrated on measured differences between human and AI writing.★ 110 GitHub starsSkillMarket Segment Identifierphuryn/pm-skills · by phurynIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.★ 26.6k GitHub starsSkillProduct Experiment Designerphuryn/pm-skills · by phurynDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.★ 26.6k GitHub stars