THE IDEA
The space to absorb a shock
A buffer is anything in a system that acts as a cushion. Savings in a bank account. Stock in a warehouse. Spare capacity in a schedule. The extra ten minutes you leave before a meeting. Buffers don’t produce anything. They don’t look productive. In a spreadsheet, they look like waste. But they’re the reason systems survive when things go wrong - and things always go wrong.
The logic of a buffer is simple: if inflows and outflows are always perfectly matched, the system works fine without one. But inflows and outflows are never perfectly matched. Demand spikes. Supplies get disrupted. Someone gets ill. A project takes longer than expected. A buffer absorbs these fluctuations without the system breaking. It’s the difference between a system that wobbles and recovers, and one that wobbles and collapses.
The tension with buffers is that they cost something to maintain. Inventory ties up capital. Spare staff capacity looks like overstaffing. Free time in a schedule looks like idleness. This is why efficiency drives almost always target buffers first - they’re the easiest thing to cut and the savings are immediately visible. The cost of cutting them only shows up later, when the first disruption arrives and there’s nothing left to absorb it.
IN PRACTICE
What happens when the cushion disappears
Hospitals used to run with spare bed capacity - empty beds that looked wasteful on a balance sheet. Decades of efficiency optimisation squeezed that buffer out. When a pandemic hit, there was no slack to absorb the surge. The system that looked lean and efficient in normal times turned out to be brittle and dangerous under stress. The buffer wasn’t waste. It was the system’s ability to cope with the unexpected.
A family that lives paycheque to paycheque has no financial buffer. Everything works as long as nothing goes wrong. But one car repair, one unexpected bill, one week off sick - and the whole household is in crisis. The same family with two months’ expenses in savings can absorb that shock without it cascading into missed rent, late fees, and spiralling debt. The buffer doesn’t prevent the problem. It prevents the problem from becoming a catastrophe.
Just-in-time manufacturing is the deliberate removal of buffers. Parts arrive exactly when needed, nothing sits in storage, capital efficiency is maximised. It works beautifully - until a factory in another country floods, or a shipping container gets stuck in a canal, or a pandemic shuts down supply chains globally. Companies that had maintained even small inventory buffers weathered these disruptions far better than those that had optimised them away entirely.
WORKING WITH THIS
Protect the slack
When you’re looking at a system - a team, a project, a household, a supply chain - ask: where are the buffers, and what would happen if they disappeared? If the answer is “everything would be fine as long as nothing unexpected happens,” you’ve found a fragile system.
Resist the pressure to optimise away all slack. Some spare capacity is not inefficiency - it’s resilience. A team that’s 100% utilised has no ability to respond to surprises, help a colleague, or think about anything beyond the immediate task. A schedule with no gaps can’t absorb a single delay without everything downstream shifting. Build in deliberate margins, and defend them when someone points at them as waste.
The art is in the balance. Too little buffer and the system is fragile - one shock and it breaks. Too much buffer and the system is sluggish - resources sit idle, responses are slow, there’s no urgency. The right amount depends on how volatile the environment is. Stable, predictable conditions need less buffer. Turbulent, uncertain conditions need more. If you’re not sure which you’re in, err on the side of more.
THE INSIGHT
Slack is a feature, not a flaw
The most efficient-looking system is often the most fragile. Buffers are what let a system absorb the world’s messiness without falling apart. Cut them in the name of efficiency, and you’re borrowing resilience from the future.
RECOGNITION
Knowing it when you see it
You’re looking at a buffer issue when a system works perfectly under normal conditions but falls apart at the first disruption. When there’s no room to absorb a surprise, a delay, or a spike in demand. When “efficiency” has been pursued so aggressively that the team, the process, or the supply chain has zero margin for error. When someone says “we’re running lean” with pride - ask what happens when something unexpected arrives.