Why Major Projects Always Run Late — and Why This Is Not a Failure, but a Structural Law
Introduction : Comprendre le retard affectant le chemin critique dans les mégaprojets
After decades of observation across engineering, infrastructure, energy, and IT megaprojects, one uncomfortable truth consistently emerges:
Major projects do not run late because of bad management.
They run late because of structural laws inherent to complex systems.
This phenomenon was formally recognized decades ago by Golub’s Law
No large project is ever completed on time, within budget, and with the original scope.
Yet most organizations still plan as if this law does not exist.
This disconnect between expectation and reality is the root cause of delay, dispute, and financial exposure.
Understanding this is the first step toward mastering delay — rather than suffering from it.
The Hidden Structural Mechanism Behind Project Delay
Project delay is not a single event.
It is the emergent result of five structural forces.
1. The Planning-Reality Divergence
Every project exists simultaneously in two parallel realities:
The narrative timeline What the plan says will happen.
The temporal timeline What actually happens.
At project start, these two timelines are aligned.
Over time, they inevitably diverge.
This divergence is delay.
Not because of incompetence — but because uncertainty, interfaces, and dependencies evolve dynamically.
The planning function does not eliminate uncertainty.
It manages its consequences.
2. Complexity Grows Geometrically, Not Linearly
At early project stages, complexity appears manageable.
But each change introduces:
new interfaces
new dependencies
new constraints
new risks
Complexity compounds geometrically.
This is why:
A poorly planned project takes three times longer than expected.
A well-planned project still takes twice as long.
This is not pessimism.
It is physics applied to systems.
3. The 90% Completion Illusion
Every experienced project professional has seen this phenomenon:
A project progresses smoothly to 90%.
Then remains at 90% indefinitely.
Why?
Because the final 10% contains the most difficult elements:
system integration
validation and commissioning
interface resolution
latent defects
contractual verification
These elements cannot be parallelized easily.
They expose the true complexity of the system.
4. The Invisible Cause Principle
Every delay has a root cause.
But the visible delay event is rarely the actual cause.
The visible delay is the consequence.
The true cause exists upstream:
flawed sequencing
unrealistic assumptions
underestimated interfaces
scope evolution
incomplete risk modeling
This is why forensic delay analysis is essential.
Not to observe delay.
But to trace its origin.
5. The Structural Law of Project Systems
Adding resources to a late project rarely accelerates completion.
It often makes it worse.
Because new resources increase:
communication complexity
coordination overhead
interface friction
Acceleration requires structural intervention.
Not brute force.
The Critical Strategic Insight Most Organizations Miss
Delay itself is not the primary risk.
Uncontrolled delay is the risk.
Organizations fall into two categories:
Reactive organizations
They detect delay early. They control its trajectory.
They protect their contractual position. They convert delay into a controlled, defensible outcome.
This distinction defines project success at the highest level.
Strategic organizations
They detect delay early.
They control its trajectory.
They protect their contractual position.
They convert delay into a controlled, defensible outcome.
This distinction defines project success at the highest level.
The True Role of Planning Is Not Prediction — It Is Control
Planning is often misunderstood.
Its purpose is not to predict the future with perfect accuracy.
That is impossible.
Its purpose is to:
detect deviation
quantify impact
identify root cause
protect contractual entitlement
enable strategic decision-making
Planning is not a reporting function.
It is a strategic control function.
The Emergence of Delay as a Strategic Discipline
At the highest level of project execution, delay management becomes a specialized discipline:
Forensic Planning
Delay Analysis
Claims Strategy
Schedule Risk Control
These functions do not eliminate delay.
They transform delay into:
a measurable phenomenon
a controllable trajectory
a defensible contractual position
This is the difference between loss and leverage.
Strategic Conclusio
Delays are not anomalies.
They are structural properties of complex projects.
Organizations that ignore this reality suffer delay.
Organizations that understand this reality control delay.
Organizations that master this reality gain strategic advantage.
About the Author
Mustapha Mokhlisse
Founder & President — ALVID Consulting
Delay & Claims Strategy | Forensic Schedule Analysis | Project Controls | Risk & Contractual Advisory
Supporting EPC contractors, operators, and infrastructure leaders in controlling delay, protecting entitlement, and securing project outcomes
