discovery-interview-prep
Structured discovery interview planning with adaptive methodology selection based on research goals and constraints.
- Guides product managers through four adaptive questions to define research goals, target segments, access constraints, and interview methodology
- Generates tailored interview frameworks with 5+ context-specific questions, follow-ups, and bias-avoidance guidance for each methodology (Mom Test, Jobs-to-be-Done, switch interviews, timeline mapping)
- Includes opening/closing scripts, success criteria focused on specific stories and pattern detection across 5+ interviews, and recruitment logistics
- Highlights common pitfalls (leading questions, hypothetical asks, wrong audience, premature conclusions) with concrete fixes
Purpose
Guide product managers through preparing for customer discovery interviews by asking adaptive questions about research goals, customer segments, constraints, and methodologies. Use this to design effective interview plans, craft targeted questions, avoid common biases, and maximize learning from limited customer access—ensuring discovery interviews yield actionable insights rather than confirmation bias or surface-level feedback.
This is not a script generator—it's a strategic prep process that outputs a tailored interview plan with methodology, question framework, and success criteria.
Key Concepts
The Discovery Interview Prep Flow
An interactive process that:
- Gathers product/problem context (marketing materials, assumptions)
- Defines research goals (what you're trying to learn)
- Identifies target customer segment and access constraints
- Recommends interview methodology (Jobs-to-be-Done, problem validation, switch interviews, etc.)
- Generates interview framework with questions, biases to avoid, and success metrics
Why This Works
- Goal-driven: Aligns interview approach to what you need to learn
- Adaptive: Adjusts methodology based on product stage (idea vs. existing product) and access constraints
More from deanpeters/product-manager-skills
prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
1.7Kuser-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
1.7Kroadmap-planning
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
1.5Kcompany-research
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
1.3Kproduct-strategy-session
Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.
1.2Kprioritization-advisor
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
1.1K