discovery-process

这段内容是审核时保存的快照。外部来源才是完整且最新的版本。

---
name: discovery-process
argument-hint: "[problem hypothesis]"
description: Run a full discovery cycle from problem hypothesis to validated solution. Use when a team needs a structured path through framing, interviews, synthesis, and experiments.
intent: >-
  Guide product managers through a complete discovery cycle—from initial problem hypothesis to validated solution—by orchestrating problem framing, customer interviews, synthesis, and experimentation skills into a structured process. Use this to systematically explore problem spaces, validate assumptions, and build confidence before committing to full development—avoiding "build it and they will come" syndrome and ensuring you're solving real customer problems.
type: workflow
theme: discovery-research
best_for:
  - "Running a full discovery cycle from hypothesis to validated solution"
  - "Investigating a retention or churn problem systematically"
  - "Setting up continuous discovery as an ongoing practice"
scenarios:
  - "I have a hypothesis that B2B customers struggle with onboarding and want to validate it before building anything"
  - "Our activation rate dropped 15% this quarter and I need to run discovery to find out why"
estimated_time: "30-60 min"
---


## Purpose
Guide product managers through a complete discovery cycle—from initial problem hypothesis to validated solution—by orchestrating problem framing, customer interviews, synthesis, and experimentation skills into a structured process. Use this to systematically explore problem spaces, validate assumptions, and build confidence before committing to full development—avoiding "build it and they will come" syndrome and ensuring you're solving real customer problems.

This is not a one-time research project—it's a continuous discovery practice that runs in parallel with delivery, typically 1-2 discovery cycles per quarter.

## Input

**Works best with:** Your starting problem hypothesis — even a rough one.
**Also useful:** Prior research, customer access, timeline, and what decision the discovery must inform.

Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.

**Arriving empty-handed? That works too.** The workflow starts at problem framing and helps you construct the hypothesis first.

**Example invocation:** `Run discovery on this hypothesis: SMB admins abandon onboarding because the data-import step requires IT help they don't have.`

## Key Concepts

### What is the Discovery Process?

The discovery process (Teresa Torres, Marty Cagan) is a structured approach to exploring problem spaces and validating solutions before building. It consists of:

1. **Frame the Problem** — Define what you're investigating and why
2. **Conduct Research** — Gather qualitative and quantitative evidence
3. **Synthesize Insights** — Identify patterns, pain points, and opportunities
4. **Generate Solutions** — Explore multiple solution options
5. **Validate Solutions** — Test assumptions through experiments
6. **Decide & Document** — Commit to build, pivot, or kill

### Why This Works
- **De-risks product decisions:** Tests assumptions before expensive builds
- **Customer-centric:** Grounds decisions in real customer problems, not internal opinions
- **Iterative:** Builds confidence progressively through small experiments
- **Fast learning:** Discovers "no-go" signals early, saves wasted effort

### Anti-Patterns (What This Is NOT)
- **Not waterfall research:** Discovery runs continuously, not once before dev
- **Not user testing:** Discovery validates problems; testing validates solutions
- **Not a substitute for shipping:** Discovery informs delivery, doesn't replace it

### When to Use This
- Exploring new product/feature areas
- Investigating retention or churn problems
- Validating strategic initiatives before roadmap commitment
- Continuous discovery (weekly cust