Every system that fails spectacularly was already failing quietly.
The bridge that collapsed had been corroding for years. The company that imploded had been ignoring its own internal signals for quarters. The policy that caused harm had been working around a problem it never solved.
We remember the collapse. We rarely audit the silence before it.
The Accumulation Problem
Complex systems have a remarkable property: they absorb small failures without breaking. This is a feature. It’s also how they eventually fail catastrophically.
Each small workaround, each patch, each “good enough for now” decision is a coping mechanism. The system keeps functioning. The signal that something is wrong gets quieter. The people inside it adapt their behavior to accommodate the dysfunction until the dysfunction becomes invisible.
This is why post-mortems are hard. The failure was “sudden” from the outside. From the inside, it was a slow accumulation that everyone had stopped noticing.
What This Means for Design
If you’re designing systems — software, organizations, processes, anything — the most important thing you can build is not resilience to catastrophic failure. It’s visibility into the quiet ones.
- What are the things people work around instead of fixing?
- What signals are being ignored because they’ve always been there?
- What decisions are being made because “that’s how we’ve always done it”?
The cracks are always visible. They’re just easy to scroll past.