Scenario Planning

The Forecast That Keeps Dying

Every planning cycle for orbital governance begins with a curve: debris density, launch cadence, projected collisions, some extrapolated line of demand for space-based services. And every planning cycle, the curve gets it wrong. Not by a little — by enough that executives who built capital allocations around it end up rebuilding them within three years. A constellation operator plans for a permissive regime; the regime tightens. A national agency plans for binding multilateral rules; the rules fail to coalesce. An insurer prices premiums against a benign debris trend; a single rapid break-up event rewrites the actuarial table overnight.

The failure is not that the curves were badly drawn. It is that the question itself — “what will happen?” — has no honest single answer in a domain where critical variables remain genuinely unresolved. Orbital governance a decade or two from now will not be the product of a trend; it will be the product of which alliances form, which commercial standards gel, which near-miss incidents trigger political action, and which quietly do not. Several very different worlds are plausible. Decisions taken against only one of them are structurally brittle.

This is the problem scenario planning was built to solve. It replaces the single-forecast habit with a disciplined exercise in plural future-construction — and, more usefully, forces strategies to prove themselves against several of those futures before commitments are made.

The Method’s Unusual Parentage

Scenario planning sits at an odd genealogical junction. Its technical parents were nuclear strategists; its practical parents were oil executives; its public voice came from the consulting networks of the late twentieth century.

Herman Kahn, working at RAND in the 1950s and early 1960s, developed the habit of writing out multiple “alternative futures” as a way of thinking about thermonuclear war. Kahn’s work, controversial then and since, rejected the idea that one could assign probabilities to unthinkable outcomes and instead insisted on reasoning through the structure of each possible world. Thinking the unthinkable, he argued, was the only way to avoid being paralyzed by it.

Pierre Wack carried the idea out of the defense world and into Royal Dutch/Shell through the late 1960s and the 1970s. Wack’s teams were assigned to prepare Shell’s planners for futures that did not match the consensus. Two of his scenarios — the ones that envisaged a radical realignment of oil-producing power — were dismissed by most executives when written. When the first oil shock landed in 1973, Shell was among the few majors already positioned intellectually to absorb it. Scenario planning’s reputation as a strategic tool was secured not by its elegance but by that outcome.

Peter Schwartz, who apprenticed under Wack and later co-founded the Global Business Network in 1987, translated the Shell practice into a more teachable craft and exported it to corporate and governmental clients. The 2×2 matrix of critical uncertainties that most practitioners now treat as canonical is in large part Schwartz’s pedagogical simplification of what Wack and his colleagues had done more fluidly. The simplification is honest about its own cost: what the matrix gives in accessibility it takes in nuance.

What Scenarios See That Forecasts Do Not

The analytical gesture at the center of scenario planning is deceptively simple. Identify the driving forces that shape a strategic domain. Among those, isolate the two that are simultaneously most consequential and most genuinely uncertain. Cross them. Four worlds appear. Each world gets a narrative. Each narrative gets early-warning signals. Every strategy under consideration is then walked through every world and judged on its performance.

What this gesture accomplishes — and why it has survived six decades of methodological fashion — is a reframing of the strategic question. Instead of “what is the future?” the practitioner is compelled to ask “which future are we being prepared for, and which are we ignoring?” The method’s power is not predictive; it is diagnostic. It reveals the hidden assumptions embedded in the strategies an organization is already pursuing.

A forecast compresses uncertainty into a single estimate, often with error bars that are themselves an artifact of the forecaster’s priors. A trend extrapolation assumes that past drivers will continue to shape future outcomes with roughly their current weight. Both are useful when the future resembles the past. Scenario planning is designed for the cases where that assumption is known to be fragile — where a shift in alliance structures, regulatory posture, or technological substrate could invalidate the trend entirely.

The discipline is in the orthogonality of the axes. If the two uncertainties chosen for the matrix turn out to be correlated — if “commercial market maturity” and “regulatory activism” move together — then the four quadrants collapse into a diagonal and the exercise has learned nothing. The hardest intellectual work in scenario construction is not the narrative writing but the axis selection: verifying that the two chosen dimensions can in fact vary independently, and that they together span the space of outcomes worth worrying about. Practitioners who skip this step produce beautifully written scenarios that are really a single forecast in four costumes.

The second discipline is in the equiprobability commitment. The method insists that no scenario be presented as “most likely.” The moment analysts rank the quadrants by probability, decision-makers hear “central case” and “edge cases,” and the organization quietly returns to single-point planning with extra steps. Scenarios are tools for exposing strategic fragility; they are not substitutes for forecasts.

A 2×2 for Orbital Debris

Consider the focal question an executive team at an in-orbit servicing company might set: what will the orbital debris governance regime look like by 2040, and which of our product lines is robust to that future? The first pass at driving forces yields a familiar list — launch cadence, major collision events, great-power alignment, commercial insurance pricing, national licensing regimes, the maturity of active debris removal technology, public attitudes toward space activities.

Two of those forces keep surfacing as both high-impact and genuinely undecided: the degree of international cooperation on binding rules, and the effectiveness of commercial self-regulation — industry-led standards, deorbiting practices, and on-orbit norms that either do or do not hold without state enforcement. Cross them and four worlds appear.

The non-obvious insight falls out when the company’s product portfolio is walked through all four. A premium active-debris-removal service performs well in worlds one and two and poorly in worlds three and four — it depends on a liability regime that either exists or is being forced into existence. A cheaper rendezvous-and-proximity product performs acceptably in worlds two, three, and four, because all three have a growing problem and at least some willing buyers. The portfolio’s apparent crown jewel turns out to be the most fragile. That is the kind of finding a single forecast never produces.

What It Does Well and Where It Zoppica

Scenario planning’s strength is exposing hidden strategic fragility. It is unmatched for stress-testing commitments against divergent futures over five- to thirty-year horizons. It handles ignorance honestly: rather than pretending to probabilities that do not exist, it lets the practitioner reason across a bounded space of plausible worlds. And it produces artifacts — the matrix, the narratives, the signposts — that survive in institutional memory and give later analysts something to update rather than something to re-invent.

Its weaknesses are largely the mirror image. The 2×2 is a pedagogical compression; real problems often have three or four critical uncertainties, and forcing two axes can smuggle the others into the narratives where they become invisible assumptions. Equiprobability, while methodologically essential, is psychologically unstable — teams drift back toward a “central case” the moment the workshop ends. Scenarios can become literary exercises disconnected from operational levers if the authors are more skilled at narrative than at causal mechanics. And the method is expensive: a serious scenario exercise consumes weeks of analyst time and days of executive attention, which is why it is so often replaced by its cheaper cousin, sensitivity analysis, and why the substitution so often disappoints.

It also cannot answer certain questions. It will not tell an executive which scenario is closest to materializing — only which signposts to watch. It will not value a strategy in financial terms, which is why a pairing with real-options thinking is common. It will not model strategic interaction among rivals; for that, game theory is the complement. And it does not generate the signal inventory on which its own driving-forces list depends — horizon scanning is a prerequisite, not an output.

The method library treats scenarios as the middle of a chain. Horizon scanning and trend analysis feed the driving-forces inventory upstream. Backcasting takes a chosen scenario endpoint and works backward to a pathway. Resilience analysis supplies the stress-test variables against which scenario robustness is checked. Game theory sharpens the actor dynamics within a scenario. A scenario exercise run without those neighbors is a scenario exercise run with one hand tied.

For the Practitioner