New to Claude Skills? Learn how to install them →

phuryn on GitHub

Customer Interview Script

Free

Craft structured interview scripts to uncover user insights.

by phuryn25.1k stars on phuryn/pm-skills
1 views
Updated Jul 3, 2026
Get this skill

Free · Opens the source repo

What Customer Interview Script does

The Customer Interview Script skill provides a structured approach to conducting user interviews, focusing on extracting genuine insights rather than opinions. It is grounded in the principles of 'The Mom Test', which emphasizes asking about users' past behaviors and experiences rather than pitching ideas or leading questions. This skill is particularly useful for product managers, designers, and researchers who need to prepare for effective user interviews that inform product development and discovery processes.

The skill guides users through the creation of an interview script that includes essential sections such as opening statements, warm-up questions, core exploration of the user's experiences, and a wrap-up. Each section is designed to build rapport, gather context, and probe deeper into the user's behavior and pain points. By following the outlined instructions, users can ensure that their interviews are focused, productive, and respectful of the participants' time and insights.

Additionally, the skill provides probing techniques to help interviewers delve deeper into interesting topics and encourages a conversational style that prioritizes listening over talking. It also includes a note-taking template to capture key findings during the interview, making it easier to analyze the data afterward. This structured approach is ideal for teams engaged in continuous discovery, ensuring that they gather valuable information directly from users without intermediaries.

Overall, this skill is an essential tool for anyone involved in user research, helping to create a framework that leads to actionable insights and better-informed product decisions.

When to use it

Use this skill when preparing for user interviews, creating interview guides, or planning discovery research to ensure effective data collection.

When not to use it

This skill may not be suitable for informal conversations or exploratory discussions that do not require a structured approach.

What you can build with it

Preparing for User Interviews

Use this skill to create a comprehensive interview script that ensures all relevant topics are covered during user interviews.

Conducting Discovery Research

Leverage the structured approach to gather insights directly from users, aiding in product development and feature prioritization.

Validating Assumptions

Utilize the script to test hypotheses and validate assumptions about user needs and pain points through direct engagement.

How to install Customer Interview Script

View source

1. Install with the skills CLI

npx skills add phuryn/pm-skills/interview-script --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by phuryn

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

Frequently asked questions about Customer Interview Script

Similar skills