Generated banner for Interview Script
Generated logo for Interview Script

Interview Script

Pawel HurynCommunityCreated by Pawel Huryn

  • Skill
  • Content generator
  • Business and productivity
  • MIT
  • No issues found

From the author

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.
— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill helps product managers and researchers create effective interview scripts that prioritize gathering factual insights over validating personal ideas. By focusing on past behaviors, specific pain points, and actual outcomes, the generated scripts help teams avoid leading questions and common pitfalls. It provides a structured framework for the entire interview process, from warm-up to wrap-up, and includes a standardized note-taking template to ensure consistent data collection across discovery sessions.

What it does

  • Generates a structured interview script tailored to specific research objectives.
  • Incorporates Jobs to Be Done methodology to uncover user motivations.
  • Applies The Mom Test principles to minimize bias and avoid leading questions.
  • Provides a standardized note-taking template for consistent documentation.
  • Offers specific probing techniques to dig deeper into user stories.
  • Guides the user through setting clear research goals before drafting questions.

When to use it

  • When preparing for user discovery interviews.
  • When you need to validate assumptions about user pain points.
  • When planning research to inform product decisions.
  • When you want to ensure your interview questions focus on past behavior rather than hypothetical future actions.

Advantages

  • Reduces interviewer bias by enforcing non-leading question structures.
  • Ensures interviews remain focused on real-world experiences rather than opinions.
  • Standardizes the output of discovery research for easier analysis.
  • Helps build rapport while maintaining a professional research focus.
  • Encourages active listening and deeper exploration of user problems.

Usage examples

“Create an interview script for a new B2B SaaS tool that helps accountants manage tax filings.”
A structured interview guide including warm-up questions about their daily workflow, core exploration questions about their last tax filing experience, and a note-taking template.
“Draft an interview script to understand why users are churning from our mobile fitness app.”
A set of questions focused on the user's past exercise habits, their specific frustrations with the app, and what alternative solutions they have tried, adhering to The Mom Test.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/phuryn/interview-script/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip interview-script.zip -d .agents/skills

Documentation by Pawel Huryn

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

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Pawel Huryn
Publisher
Pawel Huryn (Community)
Source
phuryn/pm-skills · pm-product-discovery/skills/interview-script · commit 2a12295
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pawel Huryn or Pawel Huryn.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download interview-script.zip