Skip to main content

Scenario Planning

TL;DR

Scenario Planning: Instead of predicting one future, build 3–4 structurally distinct plausible futures and design strategies that work across all of them. Strategy that only works in the expected future is a bet, not a plan.


What Is Scenario Planning?​

Most strategic planning is secretly prediction dressed up as planning. Executives project growth rates forward, make assumptions about competitive dynamics, and build plans optimized for those assumptions. The plan works beautifully if the assumptions hold — and falls apart when they don't.

Scenario Planning was developed to fix this. Its intellectual origins trace to Herman Kahn at the RAND Corporation in the 1950s, who applied it to nuclear war strategy — a domain where uncertainty was so extreme that single-point forecasting was obviously insufficient. The corporate application was pioneered by Pierre Wack and Ted Newland at Royal Dutch Shell in the early 1970s.

Shell's story is the model's most famous validation. In 1972, Wack and his colleagues developed scenarios for the global oil market. One of those scenarios described a world in which OPEC would successfully coordinate a production cut, producing an oil price shock. When the 1973 oil crisis arrived, Shell had already stress-tested its strategy against that future. While competitors scrambled, Shell adapted rapidly — moving from the seventh-largest oil company in the world to the second within a few years. The scenario didn't predict the crisis; it prepared Shell to recognize and respond to it faster than anyone else.

The core insight: the value of Scenario Planning is not that one scenario will be correct. It is that having thought rigorously through multiple futures, you will recognize reality faster when it arrives — and you will have already thought through your response.

Modern Scenario Planning diverges from prediction in a specific way: it does not assign probabilities to scenarios. The moment you do that, you will unconsciously optimize for the most likely one and treat the others as background. Instead, scenarios are treated as equally serious objects of strategic preparation.


How It Works​

Step 1: Identify the Focal Question
What specific strategic decision or time horizon are we planning for?
Example: "What should our go-to-market strategy be for 2026–2028?"

Step 2: Identify Critical Uncertainties
What are the 2–3 most important variables that are:
(a) highly uncertain — we genuinely don't know which way they'll go
(b) highly impactful — if they go differently, our strategy must change

Separate from "known trends" (certain, should be planned for) and
"predetermined elements" (very likely, high confidence)

Step 3: Build the Scenario Matrix
From 2 critical uncertainties, build 4 scenarios (2×2 matrix).
Name each scenario evocatively — names aid recall and communication.

Example axes:
X: AI commoditizes our core features / AI creates new value
Y: Enterprise budgets recover / Budget environment remains tight

Step 4: Develop Each Scenario Into a Narrative
Write 1–2 pages per scenario: what does the world look like in 3 years?
Who are the winners? What does our industry look like? What do customers
care about? What does our competition look like?

Step 5: Test Your Current Strategy Against Each Scenario
For each scenario: does our current plan work?
If our plan only works in the expected scenario, it is a bet, not a strategy.

Step 6: Identify Robust Moves and Early Warning Signals
Robust moves: investments that are valuable across multiple scenarios
Early warnings: what observable events would signal that a specific
scenario is becoming reality, allowing early adaptation?

Three Real-World Examples​

Shell and the 1973 Oil Crisis​

Shell's planning team identified two critical uncertainties in 1972: OPEC's ability to coordinate, and Western governments' energy policy response. Their "surprise" scenario described successful OPEC coordination producing an oil shock. They didn't know if it would happen, but they developed a full narrative of what that world would look like and what Shell should do.

When the crisis arrived in October 1973, Shell's managers recognized the scenario they'd already studied. They didn't need to convene an emergency strategy session — they'd already had it. Shell redirected capital away from refining capacity (which would be stranded in a high-price world) and toward exploration in non-OPEC regions. Competitors who hadn't done the scenario work made those capital allocation decisions months later and at higher cost.

The lasting lesson: the scenario didn't give Shell perfect knowledge. It gave them a decision framework that activated the moment reality aligned with one of the prepared futures.

Google's 2005 Mobile Strategy​

Google's strategy team in 2005 built scenarios around smartphone adoption — then a genuinely uncertain outcome. The critical uncertainties: would carriers control the smartphone experience (protecting their data revenue), or would open platforms emerge? Would enterprise or consumer use cases dominate the early market?

The scenario where open platforms prevailed with consumer-first use cases pointed toward a specific investment: a mobile operating system that Google could give away free, ensuring Google Search remained the default on whatever devices came to dominate. Android was not the product of predicting iPhone's success — it was a robust move that created value across multiple scenarios, including the one where Apple won.

The key insight: Android was valuable even in the scenarios where it didn't win market share, because it set pricing expectations that prevented carriers and Microsoft from locking Google out of mobile search.

COVID-19 Pandemic Response (2020)​

Organizations that had pandemic scenarios in their business continuity plans — hospitals, logistics companies, some governments — moved to remote operations weeks faster than those that hadn't. The specific scenario (coronavirus, Wuhan origin, exponential spread) hadn't been modeled exactly, but the "respiratory pandemic requiring mass remote work" scenario was available.

The classic Scenario Planning lesson: the organizations that had thought through an extreme scenario were not more correct about the future. They were faster to adapt when reality resembled their preparation.


When to Use It​

✅ Use Scenario Planning when:

  • Planning with a 3–10 year time horizon in a volatile environment
  • A major strategic decision depends heavily on uncertain external factors
  • You need leadership alignment on how to respond to different futures
  • The cost of being wrong in a single-scenario plan is high
  • You're in an industry subject to technological disruption, regulatory change, or geopolitical volatility

❌ Skip or simplify when:

  • Time horizon is less than 12–18 months (scenarios are most valuable over longer periods)
  • The key variables are actually predictable (demographic trends, contracted revenue)
  • The decision is reversible and low-cost — Two-Way Door decisions don't need scenarios
  • You lack the facilitation time (well-executed scenario work takes 2–5 days of leadership time)
Pairs well withWhy
InversionScenario narratives benefit from imagining failure modes in each
Pre-mortemRun a pre-mortem within each scenario
OODA LoopScenarios define what to Orient toward; OODA structures the response
Second Order ThinkingScenarios are an extended form of second-order consequence mapping

Common Misuses and Limitations​

Building scenarios that are really just optimistic/pessimistic versions of one future. True scenarios are structurally distinct — different causal stories, not different magnitudes of the same story. "High growth" and "low growth" are not scenarios. "AI commoditizes our product" and "AI creates a new market we can enter" are scenarios.

Assigning probabilities. The moment you label one scenario "most likely" (80%), you have essentially returned to single-point planning. Everyone prepares for the 80% scenario and the 20% ones get lip service.

Doing the work but not building decision triggers. Scenarios without early warning signals and pre-specified responses are interesting documents but not strategy. For each scenario, define: what observable event would tell us this scenario is materializing? What is our playbook response?

Treating scenarios as forecasts and being frustrated when they're wrong. Scenarios are not meant to be correct. They are meant to expand the range of futures your organization has seriously prepared for.


  • Second Order Thinking — the thinking discipline underlying scenario construction
  • Inversion — essential within each scenario's failure analysis
  • Commander's Intent — communicating the strategic direction that must hold across scenarios
  • Black Swan Theory — the scenario planning edge case: what if the future is entirely outside your scenario set?

FAQ​

How many scenarios should you build?

Three or four. Two scenarios tends to collapse into best/worst case thinking. Five or more is cognitively unmanageable and dilutes preparation. The standard practice — developed at Shell and widely adopted — is a 2×2 matrix of two critical uncertainties producing four distinct scenarios. Each gets a name and a full narrative.

How do you choose the critical uncertainties?

Two tests: (1) high uncertainty — you genuinely don't know which direction this variable will go; and (2) high impact — if it goes differently, your strategy must fundamentally change. Common candidates: technology disruption timing, regulatory outcomes, competitive entry, customer behavior shifts, macroeconomic conditions. Avoid "known trends" (factors you're confident about) — those belong in all scenarios as constants.

How is Scenario Planning different from risk management?

Risk management identifies specific risks and attaches probabilities and mitigation plans. Scenario Planning doesn't require probabilities and isn't organized around risks — it's organized around fundamentally different futures. The two complement each other: scenarios define the range of futures; risk management handles specific threats within each. In practice, scenario work often feeds into risk registers by expanding the set of risks worth managing.


Apply with AI​

🚀 Apply Scenario Planning to your strategy in MindMax →


Further Reading​

  • Peter Schwartz, The Art of the Long View (1991) — The definitive practitioner's guide to Scenario Planning, written by Shell's head of planning.
  • Pierre Wack, "Scenarios: Uncharted Waters Ahead" (Harvard Business Review, 1985) — The original Shell practitioner account.
  • Kees van der Heijden, Scenarios: The Art of Strategic Conversation (1996) — The academic treatment with deep methodology.

This page is part of the MindMax Mental Models Knowledge Base.