A village beside a river can do many things to prepare for floods. Families can raise valuables above floor level. Volunteers can monitor the river. Farmers can move livestock. Local leaders can establish evacuation routes. Yet the village may still be badly exposed if the upstream warning arrives late, the road out is already flooded, the mobile network fails, or emergency cash cannot reach households in time.
This reveals something important about resilience. It is rarely produced by one capable actor.
A household can be resilient and still live inside a fragile system.
That creates a puzzle. We usually organise resilience by sector. Disaster agencies manage hazards. Health departments manage hospitals. Utilities manage electricity. Municipalities manage drainage. Employers manage workplaces. Banks and insurers manage financial risk. Each institution may perform its own job reasonably well, yet people can remain exposed because the shock moves across the boundaries between them.
The problem is often not what happens inside institutions. It is what happens between them.
Consider extreme heat. A weather agency may predict dangerous temperatures accurately. But the forecast protects nobody by itself. Someone must decide when schools change hours, when outdoor work stops, whether health facilities prepare for additional patients, how drinking water is provided, and what happens to workers who lose income because they followed the advice.
Everyone can own part of the problem while no one owns the outcome.
This is what I mean by shared resilience.
Shared resilience is the ability of connected people and institutions to understand a risk, act together before and during a shock, absorb its consequences and recover without simply transferring the damage to someone weaker.
In simple terms:
Shared resilience = shared understanding of risk + connected institutions + coordinated action + appropriate finance + local capability.
There is an obvious objection. If resilience becomes everybody’s responsibility, it can quickly become nobody’s responsibility. “Shared” can become an excuse for meetings, committees and blurred accountability.
That objection is right.
Shared resilience should not mean that every actor does everything. It means almost the opposite. Each actor should know what it owns, what it depends on others for, and what must happen when responsibility passes from one institution to another.
An electricity grid offers a useful analogy. Reliability does not come from every component performing the same function. Generators, transmission lines, substations and distribution networks do different things. The system works because their roles connect.
Resilience works similarly.
A forecast is useful because someone can act on it. Early action is useful because households can afford to respond. Infrastructure is useful because it continues functioning during shocks. Insurance is useful because the payment arrives when recovery capital is needed. Local knowledge is useful because institutions can incorporate it into decisions.
The real unit of resilience is therefore not the project.
It is the chain of action.
This changes what we should look for when evaluating resilience. We tend to count infrastructure built, people trained, warnings issued or finance committed. Those measures matter. But they can miss the point at which systems fail.
A better question is: where does the chain break?
Does the information fail to reach decision-makers? Does authority become unclear? Does funding arrive too late? Does one institution assume another will act? Does the household receive a warning but lack the money to follow it?
Once we start looking at resilience this way, something else follows.
The strongest intervention may not always be another project. Sometimes it is fixing the connection between two existing capabilities.
That is why shared resilience matters. Serious risks increasingly travel faster than our institutional boundaries do.
Our institutions do not all need to become larger.
They need to become better connected.
Leave a comment