Protecting revenue when the operating system breaks
How companies can design for revenue and value continuity when shocks disrupt customers, channels, technology or supply.
Read articleWhere does resilience stop working?
A conventional exercise asks whether the plan works under a chosen scenario. A serious stress test asks how far conditions must deteriorate before the business can no longer protect an essential outcome. That boundary is more decision-useful than a reassuring pass.
Define failure first: unsafe operation, breach of obligation, loss of minimum service, liquidity exhaustion, irreversible customer migration or loss of stakeholder confidence. Build a severity ladder across duration, geography, demand, workforce, suppliers and technology. Combine stresses to expose nonlinear effects and feedback between operational, financial and reputational pressure.
Work backward through reverse stress testing. Bank of England guidance describes it as a tool for identifying business-model vulnerabilities and the circumstances in which counterparties stop transacting, shareholders withhold capital or operations become unviable�often before nominal resources are fully exhausted.
At each threshold, identify detection signals, remaining decision time and management actions. Challenge whether mitigations are executable under the same stress: asset sales may face illiquid markets, alternate suppliers may share a bottleneck and leaders may be unavailable. Credit only responses with owners, prerequisites and tested lead times.
Use the result to change limits, buffers, architecture and strategy, not merely to document an extreme case. Track distance to the boundary as exposure evolves and rerun tests after material changes. Resilience stops where assumptions, resources and response speed no longer hold together; leadership should know that point before real conditions discover it first.
Related macro
Articles
How companies can design for revenue and value continuity when shocks disrupt customers, channels, technology or supply.
Read articleHow realistic disruption simulations can expose hidden dependencies and reveal where resilience investment creates the greatest strategic value.
Read articleFocus
Critical knowledge often sits outside formal job descriptions, making individual dependency difficult to see until the person is unavailable.
Separate vendors can still share the same infrastructure, geography, upstream producer or logistics route, creating hidden concentration.
Strategic challenges
Distributed technology can still depend on common regions, identities, control planes, providers or services that create systemic failure points.
Continuity decisions should reflect revenue, strategic importance, switching behaviour and the consequences of prolonged service degradation.
POV
Critical systems often need robustness first. Antifragility matters where controlled variation, experimentation and adaptation can improve future performance.
When actions and claims diverge, more communication can amplify the credibility problem rather than contain it.
Strategic impact
Understanding how exposures interact is often more valuable than predicting which individual shock will occur next.
Distributing essential capabilities across more than one person or team gives the organisation credible alternatives when normal capacity disappears.
What we observe
We frequently see organisations restore operations after disruption without changing the dependencies and assumptions that amplified it.
We frequently see scenarios quantify the shock without modelling the actions, constraints and second-order effects that determine the eventual outcome.