Why large-scale projects always overrun their deadlines — and why it's not a failure, but a structural law
Introduction: Understanding the delay affecting the critical path in megaprojects
After decades of observing megaprojects in engineering, infrastructure, energy, and IT, an uncomfortable truth consistently emerges:
Major projects do not fall behind due to poor management.
They are falling behind due to structural laws inherent in complex systems.
This phenomenon was formally recognised several decades ago by the Golub law:
No large project is ever completed on time, within budget, and with the initial scope.
Yet, the majority of organisations continue to plan as if this law did not exist.
This gap between expectations and reality is the root cause of delays, disputes, and financial exposure.
Understanding this is the first step to mastering procrastination – rather than being a victim of it.
The hidden structural mechanism behind project delay
Delay is not an isolated event.
It is the emergent result of five structural forces.
The divergence between planning and reality
Each project exists simultaneously in two parallel realities:
The narrative calendar: what the schedule foresees.
The timeline: what's really happening.
At the start of the project, these two timelines are aligned.
With time, they inevitably diverge.
This divergence constitutes the delay.
Not due to incompetence — but because uncertainty, interfaces and dependencies are dynamically evolving.
Planning does not eliminate uncertainty.
She deals with the consequences.
2. The complexity grows geometrically, non-linearly.
In the early stages, the complexity seems manageable.
But each modification introduces:
new interfaces
new dependencies
new constraints
new risks
The complexity accumulates geometrically.
That's why:
A poorly planned project takes three times longer than anticipated.
A well-planned project still takes twice as long.
It's not pessimism.
It is the application of physical laws to complex systems.
3. The 90 illusion %
Every experienced professional has observed this phenomenon:
A project is progressing smoothly up to 90 %.
Then it gets stuck at 90 % indefinitely.
Why?
Because the remaining 10 % focus on the most complex elements:
Systems integration
Validation and commissioning
interface resolution
hidden defects
Contractual reviews
These elements cannot be easily parallelised.
They reveal the true complexity of the system.
4. The principle of the invisible cause
Every delay has a root cause.
But the visible event is almost never the real cause.
The observable delay is the consequence.
The true origin lies upstream:
Sequencing failure
unrealistic hypotheses
underestimated interfaces
Scope evolution
Incomplete risk modelling
This is why delay forensics analysis is essential.
Not to note the delay.
But to trace its origin.
5. The structural law of project systems
Adding resources to a delayed project rarely speeds up its completion.
This often makes it worse.
As new resources increase:
the complexity of communication
the coordination charge
interface friction
Acceleration requires structural intervention.
Not a brute force answer.
The strategic teaching that most organisations ignore
The delay in itself is not the main risk.
Uncontrolled delay is the real risk.
Organisations fall into two categories:
Responsive organisations
They discover the delay after it has happened.
They suffer the contractual and financial consequences of this.
Strategic organisations
They detect the upstream delay.
They control its trajectory.
They protect their contractual position.
They transform delays into controlled and defensible results.
This distinction defines the success of projects at the highest level.
The real role of planning: not to predict, but to control
Planning is often misunderstood.
Its aim is not to predict the future with perfect accuracy.
That's impossible.
Its objective is to:
detect anomalies
quantify the impacts
identify root causes
protect contractual rights
to enable strategic decision-making
Planning is not a reporting function.
It's a strategic control function.
The emergence of delay as a strategic discipline
At the highest level of project execution, delay management becomes a specialised discipline:
Forensic planning
Delay analysis
Claims strategy
Calendar risk management
These functions do not remove the delay.
They turn delays into:
measurable phenomenon
controllable trajectory
Defensible contractual position
It's the difference between loss and strategic leverage.
Strategic conclusion
Delays are not anomalies.
These are structural properties of complex projects.
Organisations that ignore this reality will fall behind.
Those that understand it master it.
Those who dominate it gain a strategic advantage.
About the author
Mustapha Mokhlisse
Founder & President — ALVID Consulting
Delay & Claims Strategy | Forensic Schedule Analysis | Project Controls | Risk & Contractual Consulting
Supporting EPC contractors, operators, and infrastructure leaders in managing delays, protecting contractual rights, and securing project performance.