Why 70% of Transformations Fail: A UK CEO Assurance Checklist

UK CEOs should assure transformation through independent, staged reviews of behaviour, benefits and delivery, using the NISTA and Corporate Governance Code principles, rather than relying on programme self-reporting.

Most transformation programmes report green until they suddenly report red. The gap between those two states is an assurance failure, not an execution surprise. Under the UK Corporate Governance Code (Provision 29 and the board’s wider duty to monitor strategy delivery), directors are accountable for knowing the true state of major change. The model borrowed from government, the National Infrastructure and Service Transformation Authority (NISTA, which absorbed the Infrastructure and Projects Authority) delivery confidence assessment, is a useful template for private-sector chief executives.

According to Boston Consulting Group, writing in Fortune in May 2026, about 70% of reorganisations and transformations fail, a figure that “has not improved in decades”. The same research drew on a survey of 6,000 executives and employees across 15 countries and pinned the cause on leaders misjudging how people actually change, not on employee resistance.

Why do transformation programmes keep reporting green until it is too late?

Programme offices are paid to deliver, so they are poor judges of whether delivery is working. Status reports measure milestones completed, not behaviours changed or benefits banked. A project can hit every date and still leave the organisation operating exactly as before.

BCG’s central finding is the “false consensus effect”: leaders assume the workforce sees the change as they do. When sponsors rely on their own steering group, that bias is reinforced rather than tested. Independent assurance breaks the loop by asking people outside the sponsor’s circle.

Executive Action

• Separate delivery reporting from assurance: the reviewer must not report to the programme director.
• Replace pure milestone tracking with two or three behavioural indicators, such as adoption rates and process-compliance data.
• Ask for a red-amber-green rating that the programme director cannot edit.

What should independent assurance actually test?

Effective reviews cover four questions: is the strategic case still valid, are benefits owned by line executives rather than the programme, is the delivery plan credible given dependencies, and does the workforce understand and accept what is changing. The NISTA delivery confidence scale, from “successful delivery appears highly likely” to “unachievable”, gives a shared language that boards can adopt without inventing a framework.

Time the reviews to decision points, not the calendar. A review before funding is released, one at the design-to-build transition, and one before go-live catch the most expensive errors. Reviews held after money is spent rarely change outcomes.

Executive Action

• Fix three gated reviews now: pre-funding, design-to-build and pre-go-live.
• Assign every claimed benefit to a named business-unit executive and a budget line.
• Use INFORMD’s project review checklist to structure the first review.

How much should the board see, and when?

The board does not need programme detail; it needs an early-warning signal and the confidence to challenge. Directors under section 172 of the Companies Act 2006 must weigh long-term consequences, and a large change programme is frequently the largest single call on capital and management attention. Reporting should therefore reach the board in a short, standard format each quarter, with exceptions escalated immediately.

Link the reporting to your capital discipline. INFORMD’s capital approval assessment template helps test whether a programme still earns its place when assumptions shift, and our executive briefings library includes earlier pieces on aligning strategy to national priorities and on board technology scorecards.

Executive Action

• Agree a one-page quarterly transformation dashboard with the chair and Audit or Risk Committee.
• Define escalation triggers in advance, such as a two-step slip in delivery confidence or a benefits shortfall above a set percentage.
• Invite one non-executive director to sit in on each gated review.

What does a CEO assurance checklist look like in practice?

Start with the behavioural question BCG’s work highlights: have we tested our assumptions about how people will respond? Survey and interview beyond the leadership team, particularly middle managers who carry most of the change load. Compare what they say with what the steering group believes. The gap is your risk register.

Then test the plan. Does the critical path hold if one dependency, a supplier, a regulatory approval or a key hire, slips by a quarter? Finally, test the exit: what evidence would cause you to stop, re-scope or reverse? Programmes without a defined stop condition tend to continue by default.

Executive Action

• Commission a pulse survey of middle managers within 30 days and compare results to steering-group assumptions.
• Run a one-quarter dependency slip test on the critical path.
• Write the stop, re-scope and reverse criteria into the programme charter.

Frequently asked questions

INFORMD provides intelligence briefings, tools and frameworks for senior business leaders across technology, finance, strategy and compliance. Based in Milton Keynes, UK, we help executives stay informed and act with confidence. Explore our full briefing library or access our free assessment tools. To discuss your own programme, get in touch.

Stay ahead. Subscribe to INFORMD’s weekly executive briefing at informd.co.uk.