domains / families / business / discovery-process
discovery-process
separate
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.
When to use
- 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 thi…
When not to use
- For well-understood problems (move to execution)
- When stakeholders have already committed to a solution (address alignment first)
- For tactical bug fixes or technical debt (no discovery needed)
- Waterfall research
- User testing
- Substitute for shipping
Skill page
Source