The foam was everywhere, stinging, blinding. You learn quickly that closing your eyes only traps the chemical burn closer to the cornea. The instinct is to thrash, to flush it out with cold water, to interrupt the system before the damage becomes permanent. It was a momentary, stupid failure-reaching for the conditioner bottle and grabbing the clarifying shampoo instead. I hate that kind of small, avoidable error.
But think about how much time we spend chasing those immediate, small, fixable failures. We adjust the showerhead temperature by 0.3 degrees, we spend 23 minutes optimizing a quarterly report template, we install 3 apps to track our 1-mile walking route, just so the visible output-the dashboard-looks clean and controlled. We call this efficiency. We crave the feeling of mastery over the trivial. We believe that if we eliminate all the small, irritating frictions, we achieve a frictionless life, which must mean success.
This is the core frustration I cannot shake: we are obsessed with optimizing the dashboard, while the engine room, the messy, grease-stained, redundant, vital heart of the system, is rusting out of sight. We have become terrified of redundancy. We interpret slack as laziness.
The Case for Spectacular Waste
I spent last autumn up North, visiting Flora L.M., who runs the oldest operational lighthouse on that stretch of the coastline. Flora doesn’t talk about optimization. She talks about survival. Her operational schedule is built entirely on what modern management consultants would call spectacular waste.
Flora’s Built-in Capacity (Visible Waste)
Gallons of Kerosene Stored
(Backup for 33 years of electric failure)
Backup Fog Horn Regulators
(Needs only 1)
Minutes of Mandatory Silence
(Pure structural observation)
“It’s not about if the power fails,” she said, pulling a chamois cloth tight. “It’s about *when*. And if you’ve already prioritized speed and low inventory over redundancy, you haven’t just created a lean system. You’ve created a single point of failure that screams when the wind hits 93 knots.”
And here is the contrarian angle that keeps me up at night, the idea that tastes like salt and metal: radical inefficiency is often the precursor to breakthrough stability.
Brittleness vs. Buffer
If you prune every branch that isn’t currently bearing fruit, you create a beautiful, productive, yet highly vulnerable system. A drought wipes it out. A single blight destroys the monoculture. The inefficient system, the messy one with the unused backup tanks and the slow, wandering routes, is the one that has enough mass, enough distributed capacity, enough *slowness*, to absorb the inevitable shocks.
We optimize ourselves into brittleness. We shave off the margins, believing we are maximizing profit or productivity, but all we are really doing is eliminating the buffer zone between minor disruption and total catastrophe. This applies not just to code bases or corporate supply chains, but right down to our personal operating systems.
We mistake brittleness for elegance.
– The critical realization hidden in plain sight.
The constant push to be ‘always on,’ to ‘maximize every moment,’ to ‘never waste time’ is actively eroding our resilience. When the inevitable 3-day sickness hits, or the sudden family emergency arises, the person who has zero slack-whose entire life runs at 97.3% capacity-doesn’t just pause; they break.
The Fragility of Perfection
I saw this recently in a massive tech deployment, a system integration that everyone was applauding for its sleek, optimized architecture. They had automated 93% of the manual checks. It was brilliant. It was fragile. I remember talking to the project lead-a truly brilliant, if exhausting, woman-who detailed how they had managed to cut 23 hours off the deployment time. I nodded along, all admiration, but inside I was thinking about how easily I had grabbed the wrong bottle of shampoo this morning. A momentary lapse in attention, a tiny visual miscue, and suddenly my eyes were burning. That small, human moment of error is exactly what the highly optimized system cannot process. It assumes linear, correct inputs 99.3% of the time. It doesn’t tolerate the human equivalent of stinging chemical foam.
A good system doesn’t try to eliminate all human error (which is impossible, by the way); it builds layers around it. It builds redundancy.
I’ve made this error myself, countless times. I used to manage a small creative team, and I prided myself on our lean operations. We ran at 99.3% utilization. We were fast, we were sharp, and when one person got sick, the entire structure wobbled. It was thrillingly productive until it wasn’t. I didn’t acknowledge this fragility until one major project nearly collapsed because I had optimized away the 13 hours of administrative padding that would have allowed us to adjust to unexpected client feedback. I failed to prioritize resilience over the immediate, visible metric of high utilization. It felt like winning until the moment we started losing.
True resilience isn’t about rapid recovery; it’s about having so much redundancy and slack built in that catastrophic failure is simply preventable. It’s about accepting that wastefulness is a feature, not a bug, in any system designed to last longer than 13 years.
The Three Forms of Protective Waste
Max speed, zero buffer. Single failure = total collapse.
Distributed capacity allows shock absorption and survival.
1. Physical Redundancy (Flora’s Kero)
Extra inventory, backup generators. Designed for the 1-in-103-year event. It is the cost of buying insurance against oblivion.
2. Temporal Redundancy (Slack)
Buffer time, mandated silence. The mechanism allowing the system to recognize early structural hums before they become operational failures.
3. Cognitive Redundancy (Distributed Knowledge)
Cross-training and documentation, ensuring the system doesn’t crash when the central operator gets shampoo in their eyes.
The Criticality of Dormant Skills
This last point is critical when dealing with high-stakes scenarios. Knowing how to respond when the power fails, or when a critical biological function stops, is what separates a stable organization from a fragile one. When we talk about core resilience-the ability to keep the vital signs operational even when the dashboard is dark-we must prioritize fundamental emergency skills.
Learning things like Hjärt-lungräddning.se isn’t about optimizing daily productivity; it’s about installing the deepest level of cognitive redundancy into the human network. It’s knowledge that sits dormant for decades, perhaps, but which defines survival when those critical 3 minutes arrive.
I am writing this article, arguing against optimization, on a perfectly optimized keyboard setup, running specific algorithms to ensure my word count hits the target. I hate the cognitive dissonance, but I do it anyway, because survival demands adapting to the game, even while criticizing the rules. We must learn to play the optimization game well enough to earn the time to build radical inefficiency into our lives.
The lighthouse isn’t optimized for daily operation; it is optimized for the storm that comes once in a generation. It is designed to look inefficient 362 days a year, so it can be perfectly effective on the other 3.
We must stop worshipping the output and start guarding the underlying capacity. We must stop asking, “How fast can we go?” and start asking the only question that matters when the inevitable failure occurs: Do we have 3 layers of messy, un-optimized protection beneath us?