Most organizations believe they are resilient. Most are wrong, not about the quality of their people, but about what resilience actually is.
The belief tends to hold until something disrupts it: a departure, a board priority shift, a compressed timeline, a key relationship that turns out to have been load-bearing in ways nobody mapped. At that point, the organization learns something it could have learned in a quieter moment. It learns whether its resilience lives in the design, or whether it lives in two or three people who have been quietly absorbing what the system was never built to hold.
That distinction, between resilience as a structural property and resilience as a personal one, is the central question this piece is concerned with. It is also, in my experience working with senior leaders across large organizations, one of the most consistently misread conditions in leadership architecture. The people are capable. The design is the problem. And because the people keep performing anyway, the design gap stays invisible until it isn’t.
What follows is a framework for reading that gap before a disruption makes it readable for you.
Why do most organizations confuse individual and organizational resilience?
There is a version of resilience that belongs to the leader: the capacity to stay grounded when the variables shift, to think clearly under pressure, to communicate with steadiness rather than reaction. It is real. It is worth developing. Across two decades of coaching executives, I have seen how consistently this individual capacity determines the quality of leadership in a crisis.
It is also not sufficient, and conflating it with organizational resilience is one of the more costly errors senior leaders make.
Organizational resilience is a design question. It asks: what has been built into the system such that disruption does not require heroics? When that question has a strong answer, the organization absorbs pressure without it accumulating entirely on the people at the top. When it doesn’t, the burden lands on individual leaders, and the organization calls that person’s resilience an asset rather than naming it as a gap in design.
The distinction matters for a specific reason. Individual resilience is depleting. It draws on finite reserves. A system that depends on one or two people absorbing disproportionate load will eventually face a reckoning: the resignation, the burnout, the quiet withdrawal that forces the question the organization was not designed to answer.
Organizational resilience, when it is genuinely built rather than assumed, does not deplete. It distributes. It means the system can respond to a disruption at the level where the disruption actually lives, rather than escalating every pressure to the most senior person available.
The organizations I work with almost always have capable, resilient leaders. What they frequently lack is the architecture that lets that capability do its work without extraction.
What are the signs that an organization has a resilience design gap?
Design gaps do not announce themselves. They reveal themselves through patterns that look like leadership problems until you examine the mechanism behind them.
The hero response. A disruption occurs and the organization recovers. From the outside, and often from the inside, this looks like resilience. What it actually represents, in most cases, is one or two people who absorbed a load the system was not designed to distribute. The outcome is positive. The mechanism is extraction. And extraction compounds: the people who carry the most are also the people most likely to leave, most likely to burn out, and most difficult to replace when they do. Organizations that rely consistently on the hero response are not resilient. They are one departure away from a structural crisis.
The escalation pattern. Decisions that should be resolved at one level of the organization consistently travel upward. Not because the people below lack the capability to resolve them, but because the operating model has never given them the clarity or authority to do so. This is worth distinguishing clearly from appropriate escalation, the decisions that genuinely require senior judgment because of their strategic weight, irreversibility, or cross-functional complexity. What I am describing is a different pattern: decisions that travel up not because they warrant it, but because the system offers no authorized route to resolution at the level where they live. The performance cost of this pattern is significant. Senior leaders spend decision bandwidth on questions that should not require them. The organization develops a learned helplessness that compounds over time. People stop trying to resolve things at their level because the system has consistently reinforced that the answer will come from above.
The lag that becomes a crisis. The organization responds to a known problem, but slowly enough that by the time it moves, the problem has compounded. What is often diagnosed as a speed problem is usually a structure problem. The lag is rarely about awareness. People often know what is happening before the formal escalation reaches the right level. It is almost always about the absence of decision rights that make a clear, authorized response possible without first convening a committee, building consensus, or waiting for the most senior person in the chain to weigh in. In organizations with strong load distribution, the window between a known problem and an authorized response is narrow. Not because people move faster, but because the system does not require a new alignment meeting every time conditions change.
These three patterns share a common structural feature: they all represent load that the organization is carrying as individual capacity rather than as designed capability. That distinction is the starting point for any serious structural assessment.
How do you run an organizational resilience diagnostic?
A structural diagnostic is different from a self-assessment. It is not asking how you are holding up under pressure. It is asking what the organization has been built to hold, and whether the current design matches the demands being placed on it.
The unit of analysis is the system, not the person. This shift matters because it changes what counts as a finding. A self-assessment might reveal that a leader is feeling overwhelmed. A structural diagnostic reveals whether the operating model is generating conditions that would overwhelm any leader placed in that role. The first is information about a person. The second is information about a design.
Three questions are worth running this week, at the level of your leadership team rather than in private reflection.
First: When a significant disruption occurs, which individuals are load-bearing? Count them. If the answer in any critical function is fewer than three people, meaning the organization’s capacity to absorb disruption in that area depends on a very small number of individuals, the organization is carrying resilience as a personal trait rather than distributing it as a design feature. The follow-on question is equally important: what happens to that function when one of those people is unavailable? If the honest answer is “we escalate to someone already overloaded” or “we slow down significantly,” the design gap is visible.
Second: Where do decisions go when they encounter ambiguity? Track this for a week with genuine rigor. If the consistent answer is upward, toward the most senior person in the room, the executive most likely to have a view, the leader who has historically resolved ambiguity by absorbing it, the organization may have strategic clarity without the decision rights to support it. That is a design gap, not a capability gap. Strategic clarity tells the organization where it is going. Decision rights determine whether the people who need to move can do so without first waiting for permission. You can have the former in abundance and still find the organization systematically unable to respond at the pace the environment requires.
Third: What is the lag between a known problem and an authorized response? This question is about measuring the distance between awareness and action in your operating model. In organizations with strong load distribution, that distance is narrow, not because people are heroically responsive, but because the system has been designed to authorize response at the level where the problem lives. If you find that the same problems recur because the people who first identify them do not have the authority to respond, or that the response consistently arrives after the optimal window has closed, the operating model is not designed to absorb what it is being asked to handle.
If any of these three questions surfaces a pattern, the work is not to find more resilient people. The work is in the design.
How do you build organizational resilience into the design?
Running a diagnostic is the starting point. The findings it surfaces point toward specific areas of design work. These are not prescriptions. Every organization’s architecture is different, and the sequencing of what to address first requires a full structural assessment of what is holding, what is overloaded, and where the highest leverage point sits. But the principles that guide the design work are consistent.
Distribute load before the disruption arrives, not in response to it. The hero response is so costly precisely because the load redistribution happens under pressure, when the people absorbing extra load are already stretched and the system is already under strain. Organizations that are genuinely resilient make deliberate decisions about load distribution in calm conditions: who else carries this knowledge, this relationship, this decision authority? Who is the backup that has actually been developed, not just named? The test is not whether a succession plan exists on paper. It is whether the people named in that plan have been given the conditions to actually exercise the relevant capability before they need to.
Match decision rights to the level where the decision lives. Most organizations make this error not through bad intent but through historical accretion: decisions that were once appropriate for senior sign-off because of their novelty or risk become routine over time, but the decision right never migrates down with them. A periodic audit of where decisions are being made versus where they could be made, given current capability, current information access, and current organizational priorities, is a structural investment with a significant performance return. The goal is not to push decisions down as an end in itself. It is to ensure that the decision rights and the decision-relevant information are held at the same level.
Build response capacity into the operating model, not into the schedule of the most senior person available. This is the hardest of the three, because it requires organizations to examine an assumption that is often deeply embedded: that senior leaders are the most reliable point of response in a crisis. They may be the most experienced. They are not always the most positioned. In organizations where response capacity has been genuinely distributed, a disruption in one function does not automatically require senior executive involvement to resolve. The function has the authority, the information, and the design to absorb it. Senior leaders are reserved for decisions that genuinely warrant their judgment, not as the default escalation point for anything that encounters ambiguity.
Where to start if the diagnostic surfaces a gap
The structural diagnostic described above is not a consulting engagement. It is a working session, something a leadership team can run in an afternoon with the right questions and the willingness to follow where the answers lead.
What makes it difficult is not the questions themselves. It is what the answers reveal: that some of what the organization has been calling resilience is actually something much more fragile, and that the people carrying the most load may have no visible way of saying so.
The most capable organizations I work with developed a habit of asking structural questions before disruptions made them unavoidable. Not because they anticipated every variable, but because they understood that resilience is not something a leader summons when conditions deteriorate. It is something an organization builds when conditions allow. The diagnostic is most valuable not when something has already broken, but when everything appears to be holding and there is still time to examine what it is holding on.
If this is the question you’re carrying, the monthly newsletter is where the thinking continues, one piece of structural insight per month, applied to the decisions senior leaders are actually navigating. Subscribe here.
For leadership teams ready to run a full structural assessment, strategy call applications are open.
Frequently asked questions
What is the difference between individual resilience and organizational resilience?
Individual resilience is a leader’s capacity to stay grounded, think clearly, and communicate steadiness under pressure. Organizational resilience is a structural property, what has been built into the system so that disruption does not require heroics from any one person. The two are related but distinct. An organization with highly resilient leaders can still have a significant organizational resilience gap if the design concentrates load rather than distributing it.
How do I know if my organization has a resilience design gap?
The clearest signals are patterns, not events. If disruptions consistently require one or two individuals to carry disproportionate load; if decisions routinely travel upward rather than resolving at the level where they live; or if the lag between a known problem and an authorized response is consistently long, these are design gaps, not capability gaps. The individuals in the system may be performing well. The structure around them is not.
Why do decisions keep escalating to senior leaders even when it isn’t necessary?
Usually because the operating model has never been designed to authorize resolution at the level where the decision lives. People escalate not because they lack the capability to resolve the issue, but because the system provides no legitimate route to resolution without senior sign-off. This is a decision rights gap. It is fixable through deliberate design, but requires an honest audit of which decisions actually warrant senior involvement versus which ones have simply accrued to senior leaders by default over time.
What is a structural diagnostic and how is it different from a leadership assessment?
A leadership assessment evaluates the individual, their capabilities, their style, their development needs. A structural diagnostic evaluates the system, the operating model, the decision rights architecture, the load distribution across the organization. The unit of analysis is different, and so is what counts as a finding. A structural diagnostic might reveal that a leadership team is performing well given the design they are working within, while the design itself is generating conditions that would limit any team placed in that situation.
Can organizational resilience be built without replacing people?
In most cases, yes. The gaps that undermine organizational resilience, concentrated load, absent decision rights, operating models that require escalation for routine ambiguity, are design features, not people failures. The leaders and teams I work with are typically capable. What they lack is the architecture that allows that capability to do its work. Building resilience into the system means examining and revising the design, not cycling through the people.
Where should a leadership team start if the diagnostic surfaces multiple gaps?
With the gap that is generating the most compounding cost. Organizational resilience gaps compound. A decision rights problem creates escalation patterns that overload senior leaders who then have less bandwidth to address the load distribution problem that is generating the escalation. Sequencing matters. The right starting point depends on a fuller assessment of what is holding, what is overloaded, and what the organization is currently absorbing that it is not designed to handle.
