Large IT transformations fail because execution quietly breaks down after the strategy is approved.
That's the problem in a nutshell
That’s a point explored well in @McKinsey & Company’s article “Why do most transformations fail?” by @Scott Keller and @Mary Meaney.
The article highlights familiar risks: underestimated complexity, misaligned leadership, and momentum that fades once the program moves from planning to delivery.
All of that is true.
But here is where those failures show up.
In practice, transformations rarely collapse at the executive level. They fracture downstream, when strategy meets real-world conditions across hundreds or thousands of locations.
It shows up as:
• Sites that are “mostly ready” but not fully prepared • Execution quality that varies just enough to cause rework • Second visits that weren’t planned or budgeted • Internal teams pulled into constant escalation instead of forward progress
None of those issues look fatal on their own. Together, they compound.
By the time leaders feel the impact, the program isn’t failing loudly—it’s carrying execution debt.
This is why execution discipline isn’t an operational detail. At scale, it is the strategy.
The organizations that execute well don’t rely on effort or heroics. They rely on clarity.
Clarity around what success actually looks like at the site level. Clarity around what must be ready before work begins. Clarity around who owns outcomes when conditions aren’t perfect.
Repeatability matters more than effort. Preparation matters more than speed. And systems matter more than individual performance.
This is where my work is focused.
I help leaders turn strategy into execution models that can actually hold up in the real world—models designed for compressed timelines, imperfect conditions, and the reality of operating at scale.
That means pressure-testing plans before rollout. Designing execution so the first visit is the only visit. Removing ambiguity so teams aren’t forced to improvise under stress.
Because successful transformations aren’t defined at kickoff. They’re defined weeks and months later—by whether progress feels controlled or chaotic.
The most important question isn’t: “Is the strategy sound?”
It’s: “Is our execution model clear enough to survive reality?”
That’s where transformations either hold—or quietly unravel.
"What Actually Matters" LinkedIn Newsletter