The hidden assumptions behind optimisation
Every efficient system is optimised for something: a pattern of demand, a level of reliability, a set of suppliers or a normal range of disruption. When those assumptions hold, concentration and tight coordination can produce impressive performance.
Fragility appears when the operating environment moves outside that range. A single supplier becomes a point of failure. Full utilisation leaves no room for recovery. Standardisation allows one error to travel everywhere. The savings were real, but so was the risk that remained outside the measurement frame.
Resilience is productive capacity
Redundancy is often described as waste because its value is quiet until conditions deteriorate. A second supplier, extra inventory, cross-trained staff or modular technology may look underused. In disruption, these become the capacity that protects outcomes.
The right question is not efficiency or resilience. It is how much resilience the purpose of the system requires. A critical service should be designed differently from a reversible internal process. Leaders need to distinguish harmless slack from strategic optionality.
Look for strategic debt
Efficiency creates strategic debt when short-term gains depend on reduced future freedom. Warning signs include dependencies no one owns, recovery plans that assume unavailable people, and performance targets that reward utilisation while ignoring recovery time.
A resilience review should map concentration, coupling and recoverability. Where could one failure spread? How quickly can capacity be restored? Which alternatives exist in practice, not merely on paper? Making these trade-offs visible allows efficiency to remain a strength rather than becoming a hidden liability.
QUESTION TO CARRY FORWARDWhich apparent inefficiency in your system is actually preserving an option you may need under pressure?