interview-script

Name: interview-script
Author: phuryn

1.8kinstalls2.5kforks

How to install interview-script?

phuryn/pm-skills/interview-script

$npx -y skills add phuryn/pm-skills --skill interview-script

Installs into the current project.

Summary

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 guid

Files · 1

View on GitHub

SKILL.md

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

People who liked this also viewed

6 picks

Type

interview-script

1.8kinstalls2.5kforks

View on GitHub

How to install interview-script?

phuryn/pm-skills/interview-script

$npx -y skills add phuryn/pm-skills --skill interview-script

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

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

People who liked this also viewed

6 picks

Type