Scenario Planning: How to Build a Strategy That Survives More Than One Future

Scenario planning builds a product strategy around several plausible futures instead of one forecast, using critical uncertainties to construct two to four named scenarios, then classifying moves as no-regret (do now, works everywhere) or contingent (wait for a signal). It replaces false precision with resilience — the strategy survives even when reality doesn't follow the plan.

Quick answer: Forecast for what's stable; build scenarios for what isn't. Pick your two highest-impact critical uncertainties, cross them into a 2x2 to name four futures, then split your roadmap into moves that win everywhere and bets you fund only when a signal confirms which future is arriving.

Most product strategies are built the way most financial models are built: pick the most likely number, plan around it, and hope the variance stays small. That works fine when the underlying drivers of your market are stable.

It fails, often expensively, the moment you're operating in a regulated industry where a single ruling can rewrite the addressable market. It fails just as fast in a volatile one, where a competitor's pricing move or a funding winter can invalidate a roadmap in a quarter. Scenario planning is the discipline built for exactly that condition.

Forecasting vs. Scenario Planning: Two Different Tools for Two Different Problems

Forecasting produces one number for one future and works when the underlying drivers are stable and well understood. Scenario planning produces several coherent, internally consistent futures and works when drivers are volatile, contested, or partly outside your control. Regulated and volatile markets need the second tool, because a single-point forecast is a bet dressed up as a plan.

The distinction isn't cosmetic. A forecast asks "what will happen?" A scenario set asks "what are the several different things that could plausibly happen, and how do we win reasonably well across all of them?" The second question is harder to answer but far more honest about what a product leader actually controls.

Why Point Forecasts Fail in Regulated and Volatile Markets

The clearest historical case is Royal Dutch Shell in the early 1970s. Planner Pierre Wack built scenarios around oil-producing nations gaining pricing power years before the 1973 oil shock, while competitors ran single-point forecasts extrapolated from stable postwar prices. Shell wasn't clairvoyant — it was prepared for a future its rivals had planned out of existence.

The technique itself traces further back to Herman Kahn and the RAND Corporation, who developed structured scenario methods for Cold War-era military and strategic planning in the 1950s, before the approach migrated into corporate strategy.

Regulated markets behave the same way today. A single ruling on data portability, model auditability, or capital requirements can reclassify your entire feature roadmap overnight. Planning around one regulatory forecast is planning to be surprised.

What Scenario Planning Is Not

It is not brainstorming without structure, and it is not a hedge that lets you avoid committing to anything. Kees van der Heijden, in Scenarios: The Art of Strategic Conversation, distinguishes it from simple contingency planning: contingency planning asks "what do we do if X happens," while scenario planning asks a prior question.

That prior question is "what are the small number of futures worth planning around at all, and are we sure we've named the right ones?" It's a discipline for narrowing infinite uncertainty to a workable few, not multiplying it.

This is one tool inside a broader kit — see the complete guide to advanced product strategy for how it sits alongside portfolio thinking, competitive positioning, and platform strategy.

Step 1 — Name Your Critical Uncertainties

Critical uncertainties are the two or three forces that would most change your strategy if they resolved differently, and that you genuinely cannot predict. You find them by first separating what's already determined from what's still contested, then ranking the contested factors by how much impact they'd have and how unpredictable they really are.

Van der Heijden calls the first category predetermined elements — demographic shifts, signed legislation, physical infrastructure already built. These belong in every scenario identically; there's no branching to model. Everything left over is a candidate critical uncertainty.

Useful prompts for surfacing candidates in a regulated or volatile market:

• How will regulators treat your product category — permissively, or with tightening restriction?
• How fast will customers and competitors adopt the underlying technology shift you're betting on?
• Will the market consolidate around a few dominant platforms, or stay fragmented?
• Is capital availability for your category expanding or contracting?
• Will customer risk tolerance rise or fall given macro conditions?

Predetermined Elements vs. Genuine Uncertainties

Teams frequently waste scenario-planning cycles branching on things that are actually settled. If a regulation has already passed and only its enforcement timeline is unclear, the timeline might be a genuine uncertainty, but the regulation's existence is not. Separating the two keeps your scenario tree from exploding into a dozen near-identical branches.

Grounding this in what customers are actually trying to accomplish also narrows the list. The Jobs to Be Done framework is useful here because it separates uncertainty about the underlying job — rarely contested, since core human and business jobs shift slowly — from uncertainty about how the job gets solved, which is almost always where the real volatility lives.

Ranking Uncertainties by Impact and Unpredictability

Score every candidate uncertainty on two axes: how much it would change your strategy if it resolved one way versus another, and how genuinely unpredictable it is today. Plot them on a simple grid. The one or two uncertainties in the high-impact, high-unpredictability corner are your critical uncertainties — everything else either gets treated as predetermined or set aside as noise.

If a meaningful share of your uncertainty is technical rather than regulatory — which underlying components will commoditize, which will stay custom-built — mapping the evolution of those components the way Wardley Mapping does is one of the fastest ways to tell a settled technical bet from a genuinely contested one.

Step 2 — Build Four Scenarios With the 2x2 Axes Method

Cross your two highest-ranked critical uncertainties into a 2x2 grid, name each quadrant with a memorable, story-driven label, and write a short narrative for each describing how the market, customer behavior, and competitive landscape look inside it. Four named, internally consistent futures beat one detailed forecast, because they force you to plan for the futures you'd rather ignore, not just the one you expect.

Say you're building underwriting software for community banks — a genuinely regulated, genuinely volatile category. Two critical uncertainties might surface: regulatory posture toward AI-assisted underwriting (permissive to restrictive), and the pace at which banks and their customers actually adopt automated decisioning (slow to fast). Crossed into a 2x2, four scenarios emerge:

Each of these implies a different roadmap emphasis — Open Highway rewards shipping fast, Walled Garden rewards investing early in audit trails and explainability tooling. No single forecast captures that range; a strategy built for only one quadrant is a bet, not a plan.

Naming Scenarios So They Stick

Resist the temptation to call these "Scenario A" through "Scenario D." Peter Schwartz, in The Art of the Long View — the book that carried scenario planning from Shell and the co-founded Global Business Network into mainstream corporate strategy — argues that a scenario only changes behavior if people can hold it in their heads and argue about it in a hallway. A name like "Walled Garden" does that job; a label does not.

A vision statement that's memorable enough for people to repeat should hold up across every one of your named scenarios. If your vision only makes sense in one quadrant, it's describing a bet on that future, not a strategy resilient to the others.

Stress-Testing Each Scenario for Internal Consistency

A scenario has to be a coherent story, not just an extreme combination of two variables. Ask, for each quadrant: what chain of events would plausibly lead here, and does every detail in the narrative actually belong to the same world? A scenario where regulation is restrictive but enforcement is nonexistent isn't "restrictive" — it's a different, uncounted fifth scenario wearing the wrong label. Discard or rewrite anything that fails this test before you build a roadmap on top of it.

Step 3 — Sort Moves Into No-Regret and Contingent Bets

No-regret moves win in all four scenarios and should be funded now, regardless of which future arrives. Contingent bets only pay off in specific scenarios and should be funded only after an early-warning signal confirms that scenario is actually unfolding. This split is what turns four interesting futures into one prioritized, fundable roadmap.

No-regret moves in the underwriting example above might include:

1. Building an audit trail and explainability layer into every automated decision, since it helps in Walled Garden and costs little in Open Highway.
2. Investing in core data infrastructure and integration quality, since every quadrant rewards a faster, cleaner pipeline.
3. Deepening trust-building assets — references, case studies, security certifications — since Quiet Runway and Frozen Field both reward them, and they don't hurt in the faster-moving quadrants either.

Contingent bets, by contrast, only make sense once a scenario starts confirming itself: heavy investment in self-serve automation only pays off if adoption pace turns out to be fast; deep, bank-by-bank compliance customization only pays off if the regulatory posture turns out restrictive. Fund these provisionally, with a named signal that triggers full investment — not by gut feel.

This is also where scenario planning either becomes real or dies as a slide deck. The gap between a strategy deck and daily execution is exactly where no-regret moves get forgotten under sprint pressure and contingent bets get funded early out of habit, before any signal has actually confirmed the scenario behind them.

Step 4 — Install Early-Warning Signals and Revisit Assumptions as a Habit

Early-warning signals are specific, observable, time-bound indicators tied to each scenario — a regulatory filing, an adoption metric crossing a defined threshold, a competitor's pricing move — that tell you which future is actually arriving before it's obvious from your own revenue numbers. Without signals attached to each scenario, scenarios are just interesting stories nobody ever acts on.

For every scenario, write down the two or three things you'd expect to observe in the world if that future were starting to unfold, and where you'd watch for them.

Rita McGrath, in Seeing Around Corners, calls these inflection-point signals — and argues most organizations miss them not because the data wasn't available, but because nobody owned watching for it. The Cynefin framework, developed by Dave Snowden, makes a related point: in a complicated domain, expert forecasting works; in a complex domain — most regulated, fast-moving product markets — the honest move is to probe, sense, and respond to signals rather than predict outright.

Watching where customer sentiment actually shifts along the customer journey emotion curve is often a faster early-warning signal than a lagging metric like revenue, because behavior and mood tend to shift before the numbers catch up.

Making the Signal Review a Recurring Habit, Not a One-Time Workshop

Scenarios go stale the moment they're filed away after the offsite that produced them. McKinsey & Company's guidance on planning under uncertainty has consistently pushed executives to revisit scenario assumptions on a fixed cadence — quarterly is common — rather than treating a scenario exercise as a single annual event. The assumptions underneath each scenario need an owner, a place to live, and a scheduled moment where someone actually asks whether the evidence still supports them.

This is the part most scenario-planning exercises quietly skip, and it's where a habit beats a workshop. Every scenario rests on a handful of specific assumptions — "regulators will move slowly," "banks will resist automation past 2027" — and those assumptions need to be written down individually, not buried inside a paragraph of narrative, so they can be checked one at a time.

Key Takeaways

• Forecasting and scenario planning solve different problems. Use a forecast when drivers are stable; build scenarios when they're volatile, contested, or regulatory — a single-point forecast in a regulated market is a bet, not a plan.
• Critical uncertainties, not every uncertainty, drive the exercise. Separate predetermined elements from genuinely contested ones, then rank by impact and unpredictability to find the two that matter most.
• The 2x2 axes method turns two uncertainties into four named, story-driven scenarios — memorable names make scenarios something a team can actually argue about and act on, not a slide nobody remembers.
• No-regret moves get funded now; contingent bets wait for a signal. This split is what makes four futures produce one prioritized roadmap instead of four unfunded ones.
• Early-warning signals are what make scenarios actionable rather than decorative — define specific, observable indicators per scenario and assign someone to actually watch for them.
• Revisit scenario assumptions on a fixed cadence, not just at the workshop that produced them; assumptions decay as the real future reveals itself.