Air Cover Isn't a Nice-to-Have

I've worked with a lot of teams navigating transformation. Different industries, different sizes, different starting points. Some of those efforts produced real, lasting change. Others stalled, shrank, or quietly died — not because the teams weren't capable, but because the conditions around them weren't built to let them succeed.

If I had to point to the single variable that most consistently separates those two outcomes, it wouldn't be the methodology. It wouldn't be the tools, or the training, or the quality of the change practitioners involved. It would be this: whether or not senior leadership was genuinely in it.

Not symbolically. Not in the kickoff speech. Actually in it — making visible decisions that protected the work, absorbing organizational friction so the teams didn't have to, and staying committed when the effort got uncomfortable.

That's what air cover means. And when it's absent, almost nothing else compensates.

What Air Cover Actually Is

The term gets used loosely, so it's worth being precise. Air cover isn't a leader sending an email announcing that transformation is a priority. It isn't having an executive sponsor listed on a project charter. It isn't showing up to the quarterly review.

Real air cover is what happens in the moments of organizational resistance — and there are always moments of organizational resistance. It's when a powerful department decides the new way of working doesn't apply to them, and leadership holds the line rather than carving out an exception. It's when a team runs an experiment that doesn't pan out and leadership treats it as learning rather than failure. It's when the pressure to revert to the old way of doing things rises, as it inevitably does, and the people at the top stay visibly committed to the direction they said they were going.

What makes air cover rare isn't that leaders don't care. Most of them do. What makes it rare is that providing it requires leaders to put something on the line — their credibility with other senior stakeholders, their comfort with uncertainty, their tolerance for the messy middle of real change. That's a harder ask than signing off on a transformation program. Most leaders are willing to do the former. Fewer are willing to do the latter.

What Happens Without It

Without meaningful air cover, transformation efforts tend to follow a predictable arc.

The work starts with energy. Teams engage, momentum builds, early wins surface. People start to believe something might actually be different this time. And then the organizational immune system activates — not maliciously, but naturally. Departments that feel threatened begin to resist. Middle managers who weren't consulted create friction. Processes that were supposed to change stay exactly where they were. Political capital gets spent defending old territory rather than building new ways of working.

At that moment, teams look up. They're watching to see how leadership responds. Whether the resistance gets addressed or quietly accommodated tells them everything they need to know about how serious this really is.

If leadership steps back — if they allow exceptions, avoid conflict, or signal that some parts of the organization are exempt from the change — the message lands fast. The transformation becomes optional. People who were genuinely committed start hedging. The effort doesn't always collapse immediately; sometimes it limps along for months. But the outcome is usually the same. A lot of activity. Not much that sticks.

The Implicit Endorsement Problem

One of the more subtle dynamics in transformation work is what I think of as the implicit endorsement problem. When senior leaders fail to address visible resistance or allow certain teams to opt out, they haven't just made a neutral decision. They've taken a position — one that gets read and interpreted throughout the organization, even if nothing was explicitly said.

This is how transformations die quietly. Not in a single moment of decisive failure, but through a series of small, unremarked accommodations that accumulate over time. Each one sends a signal. Together, they tell the organization that the new way of working is something to tolerate, not commit to. And once that belief is established, it's very hard to reverse.

The teams closest to the work see it first. They notice which groups are held to the new standards and which aren't. They notice whether the leaders championing change actually model it in their own decisions. They notice whether the people who resist openly face any consequence, or whether the path of least resistance is to wait it out. What they see shapes what they do — and over time, what they expect.

Why This Is a Leadership Problem, Not a Change Management Problem

There's a tendency to respond to stalled transformations by adding more change management infrastructure. More communication plans. More training. More reinforcement activities. More coaches embedded in more teams.

Sometimes that's the right response. But often it's a way of avoiding the harder conversation — which is that the change management effort is being asked to compensate for insufficient leadership commitment.

Change practitioners can map the path. They can design the process, facilitate the sessions, build the capabilities, and help teams navigate the transition. What they can't do is create organizational safety for the work when that safety doesn't exist. They can't protect teams from political consequences that leadership hasn't chosen to absorb. They can't hold a department accountable when the leader above that department has signaled, implicitly or otherwise, that accountability doesn't really apply here.

The work of creating conditions for change belongs to the leaders who have the authority to shape those conditions. When that work gets delegated entirely to a transformation team or a set of external consultants, the outcome is usually predictable — and usually disappointing.

What Genuine Commitment Looks Like

None of this means transformation requires perfect leadership or frictionless organizational support. Successful transformation almost always involves conflict, setbacks, and difficult decisions. What it requires is leaders who are willing to engage with that difficulty rather than route around it.

In practice, that means a few specific things. It means naming the resistance when it shows up, rather than hoping it resolves itself. It means holding consistent expectations across the organization, not granting exceptions that undermine the whole. It means being willing to have hard conversations with senior peers when their behavior is working against the effort. And it means treating the occasional failed experiment as the cost of real change, not a reason to slow down or pull back.

It also means leaders being honest with themselves before a transformation starts. Not just asking "do we want to change?" but asking "are we prepared to actually do what change requires?" — including the parts that are politically uncomfortable, that require letting go of control, and that will expose current ways of working to real scrutiny.

That's a harder question. But the organizations that ask it — and answer it honestly — tend to be the ones that end up with something that actually lasts.

The Differentiating Variable

When I look back at the transformation efforts I've seen succeed, the teams involved weren't always the most skilled or the most experienced. The methods weren't always the most sophisticated. What those efforts had in common was that someone at the top had made a genuine decision: this matters, we're going to do what it takes, and I'll use my authority to protect the conditions that make it possible.

That's it. That's the differentiating variable.

Air cover isn't a nice addition to a well-designed transformation effort. It's the thing that determines whether a well-designed transformation effort has any chance of becoming real.