The transformation deck on your desk is a rerun — here's the 5-question test that catches it before you fund it

BCG measured the last playbook: 70% of digital transformations fell short, and nobody wrote the closing report. Five questions, one sitting, ending in a word you can say in the meeting — including the one number here you should distrust.

Andrew Ramsden 14 May 2026

Somewhere around the second slide of the AI transformation deck, you feel it. You have approved this deck before.

It said Agile then. Or digital, or cloud, or, if you have been at this long enough, ERP. The fonts are better now, and the demo is genuinely astonishing. And yet the shape of the plan underneath is one you have already funded, watched drift, and quietly stopped asking about.

You remember roughly what the last one cost. You do not remember a closing report, because there wasn't one. Transformations in our industry rarely end. They fade. The steering committee meets monthly, then quarterly, then the invitations stop, and eighteen months later the programme name only comes up as a joke with a wince in it.

You have not said any of this in the meeting. The person presenting is good, the technology is real, and none of us wants to be the executive who blocked the future twice. I have sat in that meeting and said nothing either.

The unprecedented technology, and the extremely precedented plan

Everyone frames AI transformation as unprecedented, and on the technology they are right. The models are new, the economics are new, and the capability curve is unlike anything you rolled out before.

The rollout plan is a different matter, because it is not new at all. Look at the beats: buy the tools first, run pilots staffed by volunteers, publish an adoption dashboard, stand up a champions network, book the benefits into next year's plan. That is not an AI playbook. That is the transformation playbook, the same five beats your Agile rollout ran and your digital programme before it. The nouns changed. The plan didn't.

And unlike the technology, the plan has a track record. Somebody has measured it.

The number audit

Boston Consulting Group looked at senior executives whose companies had run a digital transformation and found that 70% fell short of their objectives. The breakdown is more useful than the headline: 30% met or exceeded their target value and changed the organisation for good, 44% created some value but missed their targets, and 26% created almost nothing.

McKinsey set a stricter bar in its 2018 global survey: only 16% of respondents said their transformation had both improved performance and equipped the organisation to sustain the change.

BCG and McKinsey both sell transformation services, so the firms describing the disease also invoice for the cure. The 70% is a band, not a verdict, and it includes a large group who did get something for their money. It is one survey of self-reported executive judgement, not an audit of anyone's books.

Which is roughly what the last deck's numbers were too, and nobody went back to check them against what actually happened at your company. That going-back is the closing report, and it never got written. So the most expensive research your organisation ever ran, a multi-year, eight-figure experiment on how change behaves in your particular culture, produced findings that are stored nowhere except in the scar tissue of the people who lived through it.

Meanwhile the rerun is already filming. S&P Global Market Intelligence surveyed more than 1,000 organisations across North America and Europe in 2025 and found that 42% had abandoned most of their AI initiatives, up from 17% the year before. The average organisation scrapped 46% of its AI proofs of concept before they ever reached production. The failure rate did not creep. It more than doubled in a year, while the decks got more confident.

What the rerun always skips

The first story is procurement. It is measurable, it finishes on time, and it genuinely completes. The licences exist, the security review passed, the vendor is live.

The second story is usage. Seats active, prompts per employee, adoption curves. It is the story the dashboard is built from, and it misleads in a predictable direction: a thousand chatbot-polished emails read as adoption, while the one team that rebuilt its claims process end to end reads as three users.

The third story is the redesign of the actual work. Which workflow, exactly, now runs differently, owned by whom, with what cycle time. It is the only one of the three that pays for the programme, and the only one that never gets a slide, because it is slow, unglamorous and impossible to buy.

The playbook is very good at finishing stories one and two while story three quietly starves. That is what the beats optimise for. Tools land, volunteers demo, and the redesign of work is left to emerge on its own. It doesn't. It didn't last time either.

The defences, named and shot

"This time the technology is real." It was real last time. Agile was not a fake idea, and iterative delivery genuinely does beat waterfall for most software. Digital was not a fake idea. The technology being real was never the failure mode. The failure mode was a plan that dropped tools into a gap nobody had designed.

"We'll go slower and learn from last time." Slower is not different. A rerun at half speed is still the same film.

"We've hired a Head of AI." The last programme had a transformation office. Someone who owns the programme is not someone who owns a workflow, and the third story is made entirely of workflows.

None of the three names the thing that actually failed, so none of them stops it failing again.

Your scar tissue is the asset

This is where the burned executive becomes the most valuable person in the room instead of the blocker.

Your organisation's last transformation established three things at enormous cost. Which parts of your culture absorb change, and which parts perform it. What happens to freed-up time when nobody redirects it, which is that it dissolves invisibly, leaving no trace in any metric. And which layer of management actually converts intent into changed work, which is the middle layer, and that is precisely the layer the rollout bypassed.

The deck in front of you asks you to set all three aside and run the experiment again. That is subconscious autopilot at an organisational scale: the pattern runs because nobody stopped to notice it running. The alternative is cheap. Write the closing report now, late, in the form of five questions, and run every new deck through it.

The Rerun Test

Take the deck on your desk, the one with the astonishing demo. This takes one sitting. Score each question 0 for no, 1 for partly, or 2 for yes with a name attached.

1. Can anyone in the room say what the last transformation promised and what it delivered? In numbers: the original deck's targets against what happened. If nobody can, you are about to rerun an experiment without its findings.

2. Does the plan name one end-to-end workflow that will run differently by a specific date, with the person who owns its cycle time? "We will empower teams to reimagine work" is not a name. "Claims triage, ninety minutes down to nine, owned by Priya, by March" is a name. This is the strongest signal in the five. A deck that cannot name one workflow has planned the first two stories only.

3. Did the pilot results come from volunteers? Pilots staffed by enthusiasts measure enthusiasm. The last rollout's pilots glowed for the same reason they later failed to scale: tool access was never the constraint, the sceptical middle of the organisation was. A pass is a pilot that includes the team who didn't want it.

4. When the tools free up hours, where does the plan say those hours go? Name the mechanism, not the aspiration. Freed time with no destination becomes invisible slack quickly enough that the productivity case dies while the dashboard stays green. A pass names who redirects the hours, and into what.

5. What result would stop, shrink or redirect the programme, and when is that checked? The last transformation had no answer, which is why it faded instead of ending. A programme that cannot fail by its own definition cannot succeed by it either. A pass is a date and a number.

Reading the score. Eight to ten is a new picture: fund it, this deck learned from the last one. Four to seven is a remake: the material is real, the plan is missing names, send it back for the specific zeros. Zero to three is a rerun, and you already know the ending. Blocking it is not blocking the future, it is declining to pay twice for the same lesson.

One limit, plainly. Five questions cannot tell you whether AI will transform your industry. They can only tell you whether this deck would transform your company, which is a different question, and the only one you are being asked to fund.

The closing report, at last

You will have a score, a word you can say out loud in the meeting, and a written record that your organisation's most expensive lessons were finally allowed to grade something.

Start with question two. If the deck cannot name one workflow, you do not need the other four this week. And if you run this on a deck and it changes what gets funded, I would genuinely like to hear about it.

Attribution

Written by Andrew Ramsden. AI tools assisted research and drafting; all outputs verified.

Accountable

Andrew Ramsden.

Limitations

BCG's and McKinsey's figures are self-reported by executives in the firms' own surveys, and both firms sell transformation services. The S&P Global figures are quoted via CIO Dive; the underlying report is paywalled.

References

Three sources, retrieved and hashed on 26 and 27 August 2026, each figure quoted with a locator in the SOURCED sidecar.