Slack
The intuition is wrong: 100% utilization doesn’t mean 100% efficiency. It means gridlock.
Traffic engineers know that highway flow peaks around 45 mph with moderate density — roughly 30 vehicles per mile per lane. Push beyond that and flow degrades. At “jam density” (185-250 cars per mile), flow drops to zero.
A highway at 100% capacity is a parking lot. The slack is what allows movement.
Tom DeMarco’s 2001 book Slack makes the organizational case: “Change and reinvention require slack. Slack is the time when reinvention happens. It is time when you are not 100 percent busy doing the operational business.”
Companies optimize slack away — every minute accounted for, every person at capacity, every dollar allocated. Then something unexpected happens and there’s no room to respond. Efficiency killed adaptability.
DeMarco: “Organizations tend to get more efficient only by sacrificing their ability to change.”
Projects with aggressive schedules fail because there’s no buffer for problems. Mandatory overtime produces impaired quality and turnover. The system becomes brittle precisely when it looks most productive.
Slack is capacity to respond to the unplanned:
- Say yes to unexpected opportunity
- Absorb setbacks without cascade failure
- Think beyond the immediate crisis
- Experiment without betting the company
A calendar with no gaps is a calendar with no possibilities. A budget with no cushion is one surprise from crisis.
Slack looks like waste. It’s insurance against fragility.
Go Deeper
Books
- Slack by Tom DeMarco — The full argument. Short, accessible, essential for anyone managing teams or schedules.
- Peopleware by Tom DeMarco & Timothy Lister — The companion classic on software teams and the sociological factors that kill productivity.
- The Goal by Eliyahu Goldratt — Theory of Constraints applied to manufacturing. Shows why 100% utilization kills throughput.
Related: [[antifragility]], [[carrying-capacity]], [[systems]]