discovery-process

Discovery Process: A Complete Product Discovery Workflow from Problem Hypothesis to Validation Plan

Skill Overview

Discovery Process is a six-stage product discovery workflow designed for product managers. It takes you step by step from an initial problem hypothesis to a validated solution. Through problem framing, user interviews, insight synthesis, and experiment validation, it helps prevent blind development based on the assumption that “if we build it, people will use it.”

Use Cases

Validating a problem hypothesis: For example, if you hypothesize that “B2B customers abandon onboarding because they lack IT support,” systematically validate whether the problem actually exists before writing a single line of code.

Investigating changes in retention and activation metrics: If the activation rate drops by 15% this quarter, use the discovery process to identify the true cause instead of instinctively changing features.

Establishing an ongoing discovery practice: Turn weekly customer interviews into a team habit, run product discovery in parallel with delivery, and continuously recalibrate product direction.

Core Features

A structured six-stage process: Problem framing → Research planning → Research execution → Insight synthesis → Solution generation and validation → Decision-making and documentation. Each stage has clear objectives, activities, deliverables, and decision points, such as criteria for determining whether interviews have reached saturation.

Orchestration of 10+ specialized sub-skills: Built-in orchestration for skills including the problem framing canvas, problem statements, discovery interview preparation (Mom Test-style questioning), opportunity solution trees (OSTs), Lean UX canvases, and epic hypotheses, covering a complete 2–4 week discovery cycle.

Actionable decision outputs: Based on problem validation and experiment results, produce GO / PIVOT / KILL conclusions. If the decision is GO, continue by generating epic hypotheses and a structured PRD, with support for presenting discovery findings to management in a 30-minute briefing.

Frequently Asked Questions

How long does it take to complete a full discovery cycle?

The guided session itself takes approximately 30–60 minutes to plan the process, but a complete discovery cycle typically takes 2–4 weeks: about 3 weeks for the fast track (5 interviews + 1 experiment), 4 weeks for the standard approach (7–10 interviews + 1–2 experiments), and 6–8 weeks for more thorough validation. It is recommended to keep discovery within 3–4 weeks to avoid analysis paralysis.

How many users need to be interviewed?

Each discovery cycle should include interviews with 5–10 customers. The stopping criterion is “saturation”: once the same pain point has appeared in three or more interviews and no new insights are emerging, you can move to the synthesis stage. Following Teresa Torres’s continuous discovery habits, maintain a steady cadence of one customer interview per week.

What is the difference between product discovery and user testing?

The discovery process validates whether “the problem genuinely exists,” while user testing validates whether “the solution is easy to use.” The two cannot substitute for each other. Discovery Process is also not suitable in three situations: when the problem is already well understood (move directly to execution), when stakeholders have already agreed on a solution (resolve alignment first), or for simple bug fixes and technical debt (discovery is unnecessary).