Run systems at 70-85% capacity — full utilization means zero ability to adapt
Run operational systems at 70-85% of measured capacity to maintain adaptive buffer, because systems at full utilization cannot absorb environmental change without breaking.
Why This Is a Rule
Resilience requires slack. A system running at 100% utilization has zero adaptive capacity — any environmental change (new requirement, team member departure, tool failure, personal disruption) immediately causes a crisis because there's no buffer to absorb the change. The system was optimized for the current environment and cannot survive even small perturbations.
The 70-85% range provides 15-30% adaptive buffer — capacity not committed to current operations that can absorb environmental changes without system failure. This buffer isn't wasted capacity; it's the price of survival. In biological systems, this is analogous to immune function: the body dedicates significant resources to defense that aren't "productive" under normal conditions but are essential when the environment changes.
Nassim Taleb's concept of antifragility goes further: systems with slack don't just survive disruption — they can improve through it, because the buffer provides room to experiment, learn, and adapt. Systems at full utilization can only maintain or degrade.
When This Fires
- Designing personal or team operational systems
- When your current system is "optimized" but fragile — breaks under any change
- After a system failure caused by an environmental change it couldn't absorb
- During any capacity planning where the target is "maximize utilization"
Common Failure Mode
Optimizing for maximum utilization because unused capacity "feels wasteful." In a factory, idle machines look like money being wasted. In knowledge work, unscheduled time looks like laziness. But the 15-30% buffer is what allows the system to handle the sick day, the emergency request, the broken tool, and the new opportunity. Eliminating the buffer to maximize short-term output guarantees long-term fragility.
The Protocol
When designing or evaluating operational systems: (1) Measure actual capacity (not theoretical maximum). (2) Design commitments and load for 70-85% of measured capacity. (3) The remaining 15-30% is adaptive buffer — not to be filled with "bonus tasks" but reserved for: variance absorption, unexpected work, experimentation, and recovery. (4) If the buffer is consistently consumed → the base load is too high or the capacity measurement is inaccurate. Reduce load or re-measure. (5) If the buffer is never touched → conditions are unusually stable. Don't tighten — conditions will change.