An uncomfortable but necessary insight into how organizations systematically exhaust their best people
Most leaders do not set out to exhaust their best people. In fact, the opposite is usually true. They invest in talent, create opportunities, and rely on their strongest performers to carry critical work forward. From a distance, the system appears to reward capability and commitment.
And yet, in many organizations, it is precisely those high performers who begin to show the earliest signs of strain. They take on more, respond faster, absorb ambiguity, and step in when gaps appear. Over time, their calendars compress, their decisions accelerate, and their margin disappears. What begins as trust becomes dependence.
This is rarely framed as a leadership problem. It is often interpreted as a capacity issue, a resilience gap, or simply the cost of operating at a high level. But if you observe closely, a different pattern emerges. Exhaustion is not randomly distributed. It concentrates around the same people—and follows the same conditions.
The issue is not effort. It is reinforcement. The system consistently teaches who should absorb pressure, how quickly priorities can shift, and whether recovery is expected or optional. And people adapt accordingly.
The Misunderstanding: We Reward Commitment, But Reinforce Depletion
In many organizations, one assumption quietly shapes leadership behavior:
- Myth: “Our best people can handle more, so giving them more is how we move faster.”
- Reality: The system relies on its strongest contributors to absorb structural gaps, not just deliver outcomes.
- When the two conflict: What is framed as trust becomes over-reliance, and over time, capability turns into exhaustion.
People do not burn out because they are weak. They burn out because they are repeatedly placed in positions where saying “yes” is easier than challenging the structure. When contribution is consistently met with more demand—but not with clearer boundaries or rebalanced expectations—the signal becomes clear: availability is what is valued.
Lived experience overrides intent. Leaders may believe they are empowering their best people. The system teaches something else.
Exhaustion as a Design Outcome
Exhaustion is not simply a workload issue. It is a pattern created through repeated moments where decisions about time, attention, and expectations are made—often implicitly.
These moments function as signals. They indicate:
- Who carries additional load
- How often priorities can change
- Whether boundaries are respected
- Whether recovery is designed into execution
A signal is not a communication. It is a consequence-bearing interaction. It teaches behavior because it shapes what is rewarded, expected, or tolerated.
When these signals repeat, they form a pattern. And patterns create conditions. Over time, exhaustion becomes not an exception, but a predictable outcome of how the system operates.
1) The Availability Reward Trigger
This trigger forms when responsiveness becomes the primary indicator of value. People who reply fastest, take on more, and remain constantly reachable are seen as dependable. Over time, availability replaces effectiveness as the visible measure of contribution.
In a global consulting team, a senior manager becomes known for “always being there.” She responds to late-night messages, joins calls across time zones, and steps in whenever deadlines tighten. During a leadership review, a partner comments, “We can always rely on her when things get intense.”
The recognition is genuine. The pattern is reinforcing.
Over the next six months, her workload increases—not through formal allocation, but through expectation. Others begin routing urgent requests to her. She becomes the default escalation point. No one explicitly assigns this role. It emerges.
Her performance remains high. Her energy does not.
What this teaches: The system begins to associate value with responsiveness rather than sustainability. Others observe and adjust:
- Fast response becomes safer than thoughtful pacing
- Boundaries appear as reduced commitment
- Saying no carries social cost
Availability becomes the path to recognition—and exhaustion follows.
A small practice that shifts it (60 seconds): When acknowledging contribution, separate outcome from availability: “I value the impact you delivered here—and I also want to make sure we’re not building this on unsustainable responsiveness.”
This reframes what is being recognized. It signals that effectiveness includes how work is sustained—not just how quickly it is absorbed.
Boundary: Availability is sometimes necessary. The shift is not to reduce responsiveness, but to avoid making it the primary signal of value.
2) The Endless Reprioritization Trigger
This trigger emerges when priorities shift frequently without explicit closure or trade-offs. Work is not removed—it is layered. Each new direction is valid. The accumulation is the issue.
In a technology organization, the Head of Product introduces a revised roadmap during a quarterly planning cycle. Two weeks later, a strategic opportunity leads to another adjustment. A month later, customer feedback triggers a third shift.
Each decision is reasonable in isolation.
In execution, teams begin restarting work streams. Initiatives are paused without being formally closed. Engineers carry partial progress across multiple directions. Meetings increasingly focus on “realigning” rather than progressing.
High performers compensate by working longer hours to keep pace with shifting expectations.
No one is explicitly overloaded. The system is.
What this teaches: The system signals that direction is fluid but accountability remains fixed:
- Work accumulates even when priorities change
- Closure is less visible than initiation
- Adaptation is expected without structural relief
Over time, people stop relying on stated priorities. They rely on momentum—and absorb the cost.
A small practice that shifts it (90 seconds): When introducing a new priority, state the removal explicitly: “To take this on, we are stopping or pausing X. Let’s name what will not move forward this cycle.”
This creates visible trade-offs. It converts change from addition into reallocation.
Boundary: Flexibility is essential in dynamic environments. The risk lies in shifting direction without rebalancing load.
3) The Invisible Recovery Trigger
Recovery is rarely designed into execution. It is assumed to happen naturally—after delivery, after milestones, or “when things calm down.” In practice, it is often deferred indefinitely.
A transformation program reaches a major milestone after months of intense work. The leadership team acknowledges the effort: “Great job pushing through. This was critical.”
Within the same meeting, the next phase is introduced. The timeline is tight. Momentum is emphasized.
There is no pause. No recalibration. No redistribution of load.
The team transitions directly into the next cycle—carrying fatigue forward.
What this teaches: The system signals that recovery is secondary to continuity:
- Completion leads immediately to new demand
- Effort is recognized, but not structurally absorbed
- Sustained intensity becomes the norm
Over time, energy is treated as renewable. It is not.
Recommended by LinkedIn
Why So Many Capable Leaders Are Struggling Right Now
Jess Bridge 2 months ago
How to Expand your Capacity to Optimize your Leadership
Jamie Shapiro, PhD 4 months ago
Why Leaders Fail: Understanding the Common Pitfalls
Rahul Chatterjee 1 year ago
A small practice that shifts it (60 seconds): At the close of a major effort, insert a reset decision: “Before we move forward, what needs to stabilize? What do we stop, defer, or redistribute to protect sustainability?”
This introduces recovery as part of execution—not an afterthought.
Boundary: Recovery does not require long pauses. It requires intentional rebalancing.
4) The Silent Capacity Assumption Trigger
This trigger operates when leaders assume capacity without making it explicit. Work is assigned based on urgency or importance, without recalibrating what people are already carrying.
During a leadership meeting, a director asks a high-performing team lead to take on an additional initiative. “You’re the best person for this,” she says.
The team lead agrees.
No one asks what this displaces. No one reviews existing commitments. The assumption is that capacity will adjust.
Over time, the team lead begins delegating less effectively—not because of skill, but because oversight time disappears. Quality starts to fluctuate. Stress increases. The signal is internalized: competence leads to accumulation.
What this teaches: The system equates capability with expandable capacity:
- Strong performers are expected to absorb more
- Trade-offs remain implicit
- Saying “I’m at capacity” becomes difficult
The result is uneven load distribution—and silent strain.
A small practice that shifts it (60 seconds): When assigning work, include a capacity check: “If you take this on, what needs to come off your plate?”
This makes capacity visible. It legitimizes rebalancing.
Boundary: Leaders must still assign critical work. The shift is to surface the cost explicitly.
5) The Recognition of Sacrifice Trigger
Recognition shapes behavior more precisely than intention. When sacrifice—long hours, personal trade-offs, constant availability—is praised, it becomes a model for success.
In a leadership town hall, a senior executive highlights a team that “went above and beyond,” working late nights to deliver under pressure. The story is compelling. It receives applause.
What is not mentioned is why the pressure existed—or how it could be avoided next time.
In subsequent cycles, similar behavior appears across teams. Not because it is required—but because it is what gets seen.
What this teaches: Recognition reinforces effort patterns:
- Sacrifice becomes a visible path to appreciation
- Prevention and planning remain invisible
- Sustainability loses status
Over time, people align with what is celebrated—even when it is costly.
A small practice that shifts it (60 seconds): When recognizing performance, name the sustainable behavior: “I want to highlight not just the result, but how this was delivered—through early alignment, clear prioritization, and disciplined execution.”
This shifts attention from sacrifice to design.
Boundary: Extra effort deserves recognition. The risk is when it becomes the dominant signal.
Systemic Synthesis
These triggers do not operate in isolation. They reinforce each other.
Availability leads to increased assignment. Reprioritization increases workload accumulation. Lack of recovery sustains pressure across cycles. Capacity assumptions concentrate load. Recognition amplifies the pattern.
Together, they form a system where exhaustion is not an anomaly—it is a predictable outcome.
Leaders do not need to intend this. They only need to repeat these signals.
And repetition creates conditions.
The Takeaway
Exhaustion is not primarily a resilience issue. It is a design issue.
Not at the level of individual tasks, but at the level of recurring moments where expectations are set, reinforced, and repeated. The question is not whether people are working hard. It is whether the system requires them to work in ways that are structurally unsustainable.
A more useful question for leaders is this: Where in our system is effort being rewarded without being rebalanced?
Because that is where exhaustion begins. And it does not require a large intervention to change it. It requires a shift in how a few critical moments are handled—consistently.
Mini-Exercise: Your Exhaustion Signal Scan (7 minutes)
Think about the past two weeks.
- Who took on additional work—and why them?
- When priorities shifted, what was explicitly removed?
- Where did recovery actually occur?
- Who is consistently the fastest to respond—and what follows?
- What behavior received the most visible recognition?
Circle the pattern that appears most often. That is where the system is teaching exhaustion.
Executive Reflection (for the week ahead)
Before your next set of decisions, consider what people will experience—not what you intend.
When you assign work, what signal are you sending about capacity? When priorities shift, what are people expected to absorb? When effort is recognized, what behavior are you reinforcing?
Then test one small shift deliberately. Because exhaustion does not happen suddenly. It is built—moment by moment—through what leaders make normal.
References
- Schein, E. H. Organizational Culture and Leadership
- Edmondson, A. C. The Fearless Organization
- Heath, C. & Heath, D. Switch: How to Change Things When Change Is Hard
- Coyle, D. The Culture Code
- Weick, K. Sensemaking in Organizations
- Kahneman, D. Thinking, Fast and Slow
