Why Some Organizations Absorb Shocks and Others Break

Resilience Is Not the Same as Strength

The most common mistake leaders make about resilience is confusing it with strength. A strong organization is one built to resist: efficient, optimized, hard to knock over by the pressures it was designed to handle. A resilient organization is one built to bend and reorganize when the pressure exceeds anything it was designed for. These are not the same property, and the pursuit of one routinely undermines the other. The leaner and more optimized an organization becomes, the less slack it holds, and slack is precisely what resilience runs on. This is why highly efficient organizations are so often surprised by their own fragility: they mistook the absence of visible waste for strength, right up until a disturbance they had not planned for arrived and there was nothing left to absorb it.

Hamel and Välikangas (2003) made the case bluntly: in a stable world, executives could treat their business model as more or less permanent and simply work to run it better. In a turbulent one, the imperative is not to get better but to get different, and continued success rides on the ability to reinvent models and strategies before circumstances force the issue. Resilience, in this framing, is not a defensive property at all. It is the capacity to keep reinventing while still operating, and organizations that cannot do this eventually meet a disturbance that their optimized, unchanging model cannot survive.

Coutu (2002), in a widely read practitioner treatment, identified three characteristics that resilient people and organizations tend to share: a sober acceptance of reality rather than the optimism that denial produces, a deep sense of meaning or purpose that holds them together under strain, and an ability to improvise with whatever is at hand. The first is worth dwelling on, because leaders often mistake resilience for relentless positivity. The evidence points the other way. Organizations that face hard facts squarely, without flinching and without pretending a disturbance is smaller than it is, respond faster and more effectively than those whose culture rewards optimism and punishes the bearer of bad news. Resilience begins with the willingness to see clearly, and cultures that make it costly to name problems are quietly undermining the first condition of it.

There is also a bottom-line case that resilience is not a soft virtue but a measurable performance advantage. Ortiz-de-Mandojana and Bansal (2016), tracking matched pairs of firms over fifteen years, found that firms with stronger social and environmental practices, a proxy for the long-term orientation that builds resilience, showed lower financial volatility, higher sales growth, and better survival rates over the long run. Resilience did not show up in any single quarter; it showed up in the shape of performance across time and across disturbances. That is exactly why it is so easy to underinvest in: its costs are immediate and visible, and its benefits are delayed, probabilistic, and invisible until the day they are not.

The Threat-Rigidity Trap

Here is the most important and most uncomfortable finding in the resilience literature: under threat, organizations reliably do the opposite of what resilience requires. Staw et al. (1981) documented what they called the threat-rigidity effect, a pattern so consistent it holds at the individual, group, and organizational levels. When people perceive a serious threat, their information processing narrows, they fall back on well-learned habits, and control centralizes upward. Decisions that were distributed get pulled to the top. Experimentation stops. The organization does the familiar thing, harder.

This response is not stupidity; it is a deeply wired reflex, and it is sometimes right. If the threat calls for a known response executed fast and decisively, narrowing and centralizing helps. But most serious disruptions are serious precisely because they are unfamiliar, and unfamiliar disruptions call for exactly what threat rigidity suppresses: distributed judgment from the people closest to the problem, a willingness to try things that are not in the playbook, and the flexibility to abandon a response that is not working. The cruel logic is that the reflex fires hardest under the conditions where it does the most damage. The organizations that come through unfamiliar shocks best are not the ones that feel less threatened; they are the ones that have built structures and habits that counteract the rigidity reflex before it takes over.

You can see the reflex most clearly in how organizations handle bad signals. Long before a crisis becomes undeniable, there are usually anomalies: a metric drifting the wrong way, a customer complaint that does not fit the pattern, a near-miss that could have been much worse. In a fragile organization, the incentives run toward suppressing these signals, because surfacing them is uncomfortable and the person who raises them often pays a social cost. In a resilient one, small anomalies are treated as information and examined rather than explained away. Weick and Sutcliffe (2007), studying organizations that operate in genuinely unforgiving environments, found that what set the best apart was a near-obsessive attention to small failures and a refusal to simplify away signals that did not fit expectations. That vigilance is expensive, and most of the time it turns up nothing, which is exactly why organizations under efficiency pressure stop doing it, and exactly why they are surprised when the signal they stopped watching for finally mattered.

The Reserves That Actually Matter

When leaders think about weathering a downturn, they think about the balance sheet, and they are not wrong to. Financial slack—cash, low fixed costs, access to credit—buys the one thing a crisis takes away, which is time. An organization with reserves can wait, watch, and choose; an organization without them is forced into whatever action relieves the immediate pressure, which is rarely the wise action. But financial slack is only half the story, and it is the half that gets all the attention.

The other half is relational, and the clearest evidence for it comes from the airline industry after September 11, 2001, a shock that hit every U.S. carrier at once. Gittell et al. (2006) asked why some carriers recovered strongly while others struggled for years, and found that the answer was not size and not even the severity of the initial hit. Carriers that had built and preserved relational reserves—trust, shared goals, and mutual respect across employee groups—recovered better, in part because they avoided the deep layoffs their competitors reached for. And the study found something leaders should sit with: the layoffs that were supposed to speed recovery actually inhibited it, over a four-year horizon. Cutting people to protect the numbers spent a reserve that could not be quickly rebuilt, and the organizations that spent it recovered more slowly than the ones that found other ways through.

The pattern generalizes beyond airlines. DesJardine et al. (2019), studying firms through the 2008 global financial crisis, found that companies with stronger social and environmental practices experienced smaller losses and recovered faster, evidence that the investments organizations make in their relationships with employees, communities, and other stakeholders function as a buffer when a systemic shock hits. This is the practical meaning of the phrase "relationships are a reserve." They are accumulated in ordinary times, drawn down in hard ones, and—unlike a credit line—impossible to arrange in a hurry once the crisis has already begun. The leader who has spent years quietly depleting trust, treating people as costs to be minimized, discovers in a crisis that the reserve is not there, and there is no time left to build it.

It is worth being precise about where this reserve actually lives, because leaders often look for it in the wrong place. Lengnick-Hall et al. (2011) argued that an organization's capacity for resilience is not stored in a document, a contingency plan, or a rainy-day fund, but embedded in the knowledge, relationships, and routines of its people—in the cognitive, behavioral, and contextual competencies that, aggregated across the workforce, make a resilient response possible. This is why resilience cannot be bought quickly or bolted on when a shock arrives. A plan can be written in a week; the relationships and practiced judgment that let an organization actually execute under pressure take years to build and can be destroyed in a single round of panicked cost-cutting. When leaders treat their people primarily as a cost line, they are not just making a morale trade-off; they are spending down the very substance that resilience is made of, and they are usually doing it at the worst possible moment.

Building It Before You Need It

Because resilience is latent, it cannot be created once a crisis is underway; by then you are working with whatever you built beforehand. That is the bad news and, in a sense, the good news, because it means the work is doable in ordinary time, when there is room to do it well. Fiksel et al. (2015), writing for a practitioner audience, argued that organizations should treat resilience as a discipline to be built deliberately rather than a quality to be hoped for, learning to manage disruption as a normal condition rather than an exception. Several moves follow from the evidence, and none of them requires a crisis to justify.

The first is to build and defend slack in the places that matter. This runs against every efficiency instinct, and it should be done selectively rather than everywhere, but an organization with zero slack has traded away its capacity to absorb surprise. The relevant question for a leader is not "where can we cut," which the organization already asks constantly, but "where would we have no room to maneuver if something went wrong," which it rarely asks at all. Naming those points, and deciding deliberately how much buffer to hold at each, is resilience work.

The second is to push authority toward the people closest to the problem, and to do it before the crisis rather than during it. Because threat rigidity centralizes control automatically, the only reliable counterweight is a structure and a culture in which distributed decision-making is already normal, already trusted, and already practiced. An organization that centralizes everything in calm conditions will centralize even harder under threat, and will lose the distributed judgment it most needs. One that habitually trusts frontline judgment has a chance of keeping that judgment available when it counts.

The third is to make it safe and normal to surface bad news. Every organization says it wants candor; far fewer make it costless to deliver. The test is simple and behavioral: when someone raises an inconvenient anomaly or a problem that reflects badly on a decision leadership has already made, what happens to them? If the honest answer is that they pay for it, the organization has just taught everyone watching to keep the next weak signal to themselves, and it has weakened its own early-warning system in the process. Resilience depends on seeing reality clearly, and cultures that punish the messenger are blinding themselves. This is not an abstract cultural nicety; it is an operational capability with a measurable failure mode. Most large disruptions are preceded by a period in which the warning signs were present and available but were not acted on, not because no one saw them but because the people who saw them had learned that raising them was not worth the cost. Building the habit of surfacing and examining inconvenient information—deliberately, routinely, and without penalty—is one of the few resilience investments that also pays for itself in ordinary operations, because the same discipline that catches a looming crisis also catches the smaller problems that quietly erode performance in normal times.

The fourth is to actually learn from disruptions rather than merely surviving them. Duchek (2020) frames resilience as three stages—anticipating, coping, and adapting—and the last is the one organizations skip most often. It is tempting, once a crisis passes, to exhale and return to exactly how things were before. Organizations that do this stay exactly as vulnerable to the next disturbance of the same kind. The resilient move is to treat each disruption as expensive tuition already paid, and to insist on extracting the lesson: what did we miss, what worked, what routine needs to change so that this particular surprise is never again a surprise. Gilbert et al. (2012) observed that organizations facing disruption need both to defend the core and to build the new, and that the ones that manage the transition treat the disruptive episode as an occasion for reinvention rather than merely for defense.

None of this is exotic, and that is the point. Resilience is not a special reserve of heroism that some organizations happen to have. It is the accumulated result of ordinary choices—about slack, about where decisions get made, about whether people can tell the truth, about whether hard lessons get absorbed—made consistently in the long stretches between crises. The organizations that absorb shocks and the ones that break usually looked similar the day before the shock. What differed was the set of conditions each had been quietly building, or neglecting, in all the ordinary days that came before. Those conditions can be examined now, while there is still time to change them, which is the entire case for diagnosing resilience before the disturbance that would otherwise reveal it the hard way.