interview-script

Solid

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 & Automation 11,758 stars 1390 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

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

Details

Author
phuryn
Repository
phuryn/pm-skills
Created
3 months ago
Last Updated
1 weeks ago
Language
N/A
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

interview

Activate for: user interview, interview guide, interview questions, discovery interview, research interview, customer interview, user research guide, interview script, how to interview users, what to ask users, interview protocol, research protocol, interview template, qualitative research, jobs to be done, JTBD, contextual inquiry, interview planning. NOT for: research synthesis from completed interviews (use official /synthesize-research), competitive analysis (use official /competitive-brief), survey design or quantitative research.

17 Updated 2 months ago
panaversity
AI & Automation Solid

discovery-interview-prep

Plan customer discovery interviews with the right goal, segment, constraints, and method. Use when preparing interviews for problem validation, churn research, or new product ideas.

4,637 Updated 1 weeks ago
deanpeters
AI & Automation Listed

conducting-user-interviews

Help plan and run customer interviews — question design, interview structure, research planning. Use BEFORE interviews to prepare. For debriefing AFTER a conversation, use discovery-debrief instead.

0 Updated today
Layneformalized225
AI & Automation Listed

user-interview

Prepare and conduct user interviews that extract truth, not validation. Use when asked to create an interview guide, prepare for user interviews, plan customer discovery, or talk to users. Built on The Mom Test and YC's Five Questions framework for startup customer development.

2 Updated today
AashutoshR2062
Code & Development Listed

pm-customer-interview-coach

Plan, critique, or stress-test a customer-discovery interview against the Mom Test rules. Use when the user is preparing an interview script, reviewing a transcript, debriefing what they "learned," or deciding what to do with a batch of customer conversations. Catches leading questions, fluff-inducing phrasing, compliments mistaken for data, premature zoom into a hypothesized problem, and missed commitment asks. Returns a question-by-question rewrite, a list of what was actually learned vs. imagined, and the next conversation to run.

0 Updated yesterday
kalyvask