Discovery method
How to Define Minimum Evidence Before Build
Minimum evidence before build is the evidence threshold a team must meet before committing delivery capacity. The threshold should match the decision’s cost, risk, reversibility, and strategic importance. Small reversible tests need less evidence; expensive or hard-to-reverse builds need stronger proof.
Key takeaways
Key takeaways
- Minimum evidence is a decision standard, not a universal checklist.
- Evidence strength should rise with cost, risk, and irreversibility.
- The Evidence Ladder helps teams classify whether signals are raw, repeated, validated, tested, or decision-ready.
- The threshold should be written before teams argue over a specific favorite idea.
The working sequence
- Define the build decision. Name what would be committed: team capacity, budget, roadmap slot, or technical dependency.
- Assess risk and reversibility. Decide how costly the decision would be to undo.
- Select the evidence level. Use the Evidence Ladder to choose the minimum acceptable confidence.
- List acceptable sources. Name which interviews, usage signals, tests, or operational data can count.
- Record the gate. Write the threshold, owner, and decision date before work moves to build.
What counts as enough evidence
Enough evidence means the available signals are strong enough for the size of commitment being made. A small prototype may only need repeated qualitative pain and a clear learning goal. A major platform build may need validated demand, tested response, operational feasibility, and explicit risk tolerance.
Decision guidance
Use minimum evidence gates before roadmap commitment, funding decisions, and major technical work. Keep the gate proportional. Over-demanding proof slows learning, while under-demanding proof turns weak signals into expensive commitments.
Common failure modes
- Universal checklist: using the same evidence bar for every decision.
- Late gate setting: defining the threshold after stakeholders are attached to a solution.
- Evidence volume bias: counting more inputs without judging quality.
- No source standard: accepting summary claims without source review.
Keep exploring
Internal links
FAQ
Frequently asked questions
What is minimum evidence before build?
It is the lowest acceptable evidence level required before a team commits delivery capacity to a product build.
Who sets the evidence threshold?
The accountable product decision owner should set it with input from research, data, design, engineering, and commercial stakeholders.
Can qualitative evidence be enough?
Yes, for some decisions. It must be specific, repeated, relevant, and proportionate to the commitment.
Next step