The Operations Bridge

There’s a version of leadership that treats every quarter as an opportunity for a new initiative. New software, new layout, new metric, new process. Each one, in isolation, is defensible. Stacked on top of each other without pause, they add up to something I’ve come to take very seriously: change fatigue.

I didn’t recognize it the first time I saw it. I read the flat affect, the slower buy-in, the eye-rolls at the word “rollout” as resistance to change itself. It wasn’t. It was exhaustion from a team that had said yes so many times in a row that they had nothing left to give the next ask, even a good one.

The signs are quieter than you’d think

• Compliance without engagement — people do the new thing, but nobody asks questions or offers improvements anymore.
• A rise in “we tried that already” even when this time is genuinely different.
• Longer gaps between an initiative launching and it actually being followed consistently.
• Your best people, the ones who usually champion change, going quiet instead.

Capacity is a real constraint, not a soft one

We plan around machine capacity constantly — throughput, changeover time, maintenance windows. We rarely plan around a team’s capacity to absorb change, even though it’s just as real a constraint. Every initiative has a cost in attention and trust, and that budget isn’t infinite just because the initiatives themselves are individually reasonable.

What actually helped

We started explicitly sequencing change instead of parallel-launching it, finishing one initiative — including the follow-up and reinforcement, not just the kickoff — before starting the next. We also started asking the team directly: “Realistically, do we have room for this right now, or does something else need to wait?” That question alone changed the tenor of a lot of planning meetings, because it gave people permission to say what they’d been thinking anyway.

Change fatigue isn’t a sign your team is resistant to improvement. Usually it’s a sign you’ve been asking them to sprint without ever calling a rest interval, and the fix isn’t fewer good ideas — it’s more discipline about pacing them.