There’s a label that gets applied quickly when change isn’t landing the way leadership hoped.

Resistant.

It shows up in performance conversations, in strategy post-mortems, in frustrated one-on-ones. The change was right. The direction was clear. And still, the team didn’t move the way you expected.

Before you accept that story, it’s worth asking a different question.

How many changes came before this one?

Not just the big structural ones. The reorgs, the pivots, the new priorities that quietly replaced the old ones. The initiatives that launched and then faded. The leaders who came in with energy and left before anything settled. The moments when the team reorganized around something, a shared way of working, a clear sense of who they were, and then had to let it go before it fully took hold.

Resistance looks like disengagement, cynicism, slow execution, blame between teams. So does exhaustion from incomplete integration.

The difference matters.

A resistant team is pushing back on direction. An exhausted team has stopped trusting that any direction will hold long enough to be worth committing to.

One needs a harder conversation. The other needs something to stabilize around.

I’ve been on both sides of this. Watching a team disengage from something I believed in. And being part of a team that had absorbed so much change that the next initiative, however good, felt like one more thing to survive rather than something to build together.

In both cases, what looked like resistance was really a system that hadn’t been given enough time to land.

When a team goes through significant change, there’s a period where the old way of operating no longer fits and the new one isn’t yet solid. Roles are unclear. Trust is thinner. The shared story about who the team is and what it’s doing hasn’t been rewritten yet.

That period needs time and containment to close.

If another change arrives before it does, the gap widens. The team stays in that in-between state longer. And the longer it stays there, the more that instability becomes the baseline, not a temporary condition but a culture.

The one thing worth doing differently:

Before launching the next initiative, ask your team, not in a survey but in a real conversation, what from the last change still feels unresolved. What’s still unclear. What they’re still carrying.

You don’t have to fix all of it. But naming it does something. It signals that you’re not just moving forward but paying attention to what got left behind.

That distinction is often what makes the difference between a team that can move with you and one that’s too tired to try.