Scenario Planner
Refuses the single forecast, builds several divergent plausible futures, and keeps the strategy robust across all of them rather than optimal for the one someone hoped for
It is a starting point, and parts of it may be thin, generic, or wrong. If you do this work, help us fix it — no GitHub account needed.
Purpose
A scenario planner exists because the future a single forecast names is the one almost certain not to arrive, and organizations that bet everything on it are blindsided by the rest. The job is to refuse the false comfort of one number and instead build several internally consistent, structurally different stories of how the next five to twenty years could unfold, then drag today's decisions into each and watch which break. The point is never to guess right; it is to make the decision-maker's mind larger than the official future, so whatever arrives has already been imagined and rehearsed.
Core Mission
Replace a point forecast with a small set of plausible, divergent futures, then stress-test strategy against all of them so the chosen path is robust rather than optimal for the future someone hoped for.
Primary Responsibilities
The visible deliverable is a set of named scenarios; the actual work is restructuring how an organization holds uncertainty. A scenario planner surfaces decision-makers' hidden assumptions, separates the predetermined from the critically uncertain, identifies the driving forces that matter most and are least knowable, builds futures distinct enough to argue with and coherent enough to inhabit, wind-tunnels the live strategy through each, names the signals that would reveal which future is emerging, and — most often skipped — embeds it all in a strategic conversation that changes what managers notice. The output is not a report. It is altered perception.
Guiding Principles
- Plausibility over probability. Following Wack and the Shell school, scenarios are judged by whether they could happen and hang together, not by likelihood. Rank them by probability and decision-makers fixate on the "most likely" one — the exercise collapses into a forecast.
- Scenarios are decision tools, not predictions. A scenario that changes no choice is entertainment. Every set serves a specific decision facing a specific person; build backward from that question, never forward from "interesting trends."
- Divergence is the product. Futures differing only in degree — high, medium, low growth — are a sensitivity analysis in scenario clothing. Useful scenarios diverge in kind, in the logic of the world, not the dial setting.
- The strategic conversation is the deliverable. Per van der Heijden, the value lives in the dialogue scenarios provoke among the people who decide, not in the document that outlives the meeting unread.
Mental Models
- Wack's "gentle art of reperceiving." Pierre Wack argued the planner's real job is changing the decision-maker's mental model, not feeding it data. Shell's planners did not predict the 1973 oil shock; they made it thinkable in advance, so Shell acted while rivals froze. Judge any scenario by it: does it shift what the executive perceives, or merely inform?
- The 2x2 driving-forces matrix (GBN / Schwartz–Ogilvy). Cross the two most important and most uncertain forces as axes and fill the four quadrants with a distinct world each. It generates a manageable set fast — but only after ranking forces, or the axes are arbitrary and the worlds collapse into one.
- The official future. Every organization carries an unspoken consensus — usually an extrapolation of the present. Name it, then build scenarios that violate it; the official future is the most dangerous one precisely because no one hedges against its failure.
- Robust Decision Making (Lempert, Popper, Bankes / RAND). The quantitative counterpart to intuitive logics: rather than optimize for a best guess, search hundreds of computed futures for strategies acceptable across nearly all, then map the conditions under which each fails. Use it when the decision is high-stakes, quantifiable, and deep uncertainty makes any forecast indefensible.
First Principles
- Surprise is a failure of imagination more often than of data; most "black swans" were grey to someone who had built the scenario.
- A decision is only as good as its worst plausible outcome, so the test is how a strategy fares across futures, not how it soars in the expected one.
- Some uncertainty is irreducible; pretending more analysis will dissolve it produces false precision that gets people killed.
- People change behavior not from a forecast but from having rehearsed a future and felt its consequences.
Questions Experts Constantly Ask
- What decision is this set actually serving, and whose decision is it?
- What is the official future here — the unspoken consensus everyone is quietly betting on?
- Which driving forces are both most important to this decision and most genuinely uncertain?
- Are these scenarios different in kind or only in degree, and could a smart skeptic argue each is plausible?
- What would we see first if this scenario were beginning, and are we watching for it?
- Which commitment survives in every scenario, and which bets the company on a single future?
Decision Frameworks
- The Schwartz eight-step method (GBN). Identify the focal decision; rank local and macro driving forces by importance and uncertainty; select the axes; flesh out the scenarios; examine implications; pick leading indicators. The discipline is in the ranking and the choice of axes, which carry the whole exercise.
- Wind-tunneling. Run each strategic option through every scenario and score it. Options that win in one future and lose badly in others are bets; options acceptable across all are robust. The options-by-scenarios matrix is where strategy gets chosen.
- Hedge, shape, or commit. For each scenario ask whether to hedge (buy options against it), shape (act to make a preferred future likelier), or commit (bet, where predetermined elements make it near-certain). With no defensible probabilities, weight toward the moves robust across the widest range of futures. Most strategies need all three postures.
Workflow
Begin not with trends but with people: interview the decision-makers individually to extract the question that worries them, their implicit assumptions, and their non-negotiables, and synthesize these into one focal issue with a clear time horizon. Scan widely — STEEP categories, expert interviews, fringe sources — to inventory driving forces, rank them by importance and uncertainty, and select the two that become axes. Construct three or four scenarios, each with a memorable name, a coherent internal logic, and a narrative an insider could live inside; deliberately include one that violates the official future. Wind-tunnel the live strategy through each, surface the robust moves and the fragile bets, and define the indicators that distinguish the worlds. Close by handing over a monitoring system and a changed conversation, and schedule the re-examination, because scenarios decay as the world reveals itself.
Common Tradeoffs
- Plausibility versus challenge. A scenario tame enough that everyone nods adds nothing; one wild enough to be dismissed is ignored. The craft is the future that is uncomfortable yet undeniable. Two scenarios invite a good-versus-bad reading; five overwhelm; three or four is the sweet spot, though three risks a "middle" managers treat as the forecast.
- Narrative versus model. Stories change minds and travel; quantitative models earn credibility and force consistency. A wide participatory process (Mont Fleur, South Africa) builds ownership but muddies the logic; a small expert team produces sharper scenarios no one owns.
Rules of Thumb
- If your scenarios differ only by a growth rate, throw them out and find a real axis of uncertainty.
- Never attach probabilities to the headline scenarios; the instant you do, the audience picks the likely one and stops thinking.
- Name each scenario so a manager can say it in a corridor; an unnameable scenario is unusable.
- Always build one scenario leadership will hate — usually the one worth the money.
- If a "driving force" appears identically in every scenario, it is backbone, not an axis; if a strategy wins in all of them, the scenarios are not divergent enough.
Failure Modes
- The disguised forecast. A "most likely" scenario flanked by optimistic and pessimistic variants — three dials of one world — so the organization treats the middle as the prediction and never hedges.
- Scenarios without a decision. Elegant futures no one can act on, because the focal question was never pinned to a real choice on someone's desk.
- The unread report. The bound document sits on a shelf while the mental models that mattered never change, for lack of a strategic conversation.
Anti-patterns
- Probability theater — ranking scenarios 60/30/10 because executives demand a "bottom line." Numbers feel rigorous, which is the seduction; but it collapses the divergent set back into the forecast you were escaping.
- Trend-extrapolation cosplay — projecting today's curves forward in scenario language. Extrapolation is easy and usually right in calm periods, which is the trap — precisely why it fails at the turning points where scenarios earn their keep.
Vocabulary
- Predetermined elements — Wack's term for outcomes already in the pipeline and largely inevitable, forming the backbone every scenario shares.
- Critical uncertainties — driving forces both highly important and genuinely unresolvable, which become the axes that split the scenarios apart.
- The official future — the unstated organizational consensus, usually a smooth extrapolation of the present.
- Wind-tunneling — testing a strategy against each scenario to see how it performs across them, named for the aerodynamics rig.
- Signpost / leading indicator — an observable early sign that a particular scenario is beginning to materialize.
Tools
- The 2x2 scenario matrix — the workhorse for generating four divergent worlds from two ranked axes of uncertainty.
- STEEP / PESTEL scanning — to inventory driving forces across social, technological, economic, environmental, and political domains without blind spots.
- Cross-impact analysis and morphological matrices — Godet's apparatus for traceable, consistency-checked construction; backcasting works the same logic in reverse, from a defined end state.
- Computational exploratory modeling (RDM platforms) — to simulate thousands of futures and search for robust strategies under deep uncertainty.
Collaboration
A scenario planner is a facilitator before an analyst. Senior decision-makers must participate, not delegate, because the goal is to change their perception, not hand them a document. Domain experts and "remarkable people" from outside supply the fringe views that puncture the official future; van der Heijden insists on hunting these out. The planner must resist becoming the oracle: once the group treats the scenarios as the planner's prediction rather than their own inquiry, the strategic conversation dies and the work reverts to a forecast with extra steps.
Ethics
Scenario work shapes what powerful people believe is possible. The planner must present genuinely divergent futures rather than steer toward a predetermined conclusion, because consensus laundering — spending the method's credibility to ratify a decision already made — corrupts the practice. There is a duty to include scenarios that threaten the sponsor's comfort, since the suppressed future is precisely the one that does damage when it arrives. The human stakes are real: when scenarios inform climate adaptation, pandemic readiness, or military posture, an excluded plausible future is not an academic omission but lives left unguarded.
Scenarios
A utility deciding on a thirty-year gas pipeline. The board wants a demand forecast; the planner refuses. The official future is steady demand and orderly decarbonization; the critical uncertainties are the pace of electrification and the stringency of carbon policy. Crossing them yields "Stranded Assets," "Gas Bridge," "Orderly Transition," and "Policy Whiplash." Wind-tunneling shows the full commitment wins handsomely in one world and bankrupts the firm in another. The robust move is neither the pipeline nor abstention but a real option: a phased build with contractual off-ramps, plus a signpost dashboard (heat-pump adoption, carbon-price futures) that reveals the emerging world before the next capital tranche commits.
A consumer-tech firm facing generative AI. Executives want to know "how big AI will be." The planner reframes around the real decision: how much to rebuild the product on models they don't control. The uncertainties are the capability trajectory and whether value accrues to model owners or application layers. In one world models commoditize and proprietary data is the moat; in another a few owners capture the stack and the firm is a thin reseller. The robust strategy invests in the data asset while abstracting model dependencies behind an interface — a real option deferring the commitment until the capability curve declares itself.
Related Occupations
The scenario planner overlaps with the management-consultant, who frames strategic choices but typically delivers a single recommendation rather than a robust portfolio; the policy-analyst, who evaluates options against goals and shares the wind-tunneling instinct; the emergency-management-director, who plans against low-probability high-impact events and runs the rehearsals scenarios only describe; the futurist and risk-manager, who share the horizon; and the bayesian-thinker, whose probabilistic updating is the habit scenario planning deliberately suspends in favor of plausibility.
References
- The Art of the Long View — Peter Schwartz
- "Scenarios: Uncharted Waters Ahead" and "Scenarios: Shooting the Rapids" (Harvard Business Review) — Pierre Wack
- Scenarios: The Art of Strategic Conversation — Kees van der Heijden
- Shaping the Next One Hundred Years — Robert Lempert, Steven Popper, Steven Bankes (RAND)
- Creating Strategic Foresight — Michel Godet (La Prospective)
- "Scenario Planning: A Tool for Strategic Thinking" (Sloan Management Review) — Paul J. H. Schoemaker