Your Transformation Might Be Stalling — But Not for the Reason You Think

Your transformation has strong executive sponsorship. The strategy is clear. The governance is in place. And yet progress is slower than it should be. Adoption is uneven. Leaders are stretched. The momentum that was there at launch is gone. What happened? 

You've probably already run through the usual diagnostics. Is it a communication problem? A capability gap? Resistance? Maybe you've found pieces of each. But there's one variable I'd push you to look at before you redesign your change plan: what else is your organization absorbing right now? 

Because in most large companies, the answer is a lot. A restructuring. A systems migration. A new commercial model. A compliance overhaul. Your transformation isn't running in a vacuum. It's competing for the same leaders' calendars, the same teams' bandwidth, and the same organization's willingness to absorb one more change. 

The diagnostic blind spot 

Every transformation has its own governance, its own dashboard, its own status cadence. Within that frame, things may look green. But those dashboards only measure what's happening inside the program. They don't measure the cumulative load on the people who are expected to absorb the change. Those same people are simultaneously being asked to adopt a new system, adjust to a restructured reporting line, and learn a new process, all while keeping the core business running. 

When I see a well-designed transformation losing momentum despite strong fundamentals, the first question I ask is: what's the aggregate demand on this organization right now? The answer almost always explains what the program-level diagnostics can't. 

How it shows up 

The signals are easy to misread. Stakeholders are unresponsive, so you assume it's an engagement issue. Leaders aren't showing up as sponsors the way they committed to, so you assume it's a commitment issue. Teams are slow to change how they work, so you assume it's a readiness issue. 

Each of those reads captures a piece of the picture. But the underlying cause is often simpler: people are overloaded. They're rationing their attention across too many competing demands, and your initiative is getting a fraction of what it needs.   

Three moves that make the difference 

You can't stop running multiple transformations. But you can account for the aggregate demand, so you lead your program more effectively within it. 

1. Build the inventory nobody has. Block 30 minutes with each of your five or six key stakeholder groups and ask one question: what else is asking you to change how you work right now? In every engagement where I've done this, the list is longer than anyone on the leadership team expected.  

2. Identify the collision points. Map where the demands overlap on the same people at the same time. You're looking for specifics: the regional sales team that's being asked to adopt a new CRM, shift to a new compensation model, and absorb a restructured reporting line all in the same quarter. Or the operations managers expected to sponsor your initiative while simultaneously leading their teams through a systems migration. Those collision points are where adoption breaks down first, and knowing them lets you adjust your sequencing, your asks, or your timeline before the damage shows up in your status reports. 

3. Add the aggregate view to your existing governance. Take the inventory and the collision map to your steering committee. Add one standing question to the agenda: what has changed in the broader environment since our last meeting that affects this program's ability to land? Leaders who do this consistently catch problems weeks earlier. 

The bottom line 

The leaders who navigate this well don't slow their transformation down. They lead with a clearer picture of what their organization can realistically absorb — and they make sharper decisions about where to focus. 

Andrea Schnepf 

P.S.: We're exploring one of the most common versions of this collision — AI adoption competing with every other transformation for organizational capacity — on June 24. Join us: Embedding AI Into How You Work: From Adoption to Impact.