The Efficiency Paradox
Why focusing on individual efficiency often slows down the collective flow.
Key Takeaways
- 100% utilization leads to system gridlock.
- Queues grow exponentially as load increases.
- Slack is essential for agility and speed.
The Resource Efficiency Trap
We often optimize for 'Resource Efficiency'—keeping every person and machine busy. But in complex work, this leads to 'Flow Inefficiency'. Every handoff between busy resources creates a queue. When you are 100% busy, you have 0% capacity to handle the unexpected.The 80% Rule (Kingman's Law)
When a system reaches 80% utilization, productivity doesn't just stay constant—it collapses. This is due to 'Queueing Theory'. Kingman's formula proves that as utilization approaches 100%, wait times increase exponentially.Kingman’s Law:
Wait Time = (Util / (1-Util)) * Variance (As utilization (Util) approaches 1, the '1-Util' denominator approaches zero, sending wait times to infinity.)📹 Video Resource: What Is the Kingman Law?
The Silent Killer: Handoffs
In a highly 'efficient' organization with specialized roles, work must pass through multiple busy people. If each person is 100% busy, work waits at every single handoff. A task that takes 2 hours of 'active' time can take 2 weeks of 'total' time because of these queues.Slack is a Feature, Not a Bug
Professional musicians and athletes don't practice 100% of their time to perform. They leave 'slack' for recovery, learning, and peak performance. Engineers need the same. Slack is the oil that allows the gears of flow to turn without grinding to a halt.Busy is not the same as productive. A highway at 100% utilization is a parking lot.
— The Traffic Analogy