Executive Burnout Is Not a Burnout Problem

On operating system drag... and what HBR, McKinsey, and CNBC named without naming.

Strategy is downstream of physiology. Behavior is downstream of identity. Output is downstream of architecture.

In the past six weeks, the business press has done something it has not done before. It has stopped pretending that executive burnout is a personal failing.

On May 5, CNBC ran Executives are burning out, just like their employees and they don’t know how to handle it.

In March, Harvard Business Review published Merete Wedell-Wedellsborg’s Leaders Feel Their Agency Eroding and They’re Starting to Withdraw, naming a phenomenon she calls psychological withdrawal: leaders becoming more rigid, more reactive, more black-and-white in their thinking.

Leaders pulling back from decision-making and from the belief that their effort still matters. Two weeks later, HBR ran Daisy Auger-Domínguez’s Burnout Looks Different Across the Org Chart, locating executive burnout in value conflicts and moral strain. McKinsey’s data underwrites the alarm: seventy-one percent of CEOs reported burnout this year.

This is a category being named in real time.

What is missing in every one of those pieces is the layer underneath. The mechanism that is actually generating the symptoms.

The conventional reading is that burnout is a workload problem. The mainstream reading, post-2024, is that it is a systems problem: unclear priorities, misaligned incentives, poor decision structures. Both are true. Neither is sufficient.

Because the same workload, in the same broken system, produces wildly different outcomes in two different leaders. The CFO who absorbs three quarters of board volatility without losing decision velocity, and the CFO who absorbs one and starts re-reading her own emails at 4pm, are not running different calendars. They are running different operating systems.

What HBR has named psychological withdrawal is one of three observable surface signatures of a single underlying mechanism. Decision fatigue, in McKinsey’s language, is another. Moral strain, in Auger-Domínguez’s reading, is the third.

I have spent the last decade observing the architecture of leadership performance. What I see, repeatedly, is this: by the time an executive is exhibiting psychological withdrawal, the work is not happening at the level of stress. It is happening at the level of identity. The leader is producing the same outputs that were once aligned with who they were and the body has started to register the cost of producing them as someone they are no longer fully aligned with.

I call this operating system drag.

It is the cumulative cost of running yesterday’s identity code in today’s role. The drag of the mismatch between the self the calendar still belongs to and the self the body has already become. Every meeting, every decision, every late-night Slack reply gets metabolized twice: once by the executing self and once by the self that is half-translating, half-protecting, half-deciding the answer that finally goes out. The result reads as fatigue. It is, mechanically, friction.

This is not a metaphor.

The framework I have built around it Human Technology Architecture™ (HTA) names four layers in any leader’s internal operating system:

1.  Nervous System Regulation. the hardware layer. Where most of the wellness industry now lives.

2.  Identity Structure. the code layer. The structural self underneath the behavior.

3.  Coherence Integration. the software update, where identity, values, behavior, and nervous system align.

4.  The HTA™ Container. the complete system. The internal OS upgrade.

The current vocabulary in the business press, nervous system regulation, somatic leadership, resilience, is operating almost entirely at Layer 1. Which is necessary, and which is welcome. But it is not where the drag lives. The drag lives at Layer 2.

You can regulate a nervous system perfectly and still be exhausted, because the nervous system you are regulating is loyal to an identity the calendar has already outgrown. Regulation reduces the volume. It does not change the song.

This is why the offsite doesn’t last past Thursday. It is why the executive coach who taught your CEO breathwork did not save the board moment three quarters in. Insight, applied at Layer 1, cannot reach Layer 2.

It is also why the psychological withdrawal HBR named is not, in fact, withdrawal from leadership. It is withdrawal from a version of leadership the leader’s internal operating system has outgrown but that the internal architecture has not yet authorized them to leave.

Withdrawal looks like disengagement. Underneath, it is grief. For the version of the leader the role was designed for, and that the body has already moved past.

Executive burnout is not a burnout problem. It is operating system drag.

Until the business press names that layer, every intervention sold into the C-suite is going to keep doing what it has been doing since 2020: produce a Wednesday breakthrough and a Thursday regression, and a quarterly retreat that fills the journal and not the calendar.

If you are running a portfolio company, a board, a CHRO function, or your own founder seat, the work that matters in 2026 is not at the nervous system layer.

It is one layer down…

Erem Latif is an Executive Advisor, the author of Live Engaged, and the creator of the Human Technology Architecture™ framework. She is the founder of Engagement Lab and runs enterprise-level and individual leadership programs. The Coherence Check-In, an individual diagnostic underneath this work, is available at here.