The value lost for every week or month a decision or delivery slips: revenue not earned, savings not banked, options that expire. The price tag on "let's revisit this next quarter".
Organisations cost their projects and rarely cost their waiting. Cost of delay puts a number on the queue, which changes a surprising share of prioritisation arguments once someone runs the arithmetic.
Last reviewed 3 July 2026 · Free and ungated
Put both numbers, the cost of delay and the cost of deciding on thin evidence, to the Global Board before either wins by assertion.
Pressure-test this decisionCost of delay is the economic value an initiative forfeits per unit of time it is not live: the monthly benefit a delayed programme fails to produce, the sales a late launch concedes to a competitor, the premium a market window offers and then withdraws. Dividing an initiative's cost of delay by its duration gives a defensible way to sequence a portfolio: do the short, urgent, valuable work first, and know what the long items are costing while they wait.
Pricing time converts two familiar behaviours from free to expensive. Deferral: a decision parked for the next budget cycle acquires a visible price, which forces an honest comparison between deciding now on imperfect information and waiting for better. And queuing: when everything is priority one, cost of delay is the tiebreaker that does not depend on who argues loudest. The discipline cuts the other way too. Some delay buys information worth more than the delay costs, and a team that can price both is making a decision rather than reciting urgency.
Cost of delay inherits every weakness of the benefit estimate it is derived from, then adds urgency to it. A sponsor who inflates monthly value can present any governance step, any diligence, any challenge as recklessly expensive: "every week of review costs us €200,000" is a strong argument only if the underlying number survives contact. The tell is asymmetry: delay costs calculated to the week, delivery risks and adoption lags rounded to zero. Used that way, the metric stops informing the schedule and starts intimidating it.