The Cost of Delay Framework: Why Slow Decisions Are the Most Expensive Ones

In most organisations, the cost of a delayed program is calculated in budget overrun: how much more was spent than planned. This is the wrong metric. Budget overrun captures the cost of doing the work slowly. It doesn't capture the cost of the business value that wasn't delivered while the work was delayed.

Cost of Delay (CoD) is the framework that makes that second cost visible. For every unit of time this program is delayed, what is the economic consequence to the organisation?

Why Cost of Delay matters

Consider a program sitting in a prioritisation queue for two months while leadership decides whether to approve the business case. The standard framing: "we haven't spent anything yet, so there's no cost." The Cost of Delay framing: "for every week this program doesn't start, we're forgoing X in revenue, cost savings, or risk reduction. At eight weeks of delay, that's 8X."

Suddenly the two months of committee review looks very different. It might cost more than the program was expected to deliver in its first year.

The four types of Cost of Delay

Standard (linear)

Revenue or value accruing at a roughly constant rate. A billing system upgrade generating consistent value for every month in production has linear CoD. Every month of delay has the same cost.

Urgent (fixed date)

Near-zero CoD until a specific date, then catastrophic. A regulatory compliance program with a legislative deadline has essentially zero CoD until that date — then infinite cost if the deadline is missed.

Perishable (declining value)

A window of opportunity that closes over time. A market entry program that needs to beat a competitor to a segment has high CoD now that declines as the window closes.

Intangible

Real but difficult to quantify directly — customer experience improvements, employee productivity, capability building. These are the most commonly ignored in portfolio prioritisation and often the most consequential.

How to apply Cost of Delay in practice

1. For each program, identify what business value it generates when live
2. Estimate the value per week of that benefit stream
3. Determine the CoD profile: linear, fixed-date, perishable, or intangible
4. Use the CoD estimate to weight prioritisation decisions alongside capacity and effort

The decision acceleration effect

One of the most powerful applications of CoD is making the cost of slow decisions explicit. When a business case approval has been sitting with a committee for six weeks, expressing the CoD of that delay in economic terms — "this committee is currently consuming $240,000 of foregone value with each week of deliberation" — changes the urgency of the decision in a way that abstract "strategic importance" language never does.