Why Your Change Management Is Solving Yesterday's Problem
- Kelly Brogdon Geyer

- Jun 1
- 3 min read

Most change management frameworks were designed for a world where change was episodic. A merger. A system implementation. A restructuring. You planned it, communicated it, managed the transition, and declared it done. Then everyone went back to normal.
That world is gone. It has been gone for a while.
The problem is that most organizations are still using episodic frameworks to manage continuous change. Kotter's 8 steps. ADKAR. Prosci. They are excellent methodologies for the world they were designed for. They assume a beginning, a middle, and an end. They assume a return to stability. They treat change as something you complete.
Nobody in a leadership position actually believes their organization will return to stability. And yet the tools they reach for still operate on that assumption.
That is an expensive mismatch.
Where the methodology breaks down
There are identifiable characteristics when episodic change management is applied to continuous change:
You launch a transformation. You communicate. You train. You manage resistance. You hit go-live. You declare success, or near enough. Then, before the organization has absorbed that change, the next one starts.
People aren't confused because the change is hard. They are overwhelmed because the changes have no pauses between them. Every new initiative arrives before the last one has landed. Adoption is incomplete. Muscle memory has not formed. And then they are told to absorb the next thing.
This gets labeled "change fatigue." It is usually change overload, which is a different problem with a different fix. I will come back to that in a future issue.
Depending on which source you use, research puts transformation failure rates consistently at between 65% and 95%. The common explanation is "resistance to change." The actual explanation is usually simpler: the organization never built the capability to absorb change continuously. So each initiative is, effectively, a one-time renovation on a building that will need renovating again next quarter.
What you actually need
The fix is not a better change methodology. It is not more communication. It is not stronger leadership buy-in, though all of those matter.
What you need is an organizational infrastructure that treats change as normal, not exceptional.
That means building assessment capability: the ability to read what is actually happening before something becomes a crisis. It means governance structures that can adapt without requiring a full executive alignment process every time. It means leadership that can sponsor change continuously, not just for high-visibility projects. It means embedding behavioral changes rather than training them once and hoping they stick.
These are not project management problems. They are capability problems. No change management methodology, however well-implemented, builds them for you.
This is what I mean when I talk about the Adaptive Capability Ecosystem (ACE). It isn't a replacement for your change management approach. It's the organizational foundation that makes change management actually work. Without it, you are renovating. With it, you are building something that adapts continuously.
The question for your organization
If your organization is in the middle of, or has recently completed, a major transformation, ask yourself this: when the next change arrives (and it will), how quickly can your organization absorb it? Not manage it. Absorb it.
If the honest answer is "we would need another full change program," that is useful information. It means the work you just did left the organization more or less where it started, in terms of capability.
I work with executives who are already asking this question. They have done the programs. They have hired the consultants. They know something is structurally off, even when they cannot point to exactly what.
If that sounds familiar, the starting point is a 60-minute conversation (not a pitch) where I understand your situation: what you've already tried, what worked, and what didn't work. From there, we decide together whether an Adaptive Capability Diagnostic makes sense. If it does, it involves stakeholder interviews, documentation review, and delivers a maturity profile across all six ACE dimensions plus a strategic roadmap. If it does not, you walk away with a clearer picture of what you are dealing with.
Either way, you spend an hour. Not a bad return for something that could save you from that 65-95% failure rate.
Curious where your organization stands? Start with a conversation.




Comments