Hypothesis-driven development (build, measure, learn)
Treat each key product assumption as a hypothesis: state it with a measurable success signal, test it with the smallest experiment and decide from the result.
- Use when
- High uncertainty about value: a new product, a new market or unproven demand.
- Avoid when
- Clear, known needs where experiments only delay delivery.
- Source
- Eric Ries (2011)
- Level
- B · established practice
For agents · MCP
explain_node({ "id": "p.hypothesis_driven_dev" })