Design for resilience, not just peak efficiency

Optimized systems are fragile; resilient systems absorb disruption and recover without collapse.

Why it works

Meadows distinguishes resilience — the capacity of a system to recover from disruption — from efficiency, which is performance at a set point. Productivity systems optimized purely for efficiency (no slack, all time allocated, tightest possible schedules) have no capacity to absorb unexpected demands. A single disruption cascades across the system. Resilient systems maintain buffers and redundancy that feel inefficient in normal conditions but prevent total system failure under stress.

How to do it

1. Audit your schedule for slack: is there any recovery capacity, or is every hour allocated?
2. Build at least 20% open time into each day — not as procrastination space but as disruption absorption.
3. Identify single points of failure in your system (the one meeting that, if cancelled, wastes a day) and build redundancy.
4. Test the system under a simulated disruption: what fails first?

Evidence

The efficiency-resilience tradeoff is a well-established concept in systems dynamics, ecology, and organizational theory. Its application to personal schedule design is a principled extrapolation rather than a directly tested intervention. (mechanistic)

What counts as adequate slack varies by role and context; 20% is a heuristic, not a derived figure. Some work contexts have genuinely low slack tolerance at certain times.

Sources

• Meadows (2008), Thinking in Systems — on resilience and system design

Common mistake

Treating any unallocated time as wasted time to be scheduled — which creates a maximally efficient but maximally fragile system that fails at the first disruption.