Change Isn’t the Project Anymore. It’s the Job.

For most of business history, “leading through change” meant a discrete event — a merger, a reorg, a new system rollout — with a beginning, middle, and end. That’s no longer the operating environment most senior leaders are in. New tools, shifting regulations, restructured teams, and evolving customer expectations are now arriving continuously, often overlapping. There isn’t a “before and after” anymore — there’s just an ongoing state of adjustment.

A short check on where you actually stand

• Do you find yourself waiting for things to “settle down” before tackling certain priorities — and has that wait now stretched well past a year?
• When a new change lands, is your team’s default reaction fatigue rather than curiosity?
• Do you notice yourself under-communicating about change because you’re tired of explaining “another one,” even though your team probably needs more communication, not less?
• Have you stopped distinguishing between changes that genuinely matter and ones that are just noise — treating everything with the same, exhausted level of urgency?
• Is your own resilience the thing quietly running lowest, even as you focus on everyone else’s?

The problem is the model, not the organization

If several of these are true, the issue isn’t that your organization is unusually chaotic. It’s that the old mental model — change as an occasional project — doesn’t fit the current reality, and running that old model on a new environment is exhausting everyone, starting with you.

What the leaders handling this well actually do

They have stopped trying to get to “stable” and instead built genuine capacity for continuous change: clearer prioritization about what actually matters this quarter, more frequent — not less frequent — communication, and, critically, their own regulation, since teams take their emotional cues about how alarming a change is directly from how their leader reacts to it.