The Redundancy Paradox: Why Asking Teams to ‘Try Harder’ Is Strategic Malpractice
You’ve seen it before. A critical project fails. Deliverables missed. Customers unhappy. The post-mortem begins, and someone inevitably says: “We need to be more disciplined. Work harder. Stay focused.” The team nods. Everyone feels accountable. Everyone promises to do better.
Six months later, the same failure pattern repeats. Different project, same root cause. But this time, the exhaustion is visible. Good people burn out. The best ones leave. And leadership, bewildered, asks: “Why can’t we execute?”
Here’s the uncomfortable truth: you’re treating a systems problem like a motivation problem. And in doing so, you’re committing strategic malpractice.
Most organizations operate on a seductive fiction: that effort scales linearly with results. Work harder, achieve more. Simple math. Except it’s not math—it’s mythology. This mindset confuses individual heroism with organizational capacity. It mistakes the emergency override button for the operating system.
The real issue isn’t effort. It’s design. Specifically, how leaders systematically strip away redundancy in pursuit of efficiency, then act shocked when systems collapse under pressure. They optimize for the best-case scenario, then blame people when reality delivers anything less.
This isn’t just poor management. It’s a fundamental misunderstanding of how complex systems actually work.
The Efficiency Trap
Every business school teaches you to eliminate waste. Lean operations. Just-in-time everything. Maximum utilization. On paper, it’s brilliant—why pay for capacity you’re not using?
Because reality doesn’t arrive on schedule.
When you strip redundancy to chase efficiency, you’re not building a tight ship. You’re building a fragile one. A system with no slack is a system that can’t absorb variation. And variation—unexpected illness, supplier delays, market shifts, technical failures—isn’t an edge case. It’s the actual operating environment.
Consider the supply chain crises of recent years. Companies spent decades optimizing inventory to near-zero. They celebrated “asset-light” models. Then a pandemic hit, and suddenly no one could get semiconductors, shipping containers, or basic components. The efficiency gains evaporated overnight, replaced by catastrophic costs: halted production lines, angry customers, emergency airfreight at 10x normal rates.
The companies that survived best? Those with “wasteful” inventory buffers. Those with redundant suppliers. Those who hadn’t fully drunk the efficiency Kool-Aid.
The Attribution Error
Here’s where leadership typically fails: when systems crack under pressure, they attribute failure to individual performance rather than system design.
A team misses a deadline. Why? “They weren’t committed enough.” A customer complaint escalates. Why? “The support agent didn’t care.” A product ships with bugs. Why? “Engineering got sloppy.”
This is the fundamental attribution error writ large across organizational culture. We see outcomes and reverse-engineer motivation, completely ignoring the constraints, incentives, and design choices that shaped those outcomes.
But people don’t fail in a vacuum. They fail in contexts. And if the context is a system designed with zero margin for error—where a single sick day, a single dependency delay, a single miscommunication cascades into failure—then the system itself is the problem.
Asking someone to “try harder” in a system designed to fail is like asking a Jenga tower to be more structurally sound while you remove another block.
Redundancy as Strategy
Redundancy gets a bad reputation because we misunderstand its purpose. We think it’s about duplication—having two of everything “just in case.” That feels wasteful.
But real redundancy isn’t duplication. It’s strategic slack. It’s buffer capacity. It’s the difference between a bridge built to exactly the expected load versus one built to 3x the expected load. Both are “efficient” from different time horizons.
In software, we call this fault tolerance. In engineering, safety factors. In finance, reserves. In operations, it’s buffer stock and cross-training and decision-making authority distributed beyond single points of failure.
Organizations that build in redundancy can absorb shocks. They can experiment without betting the company. They can give employees permission to think rather than just execute frantically. They create space for quality instead of just throughput.
This isn’t theoretical. Look at companies known for operational excellence—Amazon, Toyota in their prime, modern infrastructure platforms. They over-invest in redundancy. Multiple data centers. Extensive testing environments. Cross-functional teams that can cover for each other. Decision frameworks that don’t require escalating every choice to a bottleneck executive.
The cost? Slightly higher operational expense in normal times. The return? They don’t have “not normal” times that cripple the business.
The Default to Yes Problem
Compounding the redundancy deficit is what happens when systems are optimized to say “yes” to everything. Every new feature request. Every customer demand. Every executive initiative. Without the capacity to absorb this load, teams enter permanent triage mode.
When everything is urgent, nothing is strategic. When everyone is at 100% utilization, there’s no capacity for the actual work that builds durability: documentation, refactoring, training, process improvement, deep thinking about problems before they become fires.
Leaders confuse activity with progress. They celebrate teams that pull all-nighters, not teams that prevent all-nighters from being necessary. They reward the hero who saves the day, not the systems thinker who designs systems that don’t need saving.
This creates a perverse incentive structure: the better you are at firefighting, the more fires you get assigned. Meanwhile, the person building fire-resistant infrastructure gets questioned about ROI.
So What?
If you’re leading a team, managing a business, or building anything meant to last, this matters because your next failure is already designed in. It’s sitting there, waiting for the first time normal variance exceeds your zero-tolerance system.
The question isn’t whether your people can work harder. They probably can—for a while. The question is: why are you designing systems that require heroism to function normally?
Strategic execution isn’t about pushing harder. It’s about designing for reality. And reality includes sick days, market turbulence, supplier issues, key employee departures, miscommunications, and a thousand small variations that don’t appear in your best-case Gantt chart.
Building redundancy isn’t admitting defeat. It’s choosing resilience over fragility. It’s recognizing that the most efficient system is often the first to fail, and that true strategy accounts for the world as it is, not as your spreadsheet wishes it to be.
When your next project stumbles, resist the urge to demand more commitment. Instead, ask: what systemic changes would make success normal instead of heroic?
That’s the difference between managing activity and leading strategic execution.
Take Home Points
- Efficiency without redundancy is fragility in disguise — systems optimized for best-case scenarios collapse when reality delivers normal variance
- Effort can’t compensate for design flaws — asking teams to work harder when systems lack capacity is strategic malpractice, not leadership
- Redundancy is strategic slack, not waste — buffer capacity in operations, cross-training, and decision-making authority prevents catastrophic failures
- Heroic firefighting is a symptom, not a solution — cultures that celebrate saving the day are cultures that have designed systems to need saving
- Build for reality, not spreadsheets — true operational excellence designs for variation, constraint, and human limitation from the start
Sources
- “Redundancy and Resilience” — https://seths.blog/2026/03/redundancy-and-resilience/
- “Systems and the Default to Yes” — https://seths.blog/2026/03/systems-and-the-default-to-yes/