Why Your Resilient Team Is Actually Just Exhausted The System Design Gap Leaders Miss

The Endurance Trap

Laker and Kalyuzhnova identify a pattern that will sound familiar to anyone who has worked in a modern organization. When teams face pressure, certain individuals step up. They work longer hours, take on additional responsibilities, and somehow keep projects moving forward. Managers, seeing this dedication, interpret it as evidence of a resilient team. They may even hold up these individuals as role models, inadvertently setting an unsustainable standard.

But this interpretation fundamentally misunderstands what is happening. The team is not demonstrating resilience; it is demonstrating endurance. The difference is not semantic. Endurance is about continuing despite adverse conditions. Resilience, properly understood, is about creating conditions where those adverse circumstances do not overwhelm the system in the first place.

Consider the healthcare sector during the COVID-19 pandemic. Healthcare workers were widely and deservedly praised for their resilience. They showed up day after day, dealing with unprecedented patient loads, inadequate protective equipment, and emotional trauma. Yet two years into the pandemic, the healthcare industry faced a crisis of departures. Nurses, physicians, and support staff left the profession in record numbers. What looked like resilience was actually unsustainable endurance, and the system eventually broke.

Research by Christina Maslach and Michael Leiter on workplace burnout provides crucial context here. Their work identifies six areas of work life that, when misaligned, create burnout: workload, control, reward, community, fairness, and values. Critically, their research shows that burnout results from systemic workplace factors, not individual weakness or lack of resilience. When organizations respond to burnout by telling employees to be more resilient, they are treating a systems problem as an individual failing.

This matters because the solutions are entirely different. An individual-focused approach suggests meditation apps, resilience training, and wellness programs. These interventions are not harmful, but they are insufficient when the underlying system continuously generates excessive strain. A systems-focused approach examines workload distribution, decision-making authority, recognition systems, and organizational culture.

Designing for Absorption, Not Recovery

The article's most valuable contribution is its practical framework for building system-level resilience. Rather than asking how to help people recover faster, leaders should ask how to design work so that recovery is routine rather than reactive.

Building Recovery into Workflows

The first principle is building recovery into workflows. This goes beyond simply encouraging people to take vacation. It means structuring work cycles with intentional decompression periods after intense efforts. Basecamp, the project management software company, provides an instructive example. The company maintains a strict 40-hour workweek, with no expectation of overtime. During summer months, they shift to a 32-hour, four-day workweek. Founder Jason Fried argues that this is not generosity but intelligent business design: sustained creative output requires regular recovery.

Critics might argue that such approaches work for profitable software companies but not for organizations facing competitive pressure. Yet research on recovery from work stress by Sabine Sonnentag shows that psychological detachment, relaxation, and control during off-work time directly predict performance and well-being. Organizations that fail to build in recovery are not pushing harder; they are running their human capital into the ground.

Distributing Strain Across the System

The second principle is distributing strain across the system. In most organizations, a small cadre of dependable employees becomes the de facto safety net. When something urgent arises, these are the people managers call. Over time, this creates a dangerous concentration of institutional knowledge and workload. If one of these key people leaves, becomes ill, or finally burns out, the organization faces a crisis.

The solution is building genuine redundancy through cross-training, rotating responsibilities, and decentralizing authority. Southwest Airlines provides a useful model here. The company cross-trains employees across multiple roles, allowing flexibility in operations without requiring excess headcount. When demand spikes or challenges arise, the system can absorb the strain without placing impossible burdens on specific individuals.

Weick and Sutcliffe's research on high-reliability organizations provides additional insight. Organizations like aircraft carriers and nuclear power plants, where failure can be catastrophic, build resilience through structural characteristics: mindfulness about operations, deference to expertise regardless of hierarchy, preoccupation with potential failures, reluctance to simplify interpretations, and sensitivity to operations. These are system-level characteristics, not individual traits.

Rewarding Prevention Over Firefighting

The third principle is rewarding prevention over firefighting. Organizational cultures often celebrate heroes who save the day after things go wrong. The employee who works all night to recover from a system failure gets recognized. The employee who quietly improved the system so the failure never occurred often goes unnoticed.

This creates perverse incentives. Employees learn that crisis response is valued and rewarded, while prevention is invisible. Over time, organizations can inadvertently select for crisis-prone operations because those operations create opportunities for heroism. Toyota's production system offers a counterexample. The andon cord system allows any employee to stop the production line if they identify a problem. Rather than celebrating those who work around defects, Toyota celebrates those who prevent defects from propagating.

Leadership Behaviors That Enable System Resilience

Laker and Kalyuzhnova emphasize that resilient systems require leaders who model different behaviors. This is not simply about what leaders say, but what they demonstrate through their actions.

Modeling Boundaries

Modeling boundaries is perhaps the most critical leadership behavior. When leaders send emails at midnight, work through weekends, and take calls during vacation, they send a powerful message about expectations regardless of what official policies state. Microsoft's transformation under CEO Satya Nadella illustrates the power of leadership modeling. Nadella explicitly shifted the company culture from a competitive, always-on environment to one emphasizing learning, collaboration, and work-life integration. This was not just rhetoric; it required leaders throughout the organization to demonstrate these values through their behavior.

Celebrating Foresight

Celebrating foresight rather than heroics requires active attention. Leaders must notice and recognize the quiet work that prevents problems. This means tracking leading indicators, not just lagging ones. It means asking in project retrospectives not only what went wrong and how teams recovered, but what potential problems were avoided and how.

Sharing Control

Sharing control addresses a fundamental tension in organizational life. Centralized decision-making creates bottlenecks and concentrates stress on senior leaders. Yet distributing authority requires trust and carries risks. Research on organizational resilience suggests that organizations facing unpredictable environments benefit from distributed decision-making. When circumstances change rapidly, waiting for centralized approval creates dangerous delays.

Protecting Slack

Protecting slack may be the most counterintuitive principle in an era focused on efficiency and lean operations. Slack refers to excess capacity: extra time in schedules, additional budget, or headcount above minimum requirements. From an efficiency perspective, slack is waste. From a resilience perspective, slack is what allows a system to absorb unexpected shocks without breaking.

The creative industries understand this instinctively. Orchestras have understudies. Film productions build buffer time into schedules and reserve contingency budgets. Publishers plan for some books to fail. These are not inefficiencies but recognition that unpredictability is inherent to the work. Corporate leaders, particularly those under pressure from financial markets to maximize efficiency, resist building slack. Yet research on high-reliability organizations shows that some redundancy is essential for sustained performance under uncertainty.

The Counterarguments Merit Consideration

Any argument worth making faces legitimate counterarguments, and the case for system-level resilience is no exception.

Antifragility Argument

Nassim Taleb's concept of antifragility suggests that some stressors make systems stronger. Taleb argues that overprotecting against small stressors can leave systems vulnerable to large shocks. Applied to organizations, this suggests that some pressure and challenge may be beneficial for developing capability.

This argument has merit but does not invalidate the core thesis. The issue is not whether any stress is bad, but whether chronic, unrelieved pressure that requires constant heroic effort is sustainable. An organization can provide appropriate challenges while still building in recovery, distributing load, and preventing crisis from becoming the norm. The goal is not to eliminate all stress but to prevent the accumulation of stress that leads to burnout.

Competitive Reality

A second counterargument focuses on competitive reality. In highly competitive industries, the argument goes, organizations that build in slack and limit work hours will be outcompeted by those willing to push harder. This argument appears pragmatic but often rests on a false short-term versus long-term tradeoff.

Research on productivity and work hours shows that sustained long hours actually decrease output due to increased errors, reduced creativity, and eventual burnout. The organizations that appear to be working harder may simply be working less efficiently. Moreover, in knowledge work where creativity and judgment matter, exhausted employees make poor decisions that create downstream problems.

Temporary Intense Efforts

A third counterargument acknowledges that some situations genuinely require temporary intense effort. A product launch, merger integration, or response to competitive threat may demand extraordinary work for a limited period. Does the focus on system resilience adequately account for these realities?

The key distinction is between exceptional temporary intensity and chronic overwork. A resilient system can handle periodic spikes precisely because it builds in recovery between them. An endurance-based system treats every week as a crisis, leaving no capacity for actual emergencies. When everything is urgent, nothing is urgent.

Implementation Challenges and Solutions

Translating these principles into practice faces real obstacles. The most significant is often the performance measurement system. If organizations measure and reward individual output without considering sustainability, they will select for endurance over resilience.

Redesigning Evaluation Systems

Consider how organizations typically evaluate employees. Individual performance reviews assess deliverables and outcomes but rarely consider whether those results came at sustainable cost. An employee who delivers exceptional results while working 70-hour weeks and burning out their team may receive the same or better rating than an employee who delivers strong results sustainably.

Redesigning evaluation systems to account for sustainability requires new metrics. Organizations might track team retention rates, recovery time after major projects, or distribution of after-hours work. They might explicitly evaluate managers on how effectively they develop redundancy and distribute strain. None of these metrics are perfect, but they signal what the organization truly values.

Building Redundancy

A second implementation challenge is the time and cost required to build redundancy. Cross-training employees takes time away from immediate productivity. Maintaining buffer capacity costs money. Organizations facing financial pressure may view these investments as unaffordable.

Yet research suggests this framing is backwards. The costs of burnout are substantial: recruitment and onboarding costs when employees leave, productivity losses from disengaged workers, and errors from exhausted employees. Organizations that view system resilience as a cost may be ignoring the hidden costs of endurance-based operations.

Cultural Change

A third challenge is cultural. Many organizations have deep-rooted cultures that celebrate overwork, view long hours as dedication, and treat boundaries as lack of commitment. Changing these cultures requires consistent leadership action over time, not just policy changes.

The Diagnostic Question

Laker and Kalyuzhnova offer a simple but powerful diagnostic: Did our systems protect people, or did people protect the system? This question cuts through organizational rhetoric to reveal what is actually happening.

When a project succeeds because a few people worked unsustainable hours, people protected the system. When a crisis is averted because someone noticed a problem early and had the authority to address it, the system protected people. When a team delivers strong results within normal working hours because workload is well-distributed, the system protected people.

Organizations should ask this question regularly: after project completions, during retrospectives, and in performance evaluations. The pattern of answers reveals whether resilience is real or rhetoric.

Leaders can conduct a simple audit by examining the last several major projects or challenges. For each, identify what made success possible. Was it heroic individual effort? Improvisation under pressure? Or was it well-designed processes, adequate resources, and distributed capability? The honest answers to these questions reveal organizational reality.

Building Resilient Organizations for the Long Term

The shift from endurance to resilience requires fundamental changes in how leaders think about organizational capability. Rather than viewing people as resources to be fully utilized, resilient organizations view people as complex systems that require maintenance, recovery, and investment.

This shift has implications for strategy, organizational design, and leadership development. Strategically, it means being realistic about organizational capacity and building timelines that account for sustainable work. It means sometimes saying no to opportunities because the organization lacks the capacity to pursue them sustainably.

For organizational design, it means building redundancy and flexibility into structures rather than optimizing purely for efficiency. It means creating roles and career paths that value prevention and system improvement, not just crisis response and visible heroics.

For leadership development, it means selecting and training leaders who can build sustainable high performance, not just drive short-term results. It means evaluating leaders not just on what their teams deliver, but how sustainably they deliver it.

The argument Laker and Kalyuzhnova make is ultimately about organizational sustainability. Organizations can run on endurance for some time, sometimes for years. Dedicated employees will push themselves beyond reasonable limits, especially if they believe in the mission or fear the alternatives. But endurance has limits, and when it runs out, the consequences are severe: talent exodus, degraded performance, damaged reputation, and organizational crisis.

The strongest organizations are not those with the most resilient individuals but those with the most resilient systems. These organizations design work to be sustainable. They build in recovery, distribute strain, prevent crises rather than celebrate recovery from them, and protect the capacity to absorb unexpected shocks. Their leaders model boundaries, celebrate foresight, share control, and protect slack.

Most importantly, these organizations measure success not by how quickly people bounce back from burnout, but by how rarely burnout occurs in the first place. They understand that resilience is not about recovering faster; it is about needing to recover less often. That distinction, simple as it sounds, represents a fundamental reimagining of what high-performing organizations look like.

For leaders reading this and recognizing their organization in the endurance pattern, the path forward requires honesty and courage. Honesty to acknowledge that what has been called resilience may actually be unsustainable endurance. Courage to make the structural changes necessary to build true resilience, even when those changes feel inefficient or slow in the short term.

The organizations that make this shift will be stronger, more adaptable, and more capable of sustaining high performance over time. Those that do not will eventually face the consequences of running their most valuable asset into the ground. The choice, ultimately, is not whether to build resilient organizations, but whether to do so proactively or learn the hard way after the talent walks out the door.

Learn more about building resilient organizations from the insightful perspectives of Laker and Kalyuzhnova in the MIT Sloan Management Review.