Early in my time as a Navy intelligence analyst, I watched a senior officer who had been one of the sharpest decision-makers in the command slowly stop making decisions. He didn't disappear. He attended every meeting, asked thoughtful questions, and offered careful input. But when it came time to call something, he redirected. "Let's loop in the J2." "Get me another look." "I want to see the pattern hold before we commit."

Nobody called it out. His evaluations were still strong. The team had simply learned to route around him.

I've seen that pattern in organizations at every level since then. A VP who used to be known for fast, clear direction starts hedging in senior staff meetings. A director who built a reputation for owning hard calls suddenly needs more stakeholders in the room before anything gets decided. The organization's first read is almost always the same: that leader has lost their edge.

The more diagnostic read is almost always different.

The Math Behind Withdrawal

Decision-making in genuinely uncertain environments carries a different risk profile than decision-making in predictable ones. When conditions are stable and feedback loops are short, the leader who calls something confidently and correctly gets credited. The leader who hedges gets passed over. That logic trains a generation of executives to perform certainty as the price of advancement.

In genuinely uncertain conditions, the same rules apply but the consequences shift. A call that might have been validated in 90 days now takes 18 months, and by the time the outcome surfaces the original context has changed, the decision has been revised twice, and the causal link between judgment and result is impossible to isolate. The leader who swung confidently and wrong absorbs a visible failure. The leader who deferred and distributed accountability absorbs almost nothing.

Most senior leaders are smart enough to run that calculation without running it consciously.

What the Accountability Structure Is Actually Rewarding

The accountability structures most large organizations use were designed for environments where outcomes were more predictable. They penalize visible failures and largely ignore the invisible cost of deferred decisions. A VP who makes a high-conviction call that lands badly shows up in the postmortem. A VP who spent six months routing decisions through committees, delaying a product launch by two quarters, rarely shows up anywhere.

The organization that punishes the wrong call faster than it can validate the right one has trained its leaders to stop calling.

When the environment shifts toward sustained uncertainty and feedback loops stretch, the rational response for a leader who has internalized those rules is withdrawal. Not dramatic withdrawal — visible withdrawal would itself be penalized. The subtler version: staying present, staying active, and quietly stopping the practice of actually deciding. Calendars fill with meetings that defer rather than resolve. Decisions accumulate in the space between stakeholders. Teams interpret the silence as a delegated authority they don't actually have.

What Organizations Misread

HBR published a March 2026 piece that named this phenomenon directly: leaders are feeling their sense of agency erode and beginning to withdraw from the emotional labor of deciding. The response in most leadership development circles has centered on building resilience, strengthening tolerance for uncertainty, reframing the leader's relationship with risk. That framing is not wrong. It is incomplete.

The question of why a formerly decisive leader is going quiet is partly about the individual. Mostly it's about the environment. Organizations that built their leadership culture around rewarding confident calls in conditions that no longer exist have created a structural mismatch. They're asking leaders to perform the same way in a fundamentally different game while keeping the same penalty structure for visible failure.

The leader who withdraws is responding accurately to an environment that has made decisiveness expensive without making hesitation cheap. That is a system design problem. Prescribing mindset coaching to a system design problem tends to produce leaders who are better at talking about uncertainty while still not deciding.

The Diagnostic Question Worth Asking

When a formerly decisive VP goes quiet in your senior team meetings, the first question is not what happened to them. It's what your environment stopped rewarding. That means looking at the actual consequences when a confident call goes wrong: how quickly the failure becomes public, what the postmortem looks like, whether the leader who made it is protected or exposed, and whether the leader who deferred it avoids accountability entirely.

It also means making the cost of non-decision visible. Most organizations have no disciplined way to track decisions that weren't made and the downstream damage of deferral. A wrong call shows up. A slow call disappears into the general friction of organizational life. Until the accountability structure treats those two things with comparable seriousness, the incentive to withdraw stays intact.

Some of the clearest decision-making I encountered in my time in intelligence happened in environments where the feedback was fast and the cost of deferral was immediate. That combination didn't make decisiveness effortless. It made it possible. If you want decisive leaders, the prior question is whether your environment has been built to support them.