The Cost of Late Technical Decisions
A technical decision that arrives three weeks late is rarely a three-week problem. The real cost is almost always larger, and it lands somewhere other than where the delay occurred.
Marcel Mbene, ChPP — Founder, Bold Leverage Ltd · 13 July 2026
Decisions do not sit in isolation
On a complex project, a single technical decision — a foundation detail, an equipment selection, a specification clarification — usually sits at the head of a chain of dependent activities: procurement, fabrication, site sequencing, commissioning planning. When the decision is late, everything downstream either waits or proceeds on an assumption that may later prove wrong.
This is why the cost of a late decision is so often disproportionate to the delay itself. Three weeks of indecision can translate into three months of programme impact once procurement lead times, contractor resequencing and rework are accounted for.
Why decisions become late in the first place
Late technical decisions are rarely caused by a lack of technical competence. More often, they stem from unclear ownership of the decision, insufficient information reaching the decision-maker in time, or a governance structure that requires too many approvals for a decision of that scale. In some cases, the decision is simply not recognised as urgent until the programme impact is already unavoidable.
The hidden cost: contractor pricing behaviour
There is a second, less visible cost. Contractors who have experienced repeated late decisions on a project begin to price and plan around the expectation of further delay — building float into programmes, holding back resources, or pricing risk into change requests. This defensive behaviour compounds the direct cost of the original delay and is difficult to reverse once established.
What reduces the risk
The most effective safeguard is not faster meetings but clearer visibility: a decision log that identifies, ahead of time, which technical decisions the programme depends on, who owns each one, and by what date it must be made to avoid downstream impact. This turns decision-making from a reactive process into a planned one, and makes it far easier to escalate a decision before it becomes a crisis rather than after.
Our view
Identifying and protecting the decisions that matter most is a core part of how we support clients through our project management and engineering consultancy services — the aim is to make sure the programme's critical decisions are visible long before they become critical delays.