The 80/50 Problem: Why Large Industrial Projects Overrun — and Where the Risk Actually Sits

Capital Projects

McKinsey’s review of more than 300 billion-dollar-plus projects found cost overruns averaging close to 80% and schedule slips near 50%. The evidence points not to capital, but to the approval interface — the part of a project leadership is least equipped to manage.

Altius Ventures · Policy & Regulatory Practice — 7 min read · As of June 2026

There is a comfortable story that gets told about why big industrial projects go wrong: the market turned, the technology was immature, the budget was too thin. It is comfortable because each of those causes is external — a matter of luck or capital. The data tells a less comfortable story.

In one of the most-cited reviews of its kind, McKinsey examined more than 300 projects each worth over a billion dollars and found average cost overruns approaching 80% and schedule delays near 50% (McKinsey & Company, “Don’t cancel or coddle at-risk capital projects — challenge them”). These are not marginal misses. A project that overruns its budget by four-fifths and its timeline by half is a project whose economics have been fundamentally rewritten between sanction and start-up.

What is striking is how little of that overrun traces to the things leadership instinctively worries about.

The delay sits before the first brick

When researchers look closely at where in a project’s life the slippage accumulates, the answer is consistent: a disproportionate share happens early, in the approval and evaluation phases, before construction has properly begun.

A 2025 study by the CoST – Infrastructure Transparency Initiative, conducted with the World Bank and the Government of Japan, examined 480 projects across three continents and identified approval-stage and inter-departmental approval delays as leading drivers of schedule slippage (CoST, May 2025). The World Bank’s own analysis of procurement and approval delays in infrastructure points the same way (World Bank, “Drivers of Delays in Procurement of Infrastructure Projects”). And the broader academic literature on megaprojects — most associated with Bent Flyvbjerg’s work, including a 258-project transport study showing average overruns near 28% — has long held that the seeds of overrun are planted in the front end, not the build.

The mechanism is intuitive once stated. Capital is fungible and can be raised. Engineering problems are solvable with engineering. But a project that cannot break ground because one of a dozen statutory clearances is outstanding is simply stopped — and every week it is stopped, fixed costs accrue, financing carries, contractors idle, and the market the project was sized for keeps moving. The approval interface is where time leaks, and time is the overrun.

The capital is ready. McKinsey estimates roughly US$24 trillion of investment is positioned for heavy-industrial projects over five years — with India accounting for around 8% of it. The constraint on that capital reaching the ground is rarely the capital itself.

Why this is structurally hard for leadership

Here is the uncomfortable corollary. The approval interface is precisely the part of a project that a chief executive, a board or a project-management office is least equipped to run.

A leadership team is built to make capital-allocation decisions, manage construction risk, hire, and commission. It is not built to track which of fourteen separate regulators is next in sequence, what each one’s current documentation standard is, why a consent application gets returned, or how a transition clause in a recently amended notification affects a filing. That knowledge is not generalist knowledge; it is specialist, jurisdiction-specific and perishable — it changes with every circular and office memorandum.

So the work either gets pushed down to people without the standing to resolve it, or it pulls senior leadership into a regulatory maze that consumes the management bandwidth a capital project most needs at exactly the wrong moment. Either way, the front-end risk — the risk that the data says matters most — goes unmanaged by design.

The discipline that prevents it

The antidote is not effort. Projects that overrun are rarely under-resourced; many are staffed by capable people working hard on the wrong sequence. The antidote is sequence discipline: knowing the full set of authorities a facility must clear, understanding the dependencies between them, and approaching them in an order that prevents one approval from invalidating the documentation of another.

A factory in Maharashtra, for instance, must move through land allotment, environmental consent, factory licensing, hazardous-materials clearance, fire approval and a power connection — and the order is not arbitrary. Consent to Operate cannot precede the building it certifies; a factory licence depends on documentation that other clearances generate. Get the sequence right and the approvals stack; get it wrong and you pay for the same step twice, in money and in months. (We map that full sequence in a companion report, One Factory, Fourteen Authorities.)

How Altius works this

Altius Ventures owns the front-end interface — the approval, compliance and incentive surface where the megaproject data says overrun risk actually concentrates. We sequence the authorities a facility must clear so that documentation flows in the right order and rework is minimised, and we hold that work away from client leadership so management bandwidth stays on building the business. We do not promise a timeline as a commitment — no adviser honestly can, because statutory bodies run their own processes — but we do bring the pattern recognition that keeps a project moving through them rather than stalling between them.

The 80/50 problem is real, it is measured, and it is largely a front-end problem. That is the part worth getting right before the first brick.