Most strategic plans are built to answer a single question: what should we do next? Scenario planning starts from a different, more useful question: what happens to our plan if the world does not behave the way we assumed it would? That distinction sounds academic until an organisation actually lives through an assumption failing — a market that does not grow, a partner that does not deliver, a piece of infrastructure that takes three times as long to build as forecast — and discovers that its strategy had no answer ready.
These are the questions raised repeatedly in conversations with policymakers and business leaders at forums such as the World Economic Forum in Davos, and in discussions on strategy and infrastructure with outlets such as The Economist: not what the future will look like, but how confidently an organisation can commit capital and reputation to a single version of it.
Planning for outcomes, not predictions
The instinct in most strategy processes is to forecast: to produce a single view of the future and build a plan around it. Scenario planning resists that instinct deliberately. Rather than predicting one future, it builds two or three genuinely different, internally consistent futures and asks which decisions hold up across all of them, and which only make sense in one.
That discipline is particularly valuable for large infrastructure and transformation commitments, where the asset being planned will still be in use long after the strategy that justified it has been revised or replaced. A master-planning decision for a multi-decade development, or a major port investment programme, cannot be built around a single forecast of demand twenty years out — it has to be resilient to several very different ones.
- Which decisions are genuinely reversible, and which commit the organisation for a decade or more?
- Which assumptions, if wrong, would break the plan — not merely make it less efficient?
- Where is optionality worth paying for now, even if it looks unnecessary in the base case?
The value of a scenario is not that it predicts the future. It is that it tells you, in advance, which of your decisions were actually bets.
Ayesha Sultan
Integration is where scenarios get tested first
Nowhere does the gap between forecast and reality show up faster than in a major acquisition integration. Combining two organisations exposes, within months, every assumption that was built into the deal case — about culture, about systems, about how quickly synergies can actually be realised rather than simply modelled. A scenario-based approach to integration planning, one that has already asked what happens if realisation is slower than expected, tends to protect value far better than a plan built around the optimistic case alone.
The same logic applies to growth targets. A regional business built to deliver a step change in new business volume has to plan for the scenario in which the market is slower to respond, not only the scenario in which the target is met on schedule — otherwise the organisation over-commits resources against an assumption that was never tested.
A discipline for boards, not only strategists
Scenario planning is often treated as a technical exercise handed to a strategy team. It is more useful when it is a board-level discipline — when directors ask management not “what is your plan” but “what does your plan assume, and what happens if that assumption is wrong.” That question, asked consistently at board level, does more to stress-test a strategy than any single forecasting technique.
Over a decade defined by more disruption than the last, that discipline is not a luxury. It is simply what separates organisations that adapt from organisations that discover, too late, how many of their decisions were bets they never recognised as bets.
