Ask a room of executives whether their strategy is clear, and almost every hand goes up. Ask the people three levels down to describe that same strategy, and the room goes quiet. That gap, between what leaders set and what teams actually receive, is where change quietly dies in the middle. It even has a name now.
Earlier this year the PMI and Agile Alliance introduced the Manifesto for Enterprise Agility. Defining what enterprise agility is turned out to be the easy part. The hard part is that organizations with genuinely good strategies keep struggling to take them from vision to execution. So PMI and the Agile Alliance researched the gap, and the result is a report called Closing the Change Readiness Gap. Its findings are worth sitting with!
Inside: why confident leaders and confused teams can both be telling the truth, the four obstacles that stall almost every transformation, why they are really one connected system, and the reframe that should change how you think about your middle managers.
The Gap Nobody at the Top Can See
The report opens with a number that stops you. Seventy-two percent of executives say their purpose is clear, and only about a fifth of leaders think a lack of clarity is a challenge worth worrying about. Yet the single highest answer in the survey, named by more executives than anything else, was the disconnect between planning and execution.
Both of those things are true at once, and that is the whole problem. Everyone agrees on the strategy. A lot of the time, people simply cannot describe what it is. Leaders are looking at green dashboards and reading them as proof the system is working, while the people doing the work are quietly guessing about what really matters. The report calls out four obstacles that create this gap, and the most useful move is to stop treating them as a checklist and start seeing them as a loop.
1. Signal Loss
The first obstacle is signal loss. Strategic intent starts at the top as a grand, glorious purpose, and then it calcifies as it travels down. The work moves with the org chart, but the why gets stripped out along the way, so the people on the ground are left thinking, I guess this is what we have to do. It happens all the time. At many organizations, KPIs that were framed as aspirational at the top land on the teams as hard requirements. People go a little crazy trying to hit numbers that were never meant to be pass or fail, because the intent behind them never made the trip down. The fix is deceptively simple. Do not ask people whether they are aligned to your priorities, because of course they will say yes. Instead ask what they are working on and how it connects to the top priority, and ask two or three levels below you, not your peers. The repair is real feedback loops in both directions, and empowering the managers and project professionals in the middle to be the repeaters who carry the message and bring operational reality back up.
2. Decision Rights, Within the Guardrails
The second obstacle is decision rights that sit too far from the work. If you are writing code and you have to go up three levels to ask whether you can use an API, something is broken. Authority needs to live where the information lives. Executives told the researchers they find this genuinely hard. They want to empower people, but they do not know how to truly make it happen, and they are afraid of losing control over decisions they will still be held accountable for. Teams feel the other side of that fear. They hesitate to decide because they are not sure the organization will have their back if they get it wrong. The phrase that cuts through it: decentralizing is not an abdication of decisions, it is moving authority to where the work gets done. Empowerment is authority with guardrails. The payoff shows up in the data, where empowered teams are nearly twice as likely to say decisions get made in time, and in a metric the report urges leaders to track, decision latency, because the longer a decision takes, the more it costs you.
3. Psychological Safety Is an Operational Problem
The third obstacle is the one that underpins everything else, and the report frames it in a way that lands hard. Psychological safety is an operational issue, not a cultural one. Everyone believes they understand psychological safety, and most leaders genuinely value it. What they do not know is how to operationalize it. It is a great thought, but how do you really build it, on this team, in this department, by design rather than by hope? The answer is that it starts at the top and must be earned over time. You make failure safe, you treat a good experiment that did not work as something to learn from out loud, and you lead by example rather than announcing that people are now free to speak up. Most organizations are not there yet, and until they are, the other three obstacles stay hidden, because naming a problem is exactly the thing an unsafe system punishes!
4. The Frozen Middle Is Really a Shock Absorber
There is a reframe worth making here. For years we have blamed the middle. We call managers the permafrost, the frozen layer where change goes to freeze. That label deserves to be retired. Think about what those managers do. They take pressure from the top and pressure from the bottom, and they hold the business together in between. They are told to move faster, do not miss the deadline, do not overspend, do not escalate, and they absorb all of it so the work can keep flowing. What looks like resistance is often absorption. That makes managers not the obstacle but the best bet for enterprise agility. A gym metaphor fits. If your arms are strong but your core is weak, you cannot lift much or run far. The core is what keeps the whole body aligned, and in an organization, that core is the management layer. Strengthen it instead of blaming it.
Four Obstacles, One System
The real insight is that these are not four separate problems to fix one at a time. They are a loop. Intent degrades on the way down, so people start asking instead of acting, because acting without context is risky. That pushes decisions upward, approvals accumulate, and structure hardens around them as someone adds a process to compensate. Nobody names the dysfunction because naming it is risky for a career. Every obstacle is downstream of the one before it, and psychological safety runs all the way underneath.
This is also why bolting on a solution does not work. A Deloitte finding shows nearly half of companies adopted AI without changing the underlying process structure. You cannot put more paper in a printer and expect it to print faster, and you cannot drop AI onto a slow, tangled system and expect speed. The same is true of frameworks. Implement Scrum but change nothing about how you fund work, make decisions, or grant approvals, and you have changed the vocabulary and nothing else. You do not get enterprise agility by making nine teams agile. You get it by fixing what happens between them. That is exactly what the report means by a change readiness gap.
Start by Walking the Edges
So where does a leader begin? Consider a story from one leader early in her career. As a brand-new product director, she learned that her CEO planned to spend a whole day shadowing her. It was not an evaluation. He wanted to see his own company through the eyes of someone who had not yet adjusted to it. The lesson took years to fully land. A leader sits in the middle of the system and cannot see its edges. She was on the edge, still new, so he walked out to the edge with her to see what the system really looked like from there. You cannot understand the whole system from the center. You must walk the edges.
The rest of the starting point costs nothing. Pick one decision from last month and trace it. What did the people on the ground hear? How long did it take to travel from top to bottom, and what did that latency cost? Closing this gap does not start with a framework. It starts with leadership.
The One Line to Take Home
If you keep a single idea from all of this, make it this one. Agility is not something you install in an organization. It is a behavior that a system either permits or prevents. If the system prevents it, no framework will save you. If the system permits it, there is real hope.
One closing thought sits right alongside it. Change readiness is a team sport. It is not a leader thing, or a team thing, or a middle thing. It is an everyone thing. But leaders set the tone, and the leaders who treat psychological safety as a strategy, not a slogan, are the ones whose organizations will be ready when the next change arrives. Because it will.
Go deeper: read the full PMI and Agile Alliance report, Closing the Change Readiness Gap, at agilealliance.org/closing-the-change-readiness-gap