Rajiv Gupta
September 9, 2026
The bust: Contingency is unquestionably necessary. But treating it as a planning tool admits the program has no reliable way to see what's forming inside it. That padding the cost and schedule budget is cheaper than building the visibility and proactive controls to avoid needing it. It's like keeping the white flag in your back-pocket even before entering the arena.
That's because contingency doesn't reduce risk. It funds the consequences of risk that was never detected early enough to address. The requirement that drifted unnoticed for three sprints. The design decision that contradicted an assumption two workstreams over. The adoption resistance nobody flagged until UAT.
None of those were unforeseeable. They were unseen because the program ran on status reports filtered through every layer between the work and the SteerCo, each one compressing and curating what it passed upward. Green on the outside, red on the inside. The contingency exists to absorb everything that picture missed.
A program that can see and proactively address drift as it forms, misalignment before it hardens, and adoption risk before it compounds doesn't need the same buffer. The contingency shrinks because the surprises do.
Axiamatic reads the program artifacts directly - requirements, design documents, meeting recordings, testing assets - identifying and preempting risks that would have dipped into the contingency bucket.
The programs that finish on budget and on scope didn't use their contingency to get there. They're the ones that never needed it.
