Resilience
The capacity to absorb disturbance and reorganize while maintaining essential function.
The Idea
Resilience is not the same as stability (never being disturbed) or sustainability (maintaining current state indefinitely). A resilient system can be disrupted, degraded, even partially destroyed — and still reconstitute itself. It bends without breaking, or if it breaks, it grows back different rather than not growing back at all.
The distinction from sustainability matters. Sustainability tends to assume that a known good state can be perpetuated with the right management. Resilience assumes that states will change, that disruptions will come, and asks: what conditions allow a system to absorb change and reconstitute function through it?
Origins
The concept comes from ecology, specifically C.S. Holling’s 1973 paper on resilience and stability and his later work on adaptive cycles in ecosystems. Holling noticed that healthy ecosystems don’t tend toward equilibrium — they cycle through phases: growth (rapid resource exploitation), conservation (building structure and complexity), release (disturbance — fire, flood, collapse), and reorganization (reconstituting from released elements). Resilience is the capacity to move through this cycle without collapsing entirely.
Panarchy: resilient systems are nested. Local cycles are embedded in regional ones, which are embedded in global ones. Disruption at one scale can be absorbed when other scales remain functional. A forest fire is catastrophic at the stand level; it renews the landscape at the regional level. Panarchy theory describes how these scales interact.
Resilience vs. Efficiency
Efficient systems are optimized for known conditions. Resilient systems maintain function under unknown conditions. The two are in tension: efficiency requires removing redundancy; resilience requires maintaining it.
A supply chain with no slack is maximally efficient when conditions are stable. It collapses when any node fails. The inefficiency of local production — the higher cost per unit, the lower throughput, the year of learning required — buys adaptability under conditions the efficient system can’t handle.
This is not an argument against efficiency in all cases. It’s an argument for knowing what you’re trading when you optimize for it.
The Tension
Resilience-building requires resources. A household that maintains local food production spends time and money and attention that could go elsewhere. The argument for it is not efficiency but adaptability — and the secondary benefits (knowledge, practice, relationship) that emerge from the commitment.
The deeper tension: resilience can be used to justify any inefficiency. “We’re building resilience” is the perfect cover for systems that are just bad. Genuine resilience is tested; it’s not a philosophy, it’s a demonstrated capacity to function through disruption.
Connections
- appropriate-technology — designed to function across conditions
- commons — collective resilience through shared management
- permaculture — designing for system-level resilience
- sufficiency — knowing what function needs to be maintained
- seventh-generation — decisions made for a range of futures
- maintenance — resilience requires ongoing attention
Further Reading
- Holling, C.S. “Resilience and Stability of Ecological Systems.” Annual Review of Ecology and Systematics (1973)
- Walker, Brian and Salt, David. Resilience Thinking (2006)
- Folke, Carl. “Resilience: The Emergence of a Perspective.” Global Environmental Change (2006)