The short
- Efficiency: Removes waste, slack, and redundancy.
- Resilience: Absorbs shocks and adapts to surprise.
- Failure mode: Systems collapse precisely because they are optimised.
- Signal: “There was no buffer” appears in postmortems.
- Lesson: Slack is not inefficiency — it is insurance.
Why efficiency is so seductive
Efficiency is visible.
It shows up in dashboards, margins, and timelines. It rewards managers with clarity and investors with confidence.
When systems behave as expected, efficiency looks like intelligence.
What resilience actually requires
Resilience is harder to measure.
It lives in:
- unused capacity,
- redundant pathways,
- people who can improvise.
These look wasteful — until they are needed.
How optimisation removes safety
Over time, organisations learn to trim.
Buffers become overhead. Backup plans become optional. Extra people become inefficiency.
The system runs faster — but narrower.
The speed illusion
Highly optimised systems appear strong.
They respond quickly, execute cleanly, and scale smoothly.
But they are tuned for yesterday’s conditions.
When inputs change, speed amplifies error.
Why failure feels sudden
Breakdowns rarely arrive without warning.
Signals exist — missed handoffs, brittle dependencies, silent near-misses.
Efficiency culture teaches teams to ignore these as noise.
What resilient organisations do differently
- They protect slack.
- They reward scenario thinking.
- They train judgment, not just compliance.
They accept slower averages in exchange for fewer catastrophes.
The takeaway
Efficiency maximises performance. Resilience preserves survival.
Speed without slack does not make systems strong. It makes failure arrive faster.