Discovery Interview Prep

Discovery Interview Prep

Plan customer discovery interviews with the right goal, segment, constraints, and method. Use when preparing interviews for problem validation,

Category: development Source: deanpeters/Product-Manager-Skills

What Is This?

Overview

Discovery Interview Prep is a structured skill designed to guide product managers through the process of planning effective customer discovery interviews. It helps teams define clear research goals, identify the right customer segments, account for practical constraints, and select appropriate interview methodologies before a single conversation takes place. The result is a focused interview plan that produces reliable, actionable insights rather than vague or misleading data.

The skill draws on established product research practices to walk practitioners through adaptive questions at each stage of preparation. Whether you are validating a problem hypothesis, investigating churn patterns, or exploring opportunities for a new product idea, the framework ensures your interviews are purposeful and well-structured from the start.

Poor interview preparation is one of the most common reasons discovery research fails to deliver value. Teams often enter conversations without a defined goal, speak to the wrong customers, or ask leading questions that confirm existing assumptions. This skill addresses those failure points directly by building rigor into the planning phase.

Who Should Use This

  • Product managers preparing for problem validation research on a new feature or product area
  • UX researchers who need a repeatable planning framework for customer interviews
  • Startup founders conducting early-stage discovery before committing to a product direction
  • Product teams investigating reasons behind customer churn or declining engagement
  • Growth and strategy teams exploring new market segments or unmet customer needs
  • Junior product managers who want structured guidance on interview methodology selection

Why Use It?

Problems It Solves

  • Interviews conducted without a clear goal produce unfocused conversations that are difficult to analyze or act on
  • Speaking to the wrong customer segment generates misleading signals that can derail product decisions
  • Leading or poorly constructed questions introduce bias and cause teams to validate assumptions rather than test them
  • Teams frequently skip methodology selection, defaulting to whatever format feels familiar rather than what fits the research question
  • Without documented constraints such as timeline, budget, or access limitations, interview plans are often unrealistic to execute

Core Highlights

  • Guides goal definition before any other planning step begins
  • Prompts explicit identification of the target customer segment and recruitment criteria
  • Surfaces practical constraints early so the plan remains executable
  • Supports multiple research contexts including problem validation, churn research, and new product exploration
  • Helps craft targeted, open-ended questions that minimize interviewer bias
  • Adapts to different interview methodologies based on the research goal
  • Produces a structured interview plan that can be shared across the team
  • Reduces the time spent iterating on interview guides by front-loading key decisions

How to Use It?

Basic Usage

Start by defining the core research goal in a single sentence. A well-formed goal follows this pattern:

Goal: Understand why [segment] struggles with [problem] so we can [intended outcome].

Example: Understand why small business owners abandon onboarding after day three
so we can identify the specific friction points blocking activation.

Next, document the target segment and recruitment criteria:

Segment: Small business owners with fewer than 10 employees
Criteria: Signed up in the last 90 days, did not complete onboarding step 4
Sample size: 8 to 12 participants

Specific Scenarios

Problem Validation: When testing whether a problem is real and significant, structure your questions around frequency, impact, and current workarounds rather than asking whether the participant wants your proposed solution.

Churn Research: When investigating why customers leave, focus on the timeline of their experience. Ask participants to walk you through the last time they used the product and what prompted their decision to stop.

Real-World Examples

A product team preparing to build a scheduling feature first ran discovery interviews using this framework. They discovered that the actual problem was not scheduling complexity but notification overload, which redirected the entire roadmap.

A startup founder used the skill to prepare interviews for a B2B tool and identified that their assumed primary segment, operations managers, was not the actual decision-maker. Procurement leads held the budget authority.

Important Notes

Requirements

  • A defined product area or research question must exist before using this skill effectively
  • Access to at least one representative customer or potential customer for piloting the guide
  • Basic familiarity with qualitative research concepts such as open-ended questioning and confirmation bias
  • A method for recording or documenting interview sessions, whether notes, transcripts, or recordings with participant consent