You leave with
- A problem thesis and evidence plan
- Explicit pivot, persevere, or stop gates
- A sequenced build that matches the evidence
Discipline
Product
discovery
Structured validation before build: hypotheses, evidence thresholds, and sequencing. Used when Discovery shows the team is building around an untested constraint.
The constraint
When this discipline is useful
The team is choosing what to build without a shared view of the problem, the evidence required, or when to stop.
Discovery recommends this discipline when the next useful work is to test a hypothesis, not to expand the product.
What the work produces
Outputs and boundaries
This is not
- A workshop that produces slides and no decision
- A backlog groomed without evidence thresholds
- A prototype used to delay a hard no
How we apply it
Operating principles
Name the decision
Discovery work is only useful if it changes a specific next move the team is about to make.
Set the evidence bar first
Agree what would confirm or kill the hypothesis before gathering more interviews.
Stopping is a feature
A clean stop prevents sunk-cost drift and keeps capital on the constraint that matters.
Further reading
A related practice note
Book a call before you add more work
Bring the constraint. We will say whether this discipline belongs in the next engagement, or whether to pause.