Transition Paralysis

A leadership change is underway and the whole organization has quietly stalled around it, one reasonable deferral at a time.

A leadership change is underway, and the organization has quietly stalled around it in ways that are only fully visible in retrospect. People are waiting to see who lands where, and in what role, before committing to anything that feels remotely permanent.

Decisions are getting deferred with a plausible, individually reasonable justification attached to each one: better to wait until the new structure actually settles, better to see what the incoming leader's priorities turn out to be before building a case for anything. Meanwhile the real work keeps accumulating behind all that reasonable-sounding uncertainty, and everyone involved is spending more energy managing the transition itself than doing the job the transition was supposed to eventually clarify.

A Hundred Reasonable Decisions, One Unreasonable Result

Deferring a single decision because leadership is currently in flux looks like straightforward good judgment in any individual instance you'd examine on its own. Strung together across every team making the same individually reasonable choice at roughly the same time, the aggregate is a full organizational stall dressed up convincingly as caution. Nobody sat down and decided to freeze the entire company. Every team independently decided their own particular piece could reasonably wait a little longer, and the sum of those individually defensible choices is an organization that has effectively stopped moving, without any single person having chosen that outcome.

The Freeze Outlasts the Transition Itself

The uncertainty that originally triggers this rarely resolves as cleanly or as quickly as the initial announcement seems to promise. Even well after a new leader has been formally named, people keep waiting anyway: for that leader's actual priorities to become clear beyond the announcement language, for the resulting reorg to genuinely settle rather than merely appear settled on paper, for the dust to actually finish rather than just look like it's finishing. By the time things genuinely stabilize, the organization has often lost several months it will never fully account for or recover, because none of the accumulated cost showed up as a single, visible, attributable failure anyone could point to. It showed up instead as a hundred small decisions that simply never happened, scattered across dozens of teams, none of them individually significant enough to raise an alarm.

Where the Stall Shows Up First

Initiatives are being described as "on hold pending the transition" with no defined resumption point attached. Open-ended deferral without a scheduled return date, rather than a genuinely temporary and bounded pause.

People are making real career and project decisions based on speculation rather than confirmed information. Positioning themselves for a leader who hasn't actually been named yet, or a structure that hasn't been formally announced, based on rumor and reasonable guesswork.

What's still actively moving is disproportionately the work that never required a new judgment call to continue. Genuine forward progress has narrowed almost entirely to whatever doesn't demand any fresh decision from anyone currently uncertain of their footing.

The Cost of Calling This Temporary

Leadership sometimes treats the freeze as something that will self-resolve without intervention: once the transition formally completes, normal operating tempo will simply resume on its own. That assumption treats deferral as though it has no habit-forming effect of its own, which turns out not to be true. The longer deferral remains the organizational default, the less automatically it reverses once the original justification for it has technically expired, because teams have by then built entire working rhythms around not deciding things.

Naming What Still Moves

There's no procedural checklist that substitutes for this specific step: someone with real standing, ideally the incoming leader, and as early in the process as genuinely possible, has to explicitly and specifically say what's still expected to keep moving during the transition and what's genuinely, deliberately on hold. Silence on this point gets read, reasonably, as implicit permission to defer everything indiscriminately. An explicit, specific list of what still needs to happen is the only thing that actually removes that cover for indefinite deferral.

If nobody has said out loud, recently and specifically, what shouldn't wait for the reorg to finish, that particular silence is doing the freezing, not the transition itself, and not the underlying uncertainty that triggered it.