THE IDEA
The value of what seems wasted
Redundancy is having more than you need. More capacity than current demand requires. More people than the minimum to do the work. More savings than this month’s bills. More options than the current plan calls for. In a world obsessed with efficiency, redundancy looks like waste. Strip it out. Optimise. Run lean.
Until something goes wrong.
The paradox of redundancy is that it’s unnecessary right up until the moment it’s essential. Two kidneys when one would do. An emergency fund when the bills are paid. A colleague who can cover your role when you’re always there. These look like surplus in normal conditions. In abnormal conditions - illness, recession, crisis - they’re the difference between a system that continues to function and one that collapses.
Every efficiency drive is, at some level, a redundancy removal programme. And every resilience failure is, at some level, a story about redundancy that was stripped out. The tension between efficiency and resilience is one of the most important in system design, and redundancy sits right at its centre.
IN PRACTICE
The spare part that saves everything
A supply chain team eliminates all buffer stock to reduce warehousing costs. Just-in-time delivery, zero waste, minimal inventory. The metrics look beautiful. Then a port closure disrupts deliveries for two weeks. Without buffer stock, production stops entirely. The savings from three years of lean inventory are wiped out by one disruption. The redundancy that was eliminated as waste was, in retrospect, the cheapest insurance the company had.
A small business has two people who can run the accounts. One does it daily, the other knows how but doesn’t need to. An efficiency review suggests the second person’s accounting knowledge is redundant - they should specialise in their primary role. They do. Six months later, the first person is ill for three weeks. Nobody can run payroll. The redundancy wasn’t a duplication of effort. It was a backup that cost nothing in normal times and was priceless in abnormal ones.
Your body runs two lungs, two kidneys, two eyes. Evolution didn’t optimise for efficiency - it optimised for survival. A biological system that ran on minimum viable organs would be spectacularly efficient right up until one organ failed. Redundancy in nature isn’t a design flaw. It’s a design principle. The systems that survived are the ones that could lose a part and keep going.
WORKING WITH THIS
Protecting what looks like waste
The first step is recognising that redundancy is an investment, not a cost. It doesn’t show up on the balance sheet as an asset, but it functions as one - insurance against disruption, paid for in slack rather than in premiums.
When evaluating whether to remove redundancy, ask: what happens if the thing this backs up fails? If the answer is “we manage, it’s inconvenient,” the redundancy might genuinely be dispensable. If the answer is “critical functions stop,” the redundancy is load-bearing and removing it is a gamble, no matter how efficient it looks.
The practical challenge is that nobody gets praised for maintaining redundancy. You don’t get a bonus for the crisis that didn’t happen because the backup system was there. But you do get blamed when the crisis does happen because it was removed. The discipline is maintaining redundancy against the pressure to eliminate it - knowing that the value is invisible in calm times and obvious only in turbulent ones.
THE INSIGHT
The line to remember
Redundancy looks like waste until you need it. Then it looks like the only thing that was ever worth paying for.
RECOGNITION
When this is in play
You’re seeing redundancy at work when a system handles a disruption gracefully because a backup was available. When someone says “good thing we had that spare.” When a crisis is contained because there was slack in the system to absorb it. You’re seeing its absence when a single failure cascades because there’s no backup, no buffer, and no spare capacity. When an efficiency-focused system works perfectly in normal conditions and catastrophically in any other. When the phrase “we couldn’t have predicted that” is used to explain why a system with zero margin collapsed at the first surprise.