Why Enterprise Transformation Programmes Stall After 18 Months (And 3 Governance Fixes That Change This)

The Sustained-Gains Rate Has Not Moved Because Programmes Are Built to Close

McKinsey has tracked transformation outcomes since 2012. The 30% sustained-gains rate has stayed stubbornly low across organisational, digital, and operational programmes alike. For digital transformations specifically, McKinsey's 2018 survey found that only 16% of organisations both improved performance and positioned themselves to sustain it. The investment has grown; the outcomes have not followed.

BCG's 2020 research identified the three design failures most commonly present in stalled programmes. First: governance closes with the programme rather than persisting into the operational phase. Second: the teams assembled for the initiative are released at programme close, taking institutional knowledge with them. Third: capital expenditure budgets are tied to a delivery endpoint, which means continuing the work requires a new justification cycle, often one that has not been designed or funded. The programme ends, and so does the momentum.

This pattern is not accidental. It reflects how most enterprise governance is designed. Projects have a scope, a budget, and a close-out date. That design is appropriate for delivering a defined output. It is not appropriate for building a transformation capability that needs to compound across cycles. The design mismatch is the failure, and it shows up at the 18-month mark when the initial wave of investment and energy runs into the structural limits of a governance model built to conclude.

Build the Three Governance Fixtures That Outlast the Programme

BCG's research points to three specific design choices that materially raise the rate at which organisations sustain transformation gains. Each choice is a direct response to the three design failures above.

First: design persistence into your governance from the outset, not as an afterthought at close-out. Which governance bodies, forums, and decision rights survive the programme boundary, and what triggers their continuation? If the answer is not written into the programme design before the first milestone, it will be absent when it matters.

Second: identify which teams carry the institutional knowledge that cannot be reconstructed from documentation. Plan retention explicitly. Teams released at programme close do not simply move on. They take with them the tacit understanding of what was tried, what failed, and why certain design choices were made.

Third: have the operational expenditure conversation with your CFO during this planning cycle, not in the close-out report. Transformation that moves from capital investment to operational capability needs a funding model that reflects continuity, not one designed around a delivery endpoint.

Persistent Governance Is a D4 Design Decision, Not a Procurement Choice

D4 frames transformation governance as a continuous operating system, not a project with a finish line. The distinction matters because it changes the design brief. An operating system is designed to persist, learn, and improve with each cycle. A project is designed to deliver and close. When the governance model matches the operating system brief, the compounding effect BCG describes becomes structurally achievable. The organisations that sustain transformation gains are not doing something extraordinary in delivery terms. They have made a different design choice about what governance is for.

The next time your programme reaches its close-out phase: what triggers governance continuation, which teams survive the boundary, and what does the funding look like in year two? If any answer is "the programme ends," there is more design work to do.