Contingency Map¶
Mapping artifact — instantiates Wild-Card Contingency Mapping
Wires a specific wild-card disruption to its downstream consequences, exposed assets, and accountable owner in one maintained diagram — turning a scary label into a traceable chain.
The Contingency Map takes one wild-card event class and wires it to everything downstream — the pathway by which it propagates, the specific assets and operations it would expose, and the named owner accountable for that disruption's readiness — kept honest by a review cadence so it decays visibly rather than silently. Its distinguishing job is tracing: turning a scary label from the catalog into a followed chain — this supplier fails → these two products lose their only source → these customers → this revenue, on this timeline. Where the Crisis Scenario Catalog holds the breadth of what could happen, the map supplies the depth of so what, to whom, and who owns it for a chosen few.
Example¶
A semiconductor maker maps a single wild card — "the sole-source supplier of a specialized photoresist chemical suddenly stops shipping." The map begins at the event and follows the thread: the chemical feeds one lithography step → that step is required for three of the firm's highest-margin chip families → those chips go into two automotive customers and one medical-device customer → on-hand inventory covers roughly six weeks → after that, lines idle. Along the way the map marks the exposures: the single qualified supplier, the six-week buffer, and the fact that requalifying an alternate chemical takes an estimated ≈9 months.
Each mapped disruption gets an owner — here, the VP of supply continuity — accountable for keeping this branch current and its options viable. The mapping itself surfaces the real problem: the true vulnerability isn't the supplier, it's the nine-month requalification tail, which is where preparedness effort actually belongs. On a set cadence the branch is re-walked, because suppliers, buffers, and qualifications all drift.
How it works¶
- Start from a class, follow the thread. Begin with one event class from the catalog and trace propagation through functions, dependencies, and stakeholders over time — a chain, not a label.
- Mark exposure at each node. At every step, record which assets, people, operations, and decisions sit in the blast radius, plus the buffer or slack that delays the impact.
- Assign an owner per branch. Each mapped disruption carries a named owner accountable for that branch's readiness — the antidote to "everyone's risk, no one's job."
- Re-walk on cadence. The map is revisited on a schedule so drift — a retired buffer, a new dependency — is caught in review rather than discovered mid-crisis.
Tuning parameters¶
- Propagation depth — how many hops downstream to trace. Deeper maps catch second- and third-order effects but cost effort and blur; shallow maps are cheap but miss the cascade.
- Node granularity — whole-function nodes versus individual systems and people. Finer nodes localize the vulnerability precisely but multiply maintenance.
- Owner grain — one owner per map versus one per branch or node. Per-branch ownership drives accountability deep but can fragment the overall picture.
- Review cadence — how often each branch is re-walked; faster catches drift sooner but taxes owners.
- Coupling display — whether shared choke points across disruptions are highlighted. On, the map doubles as a common-cause finder; off, each thread reads cleaner.
When it helps, and when it misleads¶
Its strength is converting a label into a followed chain, so the actual leverage point emerges — usually not the trigger everyone names but a buffer, a single qualified path, or a slow recovery tail buried deep in the pathway. Tracing shared nodes across several disruptions is also how a single point of failure hiding behind many different-looking scenarios finally becomes visible.[n1]
A map is only as honest as its pathways: a plausible-looking chain with a wrong buffer estimate or a missing dependency breeds false confidence. Maps also decay — the fastest-rotting artifact in the archetype, since the dependencies it traces change constantly — so an unreviewed map is worse than none, because it still looks current. And the classic misuse is drawing the map backwards from a response already chosen, reverse-engineering the pathway to justify the buffer someone already bought. The discipline: keep owners on the hook for their branch, re-walk on cadence, and treat every buffer figure as an assumption to be checked, not a fact.
How it implements the components¶
The Contingency Map fills the connective side of the archetype — wiring a disruption to its consequences, exposures, and owner, and keeping that wiring alive:
impact_pathway— the map's spine: the traced chain from event to consequence through functions, dependencies, and time.exposure_and_vulnerability_map— at each node it marks the assets, people, and operations in the blast radius, and the buffers that delay them.wild_card_owner— each mapped disruption names an owner accountable for keeping that branch current and its options viable.readiness_review_cadence— the map is re-walked on a set schedule so it decays visibly instead of silently.
It does not decide which classes are worth mapping — that screening is the Crisis Scenario Catalog — nor does it hold the response moves its branches point to; those are recorded in the Contingency Option Register.
Related¶
- Instantiates: Wild-Card Contingency Mapping — the map is the connective tissue linking event classes to exposures, owners, and, by reference, options.
- Consumes: Crisis Scenario Catalog — supplies the event classes worth the depth of a map.
- Sibling mechanisms: Crisis Scenario Catalog · Contingency Option Register · Strategic Reserve Plan · Red-Team Disruption Challenge · Precursor Watchlist · Disruption Playbook · Tabletop Exercise · Readiness Drill · Wild-Card Workshop
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Wires a specific wild-card disruption to its downstream consequences, exposed assets, and accountable owner in one maintained diagram — turning a scary label into a traceable chain, making its operative form a non-executable information artifact that externalizes static or prospective structure.
Independent corroboration: The frozen evidence defines Contingency Map as 'Wires a specific wild-card disruption to its downstream consequences, exposed assets, and accountable owner in one maintained diagram — turning a scary label into a traceable chain', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Futurism & Strategic Foresight
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Scenario-planning practice cohered mapping a low-probability disruption through downstream consequences, exposed assets, and responsible owners.
Related originating lineages:
- Disaster Management & Risk Reduction — Preparedness practice contributes operational exposure and accountability fields.
- Systems Thinking & Cybernetics — Causal-network mapping supplies propagation chains and hidden single points of failure.
Review resolution: Scenario planning is primary, with emergency dependency mapping and systems propagation as genuine co-lineages; the maintained owner-bearing map is synthesized.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The load-bearing element is the per-branch owner. A map with rich pathways and exposures but no named owner reliably rots, because "keep this current" belongs to no one — which is why ownership is a mapped component here, not an afterthought.
[n1] A single point of failure is one component whose loss brings down the whole system. The contingency map's cross-disruption view is a standard way to expose one hiding behind several unrelated-looking scenarios. ↩