Review Resilience Debt

Efficiency or automation removing alternate skills, channels, or relationships needed during disruption.

Resilience debt builds when an organization makes the preferred way of working more efficient by removing its second ways to operate. Normal work may improve, but people lose fallback skills, alternate communication paths, accessible records, or practiced relationships that would keep essential service moving during an outage.

System recovery and business continuity are not the same. A platform may be recovering as designed while employees still need to contact customers, find commitments, approve exceptions, and perform critical work. Resilience debt remains hidden during normal operations and becomes expensive when the primary path disappears.

A business stops printing the next day's schedule because its cloud platform has been reliable for years. During an outage, employees cannot see appointments or contact customers. A current offline schedule and a practiced manual process would not replace the platform, but they would preserve essential service until it returns.

Managing resilience debt does not mean duplicating every system or preserving every old method. It means identifying work that cannot stop, retaining a credible alternate path for that work, and practicing the handoff before disruption turns it into improvisation.

Efficiency removed the second way.

* [[debt|Debt]] * [[institutional-memory-cliff|Institutional Memory Cliff]] * [[operational-slack|Operational Slack]] * [[workaround-dependency|Workaround Dependency]] * [[concentration-risk|Concentration Risk]]

No current wording.

* Test whether critical work has an alternate route with [[operational-slack|Operational Slack]] and [[concentration-risk|Concentration Risk]] in view. * Check whether the fallback also depends on knowledge at risk of an [[institutional-memory-cliff|Institutional Memory Cliff]].