Why execution fails before projects begin.

Every project — infrastructure, mining, a large capital programme — possesses a finite period during which its underlying assumptions can still be challenged inexpensively. We call this the Framing Window. It opens the moment a project is conceived and closes the moment resources are committed against a fixed understanding of the problem. Almost every catastrophic project failure we have studied has the same root cause: the Framing Window closed before anyone realised it mattered.

The mechanism is specific, not vague. Early in a project, assumptions are cheap to test and cheap to change — a scope line can still move, a regulatory question can still be asked, a capital structure can still be redesigned. Each of these has a near-zero cost of correction. Once contracts are signed, teams are mobilised, and a delivery schedule is published, the same corrections cost ten to fifty times more, because now they require unwinding commitments rather than simply choosing differently. The window doesn't close gradually. It closes at the specific moment the organisation converts an assumption into a commitment.

This is why post-mortems on failed projects read the same way, regardless of sector. The execution team was diligent. The plan was detailed. The reporting was thorough. And still, the project finished a year late and forty percent over budget. The autopsy finds nothing wrong with how the project was run, because the fault was never there. It was upstream — in what the project was permitted to become before anyone with the authority to ask a harder question actually asked it.

The Framing Window

We define it precisely because vague concepts don't get used. The Framing Window is the interval between a project's conception and the point at which its core assumptions — scope, sequencing, capital structure, regulatory exposure — become materially expensive to revise. It is detectable in advance: it closes at the first irreversible commitment, whether that is a signed contract, a mobilised team, or a public announcement of scope. Organisations that consistently outperform are rarely the ones with superior delivery capability. They are the ones with the discipline to keep the Framing Window open until the load-bearing assumptions have actually been tested, not merely believed.

The organisations that execute well are not the ones with the best delivery teams. They are the ones that keep the Framing Window open long enough to get the framing right.

This is not an argument for endless analysis, and treating it as one misses the point entirely. Prolonged ambiguity has its own cost, addressed elsewhere in this series as Decision Debt — and an organisation that never commits is as exposed as one that commits too early. The discipline is narrower and more demanding than "be thorough": identify which specific assumptions are load-bearing, test those, and only those, before the window closes on its own.

How we use this

In our advisory work, the Framing Window is not a metaphor — it is a checkpoint we build into the front of every engagement, deliberately, before mobilisation begins. Three questions carry almost all of the diagnostic weight: what has to be true for this plan to succeed; which of those things have actually been verified rather than assumed; and who inside the organisation has the standing to say the frame is wrong while it still costs nothing to say so. This pattern recurred often enough across our engagements that we encoded the diagnostic itself into Exeri — not as a philosophy, but as a repeatable check run against live project data before the window closes.