Continuity Failure Mapping

• Pre-session preparation sheet sent beforehand.
• Dependency map showing your organisation's invisible load-bearing elements and their severity.
• Cascading impact timelines for your most critical vulnerabilities.
• A set of concrete workarounds — paper forms, phone-chain templates, manual procedures — ready to be put in place after the session.
• A prioritised list of next steps for identified gaps.

Before the session, each participant receives a short prep sheet to guide them in mapping a few tools, systems, or people they depend on most to do their work — and what they would do if each one became unavailable. This takes twenty minutes and means the workshop starts with real material rather than hypotheticals.

Using methods from user research (observation-style questioning and dependency tracing) we surface the things your organisation takes for granted: the person who "just knows" the system, the supplier who has always been reliable, the process that works fine (until it doesn't). These are the invisible load-bearing elements that rarely appear in any documentation.

From there we run a Cascading Impact Analysis on each identified dependency. Rather than rating risk in the abstract, I follow the failure forward through time: what happens after one hour, one day, one week? This transforms a list of vulnerabilities into a set of concrete, time-mapped consequences — and makes it immediately obvious which failures need a fallback and which can wait.

The second half of the session is spent designing those fallbacks. Not theoretical continuity plans, but specific, low-tech workarounds that work with what you already have: a handwritten booking ledger, a printed contact chain, a one-page procedure someone can follow under pressure. For each major vulnerability I identify, I produce a reserve routine, a restoration routine, and a return routine.

The goal is not a perfect business continuity programme. It is a set of things you can actually use if something breaks tomorrow.