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

Building your own scenario cards

The five scenarios listed above are starting points. Your household faces a unique combination of geography, health conditions, household composition, and resource access. Use this template to build custom scenario cards for any situation specific to your area.

Scenario card template

Each card fits on one side of an index card or a single printed page. The constraint is intentional — if it does not fit on one page, it is too complex to execute under stress.

Card header:

Scenario name: Short, descriptive (e.g., "Winter ice storm — 5 days")
Trigger condition: What tells you this scenario is happening? Be specific. ("Power out + temperature below 20°F / −7°C + forecast shows 48+ hours of ice" is a trigger. "Bad weather" is not.)
Duration assumption: How long are you planning for? (72 hours, 7 days, 30 days)

Decision points (list 3–5 maximum):

Stay or go? What conditions trigger evacuation vs. shelter-in-place? Define the threshold in measurable terms: "If indoor temperature drops below 45°F (7°C) for 6 hours, evacuate to [destination]."
When to start the generator? At what point does the benefit justify fuel consumption?
When to share resources with neighbors? Under what conditions, and what is the limit?
When to seek outside help? What medical, supply, or safety threshold triggers a call for assistance?
When to shift from short-term to long-term posture? What signals tell you this is lasting longer than expected?

Resource inventory (per scenario):

Resource	Current quantity	Days of coverage at usage rate	Resupply source
Water (stored)	___ gallons / liters	___ days at 1 gal (3.8 L)/person/day	Nearest secondary source
Food (shelf-stable)	___ days of meals	___ days	Pantry + nearest open store
Fuel (generator)	___ gallons / liters	___ hours runtime	Nearest fuel station
Medications	___ days supply	___ days	Pharmacy + telehealth
Cash on hand	$___	___ days of purchases	ATM (if operational)

Pre-committed actions (things you will do without further deliberation):

First 15 minutes: [specific actions]
First 2 hours: [specific actions]
First 24 hours: [specific actions]

Worked examples

Three complete scenario cards, filled in for a household of two adults in a mid-latitude suburban home with a natural gas furnace, municipal water, and two weeks of food on hand at any given time.

Example 1: 2-week winter power outage

Trigger condition: Power out + outdoor temperature below 25°F (−4°C) + utility restoration estimate exceeds 72 hours
Duration assumption: 14 days

Decision points: 1. Stay or go? If interior temperature drops below 45°F (7°C) and cannot be maintained with alternate heat source, evacuate to identified warm location within 30 miles (48 km). Trigger is measurable: an inexpensive indoor thermometer is all the instrumentation you need. 2. Generator start? At hour 4 of outage — run 4 hours on, 8 hours off to conserve fuel. Never run indoors or in the garage. 3. Water supply? Municipal pressure may hold — but freeze risk at pipes. Fill bathtubs immediately when trigger condition is met. At 48 hours, transition to stored water.

Resource snapshot: 14 gallons (53 L) stored water = 7 days at 1 gallon (3.8 L) per person. 12 days of food on hand. 5 gallons (19 L) of generator fuel = approximately 20 hours runtime at 50% load. Medications: 30-day supply, none requiring refrigeration.

Phase 1 → Phase 2 trigger: If indoor temperature drops below 55°F (13°C) OR if generator fuel drops below 2 gallons (7.6 L) with no resupply available, shift to conservation posture — one heated room only, reduced cooking, minimize door opening.

Example 2: Regional flood with 48-hour warning

Trigger condition: National Weather Service issues Flash Flood Watch for your county AND local roads show standing water
Duration assumption: 5–7 days until area is accessible again

Decision points: 1. Evacuate or shelter-in-place? If property is in a FEMA Flood Zone A or AE, evacuation is mandatory when Watch is issued — do not wait for Warning. If property is at elevation and Watch only (not Warning), shelter-in-place is defensible until roads deteriorate. 2. Vehicle timing? Leave at first Watch if Zone A. With 48 hours of warning: first 12 hours for preparation, evacuation at hour 24 to beat traffic. Do not attempt road travel through standing water — 6 inches (15 cm) of moving water can knock a person down; 12 inches (30 cm) can move a vehicle. 3. What goes first? Documents and medications in the first bag. Bug-out bag goes in the vehicle as a unit — no repacking under stress.

Resource snapshot: 72-hour bag already in vehicle. Medications in the bag. 5 days of shelf-stable food at destination (identify the destination before this scenario occurs). Cell service is likely to degrade — pre-load offline maps for alternate routes.

Phase 1 → Phase 2 trigger: Any road on the primary evacuation route becomes impassable. Immediately shift to alternate route and notify household members via pre-agreed communication plan.

Example 3: Economic disruption with 6-month supply chain delays

Trigger condition: Sustained grocery shelf gaps lasting more than 2 weeks across multiple categories, combined with significant price increases (>30% in 60 days) in staple foods
Duration assumption: 180 days of reduced supply availability; not a total collapse scenario

Decision points: 1. Purchasing posture? Shift to 3-month rolling pantry immediately. Buy normal rotation items in double quantity until 90-day buffer is established. Do not hoard — buy what you will rotate and use. 2. Cash on hand? Maintain 2–4 weeks of essential expenses in cash in case of electronic payment disruptions. Not a long-term strategy, but a buffer during the initial instability period. 3. Medical supply buffer? Request 90-day supplies from provider for any maintenance medications. This is a standard option on most insurance plans — use it before a shortage, not during.

Resource snapshot: 90 days of food, 30 days of water, 90 days of key medications, 3 months cash buffer for essentials. The extended timeline means resupply is possible — the goal is not to stockpile for 6 months but to build enough runway that you're not competing for depleted supplies.

Phase 1 → Phase 2 trigger: If fresh produce becomes unavailable for more than 30 days, begin supplementing with home garden production and any preserved/stored alternatives. See food preservation for building a shelf-stable food system.

Decision point framework: evacuate vs. shelter-in-place

The most consequential decision in most scenarios is whether to leave or stay. Neither choice is universally correct — the wrong decision in either direction can be more dangerous than the event itself. Pre-commit to this framework before the scenario occurs:

Conditions that favor evacuation: - A mandatory evacuation order is in effect for your address or zone (never stay in a mandatory evacuation zone — this decision is made by officials with more information than you have) - Primary threat involves fire or flood that can outpace your ability to shelter (a wildfire moving at 1 mile (1.6 km) per hour is not survivable inside a residential structure) - A household member has a medical need that cannot be met on-site (insulin requiring uninterrupted refrigeration, oxygen concentrator requiring power) - Structural integrity of the dwelling is compromised

Conditions that favor shelter-in-place: - Roads are more dangerous than staying (evacuation traffic, flood-covered roads, ice conditions) - Threat is short-duration and indoor protection is effective (chemical spill with a defined perimeter, tornado warning) - No pre-identified destination with confirmed availability - Leaving requires passing through the hazard zone to exit

The threshold rule: Define in advance — measurably — at what point each of these conditions is met for your household. "If indoor temperature drops below 45°F (7°C) for more than 4 hours" is a threshold. "If it gets too cold" is not. Measurable thresholds remove decision-making from the moment of highest stress.

Phase escalation triggers: Define what shifts you from Phase 1 (monitor and prepare) to Phase 2 (active response) to Phase 3 (departure or full lockdown). For each scenario, these triggers should be stated as observable facts — temperature, water level, road status, utility status — not feelings or impressions.

Field note

A scenario plan that lives only in your head dies the moment stress hits. Write it down, walk through it with everyone who would execute it, and update it every six months — or after any real event, whichever comes first. The written version does not need to be comprehensive; it needs to be findable, readable under stress, and specific enough that a household member who has never seen it before could act on it.

Testing your scenario cards

A card that has never been walked through is untested theory. Run each new card through a 15-minute tabletop within one week of writing it:

Read the trigger condition aloud and ask: "Is this happening right now?"
Each household member states their first action from memory — then check the card
Verify that every resource listed in the inventory actually exists and is where the card says it is
Identify the single weakest link and fix it within 48 hours

Update cards after any real event, after any major household change (new member, new medication, new address), and during your annual OPSEC review.

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.