Protocol
Attach confidence to the evidence, not to your tone
Confidence should describe what is known, not how strongly the estimator speaks.
Before you use it
- Use when
- A date is delivered confidently even though key inputs are still unknown.
Keep this limit in mind
- Ordinal confidence labels are editorial aids, not calibrated probabilities unless the team has defined and tested them.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
State the evidence maturity behind the forecast: known scope, validated dependencies, available historical analogues and unresolved unknowns. Use a wider range or lower confidence when important inputs are still speculative, then narrow it when real uncertainty has been removed.
Steps
- A confidence statement names the evidence that supports it and what is still missing.
An example
A draft integration estimate stays wide until the external API and sample payload are tested.
Check your result
A confidence statement names the evidence that supports it and what is still missing.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingAttach confidence to the evidence, not to your tone
Evidence and sources
IPA guidance notes that uncertainty and estimate range depend on the maturity and variability of input data, so estimates should evolve as design and evidence mature.
A later estimate can still be wrong; maturity narrows uncertainty only when real information has improved.
Cost Estimating Guidance · Estimate maturity and range
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.