The 6 Capability Gaps Hiding Inside Every Transformation

Every transformation failure I've seen traces back to one of six gaps. Most leaders can't see them until it's too late.

There's a statistic that gets quoted in every change management conversation: 70% of transformations fail. It's old, outdated, and inaccurate.

It's been cited so many times it's stopped meaning anything. It's become a backdrop, not a diagnosis. And the number is actually much higher.

There is something that the statistic doesn't tell you: they don't fail randomly. After more than two decades of working inside transformations across 22 countries, I've stopped being surprised by failure. What I keep noticing is where it happens. The same six gaps appear, again and again, across industries, across geographies, across transformation types.

They hide. They don't show up in the project plan. They don't appear on the status dashboard. And by the time they're visible, the damage is already done.

This blog post is about those six gaps — what they are, what they look like from the inside, and why most organizations don't notice them until they've already paid the ultimate price for them.

Gap 1: No early warning system

The first gap is sensing. Most organizations are reactive by design. They find out about a problem when it becomes a crisis, not before.

I'm not talking about market intelligence or competitive scanning. I'm talking about the internal signals that tell you your organization is approaching its limit. Change saturation. Capability shortfalls. Governance bottlenecks that are dramatically slowing every initiative down.

The organizations that navigate change well have built mechanisms to read those signals early — before the transformation launches, not six months in when the schedule is already slipping. The ones that don't have those mechanisms are perpetually surprised by things that, in hindsight, were visible all along.

If your organization keeps encountering the same problems at the same point in every initiative, that's not bad luck. It's a sensing gap.

Gap 2: Governance that can't carry the load

Most PMOs were built for a world of sequential priorities. One initiative at a time, managed through to completion.

That's not the world most organizations are operating in now.

When I ask leadership teams how many major transformations are running in parallel, the number is almost never one. It's five. It's seven. Sometimes more. And the governance structure hasn't kept up.

The gap here isn't a lack of process. It's a lack of capacity logic. There's no mechanism to ask, before launching the next initiative: can our organization actually absorb this? Is this the right time? What do we need to complete or stop before we take this on?

Without that question built into the process, organizations keep adding load to a structure that was never designed to carry it.

Gap 3: Capability you're renting, not building

This is the gap I see most consistently, and the one that's hardest to recover from.

Organizations hire external consultants to lead a transformation. The consultants do their work. The transformation ends. And six months later, the organization is back where it started because nothing was transferred, embedded, or owned internally.

You didn't buy change. You rented it.

The organizations that build lasting adaptability treat capability development as a strategic investment, not a project deliverable. They ask, who inside this organization will own this after we leave? They design learning into the process. They measure whether the capability actually transferred.

The ones that don't are in a continuous cycle of external dependency, spending more on the next transformation than the last because the organization never got stronger.

Gap 4: A culture that rewards the wrong things

This one tests the limits because it implicates leadership directly.

Culture isn't a values statement. It's what gets rewarded and what gets punished. And in many organizations, the behavior that gets rewarded — certainty, speed, individual performance, staying in your lane — is precisely the behavior that works against change.

I've watched organizations launch transformation programs while simultaneously promoting leaders who undermine them. Not out of malice. The leaders just had the highest numbers.

If your culture punishes people for admitting they don't know something, you've made psychological safety impossible. If you reward activity over progress, you've made honest status reporting impossible. If seniority protects people from accountability, you've made leadership alignment impossible.

The gap isn't that people resist the transformation. It's that the environment makes it rational to do so.

Gap 5: Sponsors in name only

Prosci's research has tracked this for decades: executive sponsorship is the single highest-correlated factor with change success. Not methodology. Not budget. Not team size. Sponsorship.

And yet, in most transformations, sponsorship is treated as a formality. The sponsor signs off on the charter. They show up for the launch event. They check in at the go-live. In between, the project team is on their own.

Active sponsorship means something different. It means the leader is visible throughout the process, not just at the beginning and end. It means they're having the conversations that only someone at their level can have. It means they're removing barriers that the project team can't reach.

When sponsors disappear mid-transformation, the message to the organization is clear: this initiative is not actually a priority. Teams read that signal faster than any communication plan can correct for it.

Gap 6: You shipped the project. The transformation is still waiting.

The last gap is the one that gets celebrated away.

Go-live is not the finish line. Neither is the final sprint review. Neither is the consultant exit. But organizations treat those moments as success and stop measuring what actually matters.

Did the intended outcomes arrive? Is the new system actually being used the way it was designed? Did behaviors change, or did people find workarounds? Is the improvement holding six months later, or has the organization quietly reverted?

Execution without sustainment is just a more expensive way to end up where you started.

The organizations that close this gap build measurement into the transformation from the beginning. They define what "success" looks like in six months and in two years — not just on the day the project closes. And they stay accountable to that definition even after the initiative officially ends.

What this looks like in practice

Almost no organization has all six gaps at once. Most have two or three, and those two or three are enough to determine whether the transformation sticks.

What makes this hard is that the gaps aren't always visible to the people inside the organization. Leadership often doesn't know they have a sensing gap until they're already in crisis. They don't know they have a sponsorship gap until the team has already lost momentum. They don't know they have a sustainment gap until the project has been declared a success and the results haven't followed.

This is exactly what the Adaptive Capability Diagnostic is designed to map. Not from a survey, but from evidence — stakeholder interviews, documentation review, a look at what the organization says it does versus what it actually does.

The output is a maturity profile across all six dimensions, a root cause analysis, and a roadmap. Not a generic best-practice list. A specific picture of where your organization's response mechanisms hold and where they don't.

If you've read this issue and recognized your organization in any of the six gaps — that recognition is usually enough to warrant a closer look.

---

I work with leaders from small to mid-size organizations who are curious about where they stand across these six dimensions and how to improve. If you're curious where your organization stands, let's have a conversation to see if this fits your situation:

— Kelly Brogdon Geyer