3.1 — Three Sources of Transformation Failure

This post covers Zone 3: The Resistance — naming the three failure patterns that push back against every transformation.

If you've read the first post in this series, you know where I'm coming from: transformation fails not because of the tools, but because of how it's led. In this post, I want to get more specific. After decades of leading and observing large-scale transformations across both the public and private sector, I've identified three recurring sources of failure that show up again and again — sometimes alone, sometimes in devastatingly effective combination.

I'll summarize all three here. Future posts in the series will go deeper on each one. As you read, you'll likely recognize at least one — and possibly all three — in an organization you've been part of.

The Three Sources

A simple example: you may have a critical product that can only run on an operating system that is out of support. If it breaks, you are on your own. The odds of having the right specialist available to rescue you at that moment? Close to zero. Eventually, a smoldering platform will burst into flames — through a security vulnerability, a hardware failure, or simply stopping working one day. And that will be a very bad day for whoever is responsible for keeping the lights on.

The cruel irony is that smoldering platforms are almost always known. Leadership is aware. The risk has been discussed. But budget cycle after budget cycle, the problem gets deferred — until it can't be.

Here's how it typically unfolds. An organization commits to a transformation path — say, Agile. A year in, leadership begins to realize that Agile requires an enormous amount of discipline to execute well. It's harder than the books made it sound. Then someone "discovers" a new path — the Cloud, or AI, or some new methodology — and announces it as the next priority. The original path gets quietly abandoned.

The real damage isn't just the wasted investment. It's what the silver bullet chase does to organizational culture. Teams learn quickly that sustained effort on a hard problem will eventually be replaced by a shiny new initiative. So why lean in? Why invest deeply in something that will be set aside in 12 to 18 months? The silver bullet pattern breeds cynicism — and makes each subsequent transformation harder to launch, let alone sustain.

At one financial institution I worked at, during lean times, leadership decreed that only critical production support, regulatory reform, and security controls would be funded. Overnight, every funding request transformed into one of those three categories. I saw the same thing happen when an organization declared security its top priority — suddenly, every initiative "enhanced security." The work didn't change. The labels did.

The result is a Big Ball of Mud: a sprawling, loosely connected tangle of efforts that no one can clearly explain, prioritize, or measure. It looks like progress. It produces very little of it.

I once worked for an executive who did something remarkable in contrast: he identified exactly three strategic areas of focus, highlighted incremental progress on each at every quarterly meeting, and made it a very big deal when — after three years — he added a fourth. That discipline is rare. And it works.

Why These Sources Are Especially Dangerous in Combination

On their own, each of these failure sources is damaging. But they are particularly devious when combined. Consider an organization that ignores a smoldering platform (Source 1) until it explodes, then responds by launching a massive modernization initiative without clear priorities (Source 3), and then pivots midway to chase a new technology trend (Source 2). I've watched this exact sequence play out. The organization emerges years later exhausted, over budget, under-delivered, and culturally broken.

The good news is that all three sources are identifiable in advance — if you know what to look for and you're willing to ask the right questions. That's exactly what we'll focus on in the next two posts in this series.

A Note on Finding the Right Advisors

One more thing worth saying directly: when you are considering a major transformation, make sure whoever you select to help has actually walked the walk. There is no shortage of consultants who are two chapters ahead of you in the book. What you need is someone who has personally led large organizations through transformation while under the gun to deliver day after day — someone who understands that your organization's primary job is not to transform, but to deliver.

In the next post, we'll get practical — walking through a step-by-step approach to locating and prioritizing the smoldering platforms in your organization before they become burning ones.

---