Build in slack — time, money, and energy buffers

Never plan to use 100% of your resources; leave a buffer for what you did not anticipate.

Why it works

Systems running at capacity have no resilience: a single unexpected load spike causes failure. Slack — unused capacity held in reserve — absorbs unexpected demands without propagating through the system. Research on organizational slack finds that moderate slack is associated with better adaptation to disruption, though too much produces complacency.

How to do it

1. For time: add 25–50% to your time estimate for any project with significant uncertainty.
2. For money: maintain a cash reserve that covers at least three months of obligations without income.
3. For energy: never schedule every hour; protect at least 15–20% of your time for the unexpected.
4. Treat slack as part of the system design, not as wasted capacity.

Evidence

Organizational slack research generally supports its value for innovation and adaptation, though the optimal level is context-dependent. The psychological benefits of resource slack (reduced stress, better recovery) are supported in occupational health research. (observational)

Excessive slack can reduce efficiency and be misallocated; the optimal buffer size depends on uncertainty level and is not precisely determined by research.

Sources

• Bourgeois (1981), organizational slack and performance, Academy of Management Review

Common mistake

Building slack into your plan but spending it on the first unexpected demand rather than protecting it for truly large disruptions.