Scenario planning

Scenario planning originated as a military planning tool during World War II, developed by Herman Kahn and colleagues at RAND Corporation to make sense of potential enemy actions under conditions of radical uncertainty. The core insight was that organizations forced to think carefully about multiple plausible futures made better decisions when those futures actually arrived — not because they predicted the future correctly, but because they had already engaged with the decision landscape and were not starting from zero.

The research on recognition-primed decision making by Gary Klein (developed through field studies with military planners and emergency responders) explains the mechanism: experienced decision-makers in fast-moving situations do not compare multiple options and calculate the best one. They recognize the situation as matching a previously encountered pattern and act on a plan they have already tested mentally. Scenario planning builds that pattern library before the emergency provides it the hard way.

A household that has walked through a 72-hour winter power outage scenario — even on paper, around a kitchen table — recognizes the situation differently when the power actually goes out on a winter night. The decisions were already made. The execution begins faster. The cognitive bandwidth freed from "what do we do?" can be redirected to "how are we doing?"

How scenario planning reduces decision load

Three mechanisms connect pre-event scenario planning to better real-event performance:

Pattern recognition: Klein's research found that pattern recognition, not analytical calculation, drives expert decision-making under time pressure. Scenario practice builds patterns. Each walkthrough deposits a mental template for what this type of event looks like and how effective responses begin.

Pre-commitment: Scenarios force decisions in advance. The household that has decided "if an evacuation order comes, we leave in 30 minutes regardless of road reports" does not face that decision under fear-impaired cognition. They execute a previously made choice.

Gap exposure: Walking through a scenario almost always reveals a missing dependency that the household does not know it needs to know — the secondary rallying point that was never specified, the medication that requires refrigeration in a power outage, the phone tree that only one person has a copy of.

The prospective hindsight research underlying Gary Klein's pre-mortem technique (published in Harvard Business Review, 2007) found that imagining a plan has already failed, and then reasoning about why, improves failure anticipation accuracy by approximately 30% compared to forward planning alone.

The pre-mortem: planning backward from failure

The pre-mortem is the most valuable single technique in scenario planning. Klein's method:

State the scenario clearly: "It is 72 hours into a winter power outage. Our plan has failed."
Work backward: "How did it fail? What went wrong first?"
Generate every plausible failure mode without filtering for probability
Sort failures by likelihood and impact
Assign mitigations for the top three

What the pre-mortem exposes that forward planning misses: optimistic assumptions. Most household emergency plans implicitly assume that everyone will be home, that vehicles will start, that key supplies will be where they are supposed to be, and that communications will function. Pre-mortem forces each assumption to be stated explicitly and challenged.

Scenario

Pre-mortem: "72-hour power outage, plan has failed." Why? First answers from a household group typically include: "We ran out of water because we assumed municipal pressure would hold longer." "The generator wouldn't start because the fuel was old." "Nobody knew where the paper maps were when the phone died." "The kids wouldn't sleep because we had no backup for nighttime light." These gaps would not have appeared in a forward plan that assumed everything worked.

Choosing scenarios worth planning

The most useful scenarios are high-probability/moderate-impact events, not catastrophic edge cases. Starting with worst-case scenarios produces plans that are too complex to execute under stress and burns planning bandwidth on low-probability events.

Priority selection criteria:

Local and historical precedent: What has actually happened in your area? Power outages, flooding, wildfire smoke, ice storms, water main breaks. These are not hypotheticals — they are documented local history.
Consequence of unpreparedness: Which scenario would leave you most exposed if you did nothing? That one goes first.
Resource bottlenecks: Which scenario creates the earliest resource crisis? Water supply disruption, medication access failure, fuel unavailability.

Five scenarios that cover most household exposures:

Scenario	Duration	Key variables
Power outage, winter	72 hours to 1 week	Heating, water, food preservation, communications
Evacuation warning	6–24 hours	Vehicle readiness, 72-hour bag, route selection, pets
Water supply disruption	2–7 days	Stored water, alternative sources, sanitation
Supply chain disruption	2–4 weeks	Food/medication sufficiency, resupply options
Medical emergency, transport unavailable	Single event	First aid capacity, contact sequence, alternative transport

Avoid starting with collapse scenarios (grid-down for months, social breakdown) until the five above are well-practiced. Preparedness that starts at the extreme end and works backward toward normal risks never building capability for the scenarios that are actually likely.

The tabletop exercise format

A household tabletop exercise runs in 30–60 minutes and requires nothing beyond a table, the people who would respond, and a facilitator who injects complications.

Structure:

State the scenario (5 minutes): "It is 6 p.m. Tuesday. A winter storm has knocked power out. Weather forecast shows 48 more hours of storm. Temperature is 22°F (−6°C) outside."
Initial response round (10 minutes): Each person in the household says what their first action would be. No corrections yet — this reveals what people actually know.
Add a complication (every 10 minutes): "Your primary vehicle won't start." "The neighbor's elderly parent just arrived needing shelter." "Your phone is at 20% battery and there's no power for charging." Complications force adaptation and reveal dependencies.
Resource check (5 minutes): "Do we actually have what we said we'd use? Where is it? Does anyone know how to use it?"
Debrief (10–15 minutes): What failed? What assumptions were wrong? What is the single highest-leverage fix?

CISA (Cybersecurity and Infrastructure Security Agency) uses this exact format for organizational exercises, adapted here to household scale. The structure works at any scale.

Field note

The most valuable output from a tabletop exercise is the single-fix action that can be completed within 48 hours. Not a planning document. Not a long list. One thing: buy the extra water container, move the generator manual to where it can actually be found, add the secondary contact to the phone tree. A household that consistently implements one fix per exercise makes meaningful readiness progress. A household that produces a comprehensive plan and implements none of it does not.

When not to over-plan

Scenario planning has a pathological version: the household or individual who plans for every conceivable scenario but never tests, acquires, or trains against any of them. The planning becomes a substitute for readiness rather than a path to it.

Signs of planning excess: - Plans covering scenarios with probability approaching zero before basics are secured - Plans that require resources, skills, or network support the household does not have - Plans that have never been walked through with the people who would execute them - Plans that cannot be found, accessed, or remembered under actual stress

The rule: never write a plan you cannot walk through. If the plan requires twelve pages to explain, it will not be executed under stress. One-page scenario cards with condition-based triggers are more useful than comprehensive plans that exist only on a hard drive.

Practical checklist

Run a pre-mortem on your top scenario: "The plan has failed — why?" Generate at least five failure modes and mitigate the top three
Select five scenarios from the priority list above; write a one-page condition-trigger-action card for each
Run one 30-minute tabletop exercise with all household members; implement the single identified fix within 48 hours
Add at least two realistic complications to each drill: unavailable vehicle, reduced communications, unexpected additional person
Store scenario cards in your emergency kit, not only on digital devices
Review and update scenarios after any real event, after any major household change, and annually

The scenario library you build before emergencies is the pattern recognition that replaces open-ended decision-making during them. For the decision architecture that uses these patterns in real time, see the Observe-Orient-Decide-Act (OODA) loop and prioritization under pressure. For the community coordination layer that scenarios should also cover, see communications planning.