Change Without Whiplash
Most teams can handle more change than their leaders think.
What they can't handle is whiplash.
They can handle the hard pivot that obviously needs to happen. They can handle the well-explained shift that fits the mission. Even the uncomfortable stretch that makes people grow.
Whiplash is different. Priorities change faster than people can absorb them. Yesterday's direction disappears, and nobody says a word about it. A leader says, "We need to be agile," and the team hears, "Nothing you're working on is safe."
Adaptive vs. Erratic
There's a real difference between adaptive leadership and erratic leadership. Adaptive leaders explain the why, name the tradeoffs, and stay close while people adjust. Erratic leaders change course and leave everyone else to clean up the confusion.
Teams know which one they're getting.
What Fatigue Actually Looks Like
The hard part of badly led change isn't the new work. It's the repeated loss of footing. People stop going all in because they're not sure how long anything will last. They get cautious. Not because they're stubborn. Because they've been burned.
Then leaders see that caution and call it resistance.
Sometimes resistance isn't resistance. It's fatigue.
Respect What Change Costs
If you want to lead change well, start by respecting what change actually costs. Every pivot asks people to let go of something. A routine. A plan. A sense of competence. A relationship to the old way. Sometimes a piece of how they see themselves.
Leaders forget this because they've usually been sitting with the change for weeks before they announce it. By the time the team hears about it, the leader is already on the other side emotionally. The team is just walking into the disruption for the first time.
Good leaders slow down long enough to close that gap.
Five Questions to Answer Early
Why are we changing this?
What stays the same?
What will be harder for a while?
What support will people have through the transition?
What does success look like on the other side?
Those answers don't eliminate discomfort. They reduce chaos.
Name the Messy Middle
It also helps to name the middle honestly. Change almost always has a messy middle where the old system is gone, the new one doesn't feel natural yet, and everyone is a little worse at their job than they were two weeks ago. When leaders pretend that part should feel smooth, people think something is wrong with them. When leaders name it, people relax enough to keep going.
You can say things like: "This will probably feel slower before it feels better." Or: "Some confusion right now is normal." Or: "We're not looking for perfection on day one. We're looking for traction."
That kind of honesty lowers fear without lowering standards.
Stop Changing Everything at Once
One more thing leaders get wrong: changing too much at once. Not every problem needs its own initiative running at the same time. What looks like a transformation from the top can feel like fragmentation from the middle. When everything shifts together, nothing feels solid.
Strong leaders sequence change. They figure out what has to change now, what can wait, and what doesn't actually need to change at all.
That last category matters more than people think. During transitions, teams need to know what's still true. The purpose. The standards. A few stable rhythms they can count on. Those anchors are what keep change from turning into free fall.
This Week
Pick one change you're leading right now. Before you communicate it again, answer five questions in plain language. Why this? Why now? What stays the same? What's going to be hard for a while? What should people do next?
Then say it clearly.
Teams can walk through hard transitions. What wears them down is doing it without footing.
Leadership Reframed goes deeper on this shift — especially if you're trying to build a team that can think and move without waiting on you.
Comments