What scenario planning is — and the story that made it famous
Scenario planning starts from an admission most planning avoids: for some decisions, the future genuinely branches, and no amount of analysis will collapse it to one line. Rather than betting on a single forecast, you build a handful of structurally different, internally consistent futures and ask of your strategy: how does it fare in each?
The method's intellectual roots are in Herman Kahn's scenario work at RAND in the 1950s–60s — thinking the unthinkable about nuclear strategy by narrating it. Its business canonization came at Royal Dutch Shell, where Pierre Wack's planning group built scenarios in the early 1970s that included a future of producer-driven oil-price shocks. When the 1973 embargo hit, Shell's managers had already rehearsed the world they woke up in. Wack told the story — and the method's real lesson — in two 1985 Harvard Business Review pieces, "Scenarios: Uncharted Waters Ahead" and "Scenarios: Shooting the Rapids".
Wack's lesson is routinely missed by imitators: the scenarios' purpose is not prediction but re-perception — changing the mental models of the managers who must decide. A scenario deck that doesn't alter what anyone decides is, in Wack's framing, water on a stone. That standard — decision consequence — runs through everything below. Context in the toolbox: decision-making models; scenario planning's raw material comes from a PESTLE scan.
When to use it — and when not to
Scenario planning earns its considerable cost when:
- ✓The decision is long-lived and the environment genuinely branches. Infrastructure, platform bets, market entries with decade horizons — where being wrong about the world costs more than the exercise.
- ✓Key uncertainties are identifiable but not probabilizable. You can name the drivers (regulation tightens or not; a technology matures or stalls) without honestly being able to weight them.
- ✓The leadership's mental model is the risk. When everyone plans inside one 'official future', scenarios are the instrument that makes alternatives thinkable — their original Shell function.
And the failure modes — scenario planning fails more often than it works, usually one of these ways:
- ✗Scenarios as theater. Four vivid futures, a stimulating workshop, zero changed decisions. If no strategy, hedge, or trigger changed, the exercise failed by Wack's own standard.
- ✗The official future plus decoration. One scenario is the real plan; the others exist to make it look considered. The tell: capital allocation matches exactly one future.
- ✗Probability creep. Assign likelihoods and people optimize for the 60% world — collapsing the method back into the single forecast it was built to escape.
- ✗Indicators nobody watches. Early-warning signposts defined in the workshop and never monitored. A scenario system without a watch rota is a document, not a capability.
Step by step, with a worked example
Illustrative scenario: an invented European logistics company setting its five-year fleet strategy. The procedure:
- 1Frame the focal decision and horizon. "What fleet and charging infrastructure do we commit to over five years?" Scenarios without a focal decision drift into futurology.
- 2Identify driving forces. A PESTLE-style scan surfaces them: emissions regulation, battery cost curves, charging build-out, freight demand, labor supply, fuel prices.
- 3Split predetermined from uncertain. Wack's crucial move. Already in the pipeline: announced low-emission-zone rules, the age profile of the current fleet. Genuinely uncertain: pace of charging infrastructure; freight-demand structure (e-commerce vs industrial mix).
- 4Pick two axes, build the 2×2. Axis 1: charging infrastructure — fast build-out vs stalled. Axis 2: freight demand — fragmented/urban vs consolidated/long-haul. Four futures, each named and narrated until internally consistent: Wired & Local, Wired & Heavy, Stalled & Local, Stalled & Heavy.
- 5Test the strategy in each world. The all-electric-now plan thrives in the Wired futures and strands capital in the Stalled ones. The all-diesel plan inverts. A staged mixed fleet with conversion-ready depots survives all four — worse than the best bet in its best world, catastrophic in none.
- 6Derive moves, hedges, options, indicators. Robust move: depot conversion-readiness (cheap now, valuable everywhere). Option: contracted capacity with an EV supplier, exercised only in Wired worlds. Indicators with owners: quarterly charging-corridor build rate; e-commerce share of contract mix. Each indicator names who watches it and which decision it triggers.
Scenarios as an argument tree
In decision-quality terms, scenario planning feeds the frame (which world are we deciding in? — answer: several) and alternatives (strategies you'd never generate inside the official future). What the four narratives lack is a place where 'our strategy survives scenario A' gets examined rather than asserted. On an argument tree:
Strategy → root claim
"Commit to the staged mixed fleet." The recommendation stands at the root; the scenarios organize the case around it.
Each scenario → a branch of claims
"The staged fleet remains viable in Stalled & Heavy" is a claim, with supporting arguments (diesel capacity retained) and attacks (conversion capex partly stranded) — argued, not narrated.
Robustness → visible cross-branch support
A strategy that genuinely survives all four worlds shows four supported branches. One that secretly banks on the official future shows it — one strong branch, three thin ones.
Indicators fire → branches update
When the charging build-rate indicator crosses its threshold, the affected scenario branches take new evidence and the root's support shifts — the watch rota has somewhere to land its findings.
Scenarios supply frame and alternatives; the argument tree supplies the sound reasoning that turns four stories into one strategy you can defend in all of them. See decision quality.
Scenario planning vs the alternatives
| If your question is… | Reach for | Why not scenarios |
|---|---|---|
| The uncertainties are estimable — approval odds, demand ranges | Decision tree analysis | Probabilizable uncertainty deserves arithmetic, not narratives |
| What macro forces are even out there? | PESTLE analysis (feeds the scenario axes) | PESTLE lists drivers; scenarios combine them into worlds |
| Which risks do we manage continuously? | Enterprise risk management | ERM runs a register; scenarios stress whole strategies |
| Keeping the door open has value in itself | Real options thinking | Options price the flexibility scenarios reveal |