discovery-process

## 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. ## 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 s...