THE IDEA
Cycles within cycles
No system exists at just one scale. A tree is part of a forest. A forest is part of a landscape. A landscape is part of a biome. Each operates on its own timescale, each goes through its own adaptive cycle, and - crucially - they influence each other.
Panarchy describes this nesting. It’s the idea that adaptive cycles at different scales are connected in two directions. Revolt is the upward connection: a crisis at a small, fast scale can cascade upward and trigger collapse at a larger, slower scale. A single bank failure triggers a financial crisis. A single match starts a forest fire. A single departure triggers a team exodus. Remember is the downward connection: the larger, slower scale provides resources and context for the smaller scale’s reorganisation after collapse. The forest’s seed bank enables regrowth after fire. The economy’s institutions provide structure for new businesses after a crash. The family’s history provides identity during personal crisis.
This cross-scale interaction is what makes panarchy more than just nested cycles. It explains why some disruptions stay small and some cascade catastrophically. It explains why some systems recover quickly from collapse and others don’t. And it gives a richer picture of resilience - not just the ability of one system to absorb a shock, but the ability of the whole nested hierarchy to prevent small collapses from becoming big ones and to support renewal when collapse does occur.
IN PRACTICE
When scales collide
A mid-level manager burns out (individual adaptive cycle: release phase). In a healthy organisation (organisational cycle: growth or early conservation), the team reorganises, support is available, and the individual recovers. The revolt doesn’t cascade upward. But in a fragile organisation (late conservation, already rigid), the manager’s departure exposes dysfunction that was being held together by their effort. Other people leave. Projects stall. The individual-scale release triggered an organisational-scale release. Same individual event, different outcome, because the higher scale’s phase determined whether it could absorb the shock.
A local economic crisis - a factory closure - hits a town (local cycle: release). If the regional economy is healthy and diverse (regional cycle: growth), the town gets reabsorbed. Workers find jobs nearby. New businesses are attracted by available infrastructure. The regional level “remembers” and provides resources for local reorganisation. If the regional economy is also fragile (late conservation), the factory closure triggers wider decline. The revolt cascades upward. Neighbouring towns suffer. The regional economy contracts.
A new technology disrupts an industry (industry cycle: release). Startups form rapidly (small-scale reorganisation). Some succeed, most fail. The ones that succeed draw on the industry’s accumulated knowledge, infrastructure, and customer base - the “remember” function of the larger scale. The disruption was destructive at the industry level but creative at the firm level, and the larger scale’s resources enabled the new growth. Without that memory - without the infrastructure, the skills, the market relationships - the reorganisation phase would have nothing to build on.
WORKING WITH THIS
Reading across scales
When facing disruption, ask: at what scale is this happening, and what’s happening at the scales above and below?
If the disruption is at your scale, look up. Is the level above you stable enough to contain the damage and provide resources for recovery? If so, the disruption is survivable. If the level above is also fragile, the disruption may cascade.
If the disruption is below your scale, look down. Can you contain it? Can you provide the resources and context for the lower level to reorganise? If you’re in a rigid conservation phase yourself, you may not be able to absorb even a small revolt from below.
The most dangerous situations are when multiple scales are simultaneously in late conservation - rigid, efficient, and fragile. A small disruption at the bottom can cascade upward through each fragile level, producing a system-wide collapse that seems disproportionate to the trigger. The most resilient situations are when scales are in different phases - some growing, some conserving, some reorganising - so that strength at one level compensates for vulnerability at another.
THE INSIGHT
The line to remember
A small collapse stays small when the levels above can absorb it. It cascades when they can’t. Resilience isn’t just about your own level - it’s about the health of the levels that hold you.
RECOGNITION
When this is in play
You’re seeing panarchy when a small disruption cascades into something much larger - a revolt moving upward through fragile scales. When a system recovers from collapse using resources from a larger, slower system - the remember function in action. When the same kind of event produces a minor disruption in one context and a catastrophe in another - the difference is usually what’s happening at the scales above. When someone says “how did something so small cause something so big?” - the answer is almost always panarchy.