Principle
Keep mitigation work out of the hidden buffer
Planned risk reduction is still planned work.
Before you use it
- Use when
- A known prevention task is buried inside contingency because it may not feel like 'real work.'
Keep this limit in mind
- Organizations use different accounting conventions; preserve the conceptual distinction even if financial labels differ.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Put deliberate prevention and mitigation activities—tests, rehearsals, backups, reviews, compatibility checks—into the base plan when you intend to perform them. Reserve contingency for uncertainty that remains. This keeps essential safety or quality work from being squeezed out to 'save buffer.'
An example
A canary run is scheduled as normal delivery work; extra repair time if the canary exposes unexpected defects sits in contingency.
Check your result
The base plan contains the risk-reduction work you actually intend to do.
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 readingKeep mitigation work out of the hidden buffer
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaBuild contingency from named residual risks
Evidence and sources
The Green Book distinguishes prevention or mitigation costs from contingency for risks that remain after mitigation.
Organizations may use different accounting labels; the useful distinction is planned work versus allowance for residual uncertainty.
The Green Book (2026) · Optimism bias and contingency
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.