Putting a price on delayed execution

Updated 17 October 2026

A programme can remain close to its approved budget while the business loses money waiting for it. The project report records expenditure. The deferred savings or missed sales opportunity may sit elsewhere, if anyone records them at all.

Leadership needs a view of the economic consequence of waiting. This should support a decision about recovery, scope or cancellation. A large headline figure without traceable assumptions creates a different reporting problem.

Calculate the consequence of this delay

Begin with the benefit that cannot be realised until a specific outcome is delivered. Establish when that benefit was expected to start, how it would arise and which costs remain while the organisation waits.

Consider a purely illustrative system replacement. The investment case assumes that the old platform can be retired after launch, avoiding AED 80,000 of monthly external operating costs. An eight week delay, treated here as two months for a simple estimate, could defer AED 160,000 of those savings.

Assume the delay also requires two months of temporary support at AED 30,000 a month, additional to those operating costs. The estimated consequence is then AED 220,000 before any other effects. Finance should confirm the assumptions and check that the support cost has not already been counted elsewhere.

The estimate changes if contracts can be cancelled only annually, if the old platform must run in parallel after launch or if savings were never achievable in full. Those details belong beside the number.

Separate cash from opportunity

Extra supplier invoices affect cash. Staff time spent repeating work uses capacity. A deferred product launch may affect future revenue, but the lost contribution depends on demand, margin and whether sales are lost permanently or merely delayed.

Keep these effects visible separately. Avoid valuing every hour at a charge-out rate or treating all deferred revenue as a permanent loss. Ranges are often more useful than false precision when the evidence is incomplete.

Also check relationships between initiatives. If several projects depend on the same platform, count a shared benefit once. Adding their delay estimates can otherwise produce an impressive total with little economic meaning.

Compare recovery options on future value

An acceleration proposal should show the cost of intervention and the benefit expected from delivering earlier. It also needs to explain any additional risk, including reduced testing or operational pressure.

Paying AED 100,000 to recover a month may make sense if it protects a well-supported benefit worth more than that. It may be poor value if the next dependency will prevent launch anyway. The whole path to the benefit matters.

Sometimes a smaller release, a temporary workaround or an orderly stop has a better economic case than accelerating the original plan. Ask for those options before approving more resources.

Put the estimate where decisions happen

For a material delay, the executive report should show the reason, estimated economic consequence, confidence in the estimate and available response. Name the decision owner and the latest useful decision date.

Start with one delayed initiative whose economics can be checked. A defensible estimate for that decision is more useful than a portfolio total built on assumptions nobody has tested.