Build a small set of plausible futures and use them to expose assumptions, test choices and prepare signposts.
In one minute
Scenario Planning does not predict the future. It creates distinct, internally coherent views of how important uncertainties could combine. The team then asks:
- Which strategy works across several futures?
- Which commitment only works in one?
- What option should we preserve?
- What early signal would tell us that one scenario is becoming more relevant?
The output is a set of strategic insights, robust actions, contingent moves and indicators—not a collection of imaginative stories.
Best for: long-horizon, high-impact decisions shaped by external uncertainty.
Avoid when: uncertainty is low, the decision is reversible or the team only needs an operational forecast.
The problem it addresses
Plans often inherit one “official” forecast. This can hide fragile assumptions and make the organisation efficient for a future that never arrives. Scenario Planning expands the range of considered conditions without pretending that all outcomes can be assigned reliable probabilities.
The intended outcome is better preparedness and more adaptive strategic decisions.
When to use it
- before a major, long-lived or hard-to-reverse investment;
- when two or more external uncertainties could reshape the market;
- when leadership views about the future differ;
- when a conventional forecast gives a false sense of precision;
- when regulation, technology, geopolitics or social behaviour may interact;
- to stress-test an existing strategy.
When not to use it
Do not use Scenario Planning:
- to avoid making a decision;
- for short-term capacity scheduling that needs a forecast;
- when scenarios are simply “good, average and bad” versions of one variable;
- when participants refuse to consider futures they dislike;
- as a substitute for risk controls around known hazards;
- when there is no owner for signpost monitoring.
Inputs required
- a focal decision and relevant horizon;
- known trends and predetermined elements;
- a broad set of external driving forces;
- evidence on uncertainties and causal relationships;
- diverse participants, including outside perspectives;
- existing strategic options and constraints.
Step-by-step process
1. Frame the focal question
Write one decision-oriented question with a horizon: “How should Northstar build its clinic-market position over the next five years?”
2. Map driving forces
Use PESTLE, industry analysis, customer change and technology signals. Separate relatively predictable trends from genuinely uncertain drivers.
3. Rank uncertainty and impact
Prioritise drivers that are both highly uncertain and capable of changing the focal decision. Avoid selecting uncertainties that are merely interesting.
4. Create distinct scenario logics
A two-axis matrix can be useful for learning, but it is not mandatory. Choose combinations that produce meaningfully different strategic conditions. The axes should be independent enough to create four coherent worlds.
5. Develop each world
Give every scenario:
- a neutral, memorable name;
- a short causal narrative;
- customer and competitor behaviour;
- economic and operating implications;
- what would have to be true;
- early indicators.
Make each scenario plausible and challenging. Do not create one preferred future and three caricatures.
6. Stress-test current strategy
For every scenario, record which assumptions break, what performs well, where exposure rises and which capability becomes valuable.
7. Choose strategic responses
Separate:
- robust actions that make sense across scenarios;
- options that preserve future choice;
- contingent actions triggered by signposts;
- no-regret learning that reduces uncertainty.
8. Monitor and refresh
Assign indicator owners, thresholds and review dates. Scenarios are decision infrastructure, not a workshop artefact.
Visual model
Text alternative: a focal decision leads to driving forces and critical uncertainties. These form several scenarios used to stress-test strategy and define robust actions, options, contingent moves and signposts.
Interactive example
Scenario
Northstar is planning for two uncertain forces:
- adoption of AI agents for booking: slow or fast;
- health-data regulation: fragmented or harmonised.
Your move
Name four scenario worlds and identify one robust action.
Worked answer
| Fragmented regulation | Harmonised regulation | |
|---|---|---|
| Slow AI adoption | Local Rulebooks | Standard Trust |
| Fast AI adoption | Agent Patchwork | Agent Infrastructure |
A robust action could be build auditable consent and integration boundaries. It supports compliance in both regulatory worlds and makes agent integrations safer under both adoption paths.
A contingent move might be a deep platform partnership triggered only if agent-led bookings exceed a defined share in target clinics.
Facilitation notes
- Include people who challenge the organisation’s dominant assumptions.
- Use evidence to shape plausibility, not to collapse the exercise into one forecast.
- Write scenario names after the causal logic is sound.
- Rotate groups so the “owner” of a strategy does not grade it alone.
- Keep the decision visible throughout the workshop.
Expected output
- a focal question and horizon;
- prioritised drivers and critical uncertainties;
- 3–4 distinct, plausible and coherent scenarios;
- implications for customers, competitors and operations;
- stress-test results;
- robust, optional and contingent actions;
- signposts, thresholds, owners and review dates.
Common mistakes
- Treating scenarios as forecasts or predictions.
- Creating best/base/worst cases on one variable.
- Choosing dependent axes that produce repetitive worlds.
- Writing stories without strategic implications.
- Making the preferred scenario more plausible than the others.
- Failing to define signposts.
- Never revisiting the scenarios.
Quality checklist
- The focal question concerns a real decision.
- Scenarios are plausible, distinct and internally coherent.
- Critical uncertainties have high decision impact.
- Predetermined trends and uncertainties are separated.
- Every scenario challenges at least one current assumption.
- Actions are classified as robust, optional or contingent.
- Signposts have thresholds and owners.
Template
| Scenario | Causal logic | Customer behaviour | Industry structure | Key risk | Key opportunity | Strategy implication | Signposts |
|---|---|---|---|---|---|---|---|
| Action | Robust across | Fails in | Type | Trigger | Owner | Review date |
|---|---|---|---|---|---|---|
| Robust / option / contingent |
Knowledge check
Which statement best describes a scenario?
A. The most likely forecast with a confidence interval.
B. A target future that leadership wants to create.
C. A plausible, coherent future used to test assumptions and choices.
D. A list of unrelated risks.
Answer: C. Scenarios are possible worlds for decision testing; they are not predictions or aspirations.
Related tools
- Follows: PESTLE Analysis, SWOT Analysis
- Supports: Ansoff Matrix, BCG portfolio decisions
- Often combined with: Decision Matrix
- Not to be confused with: forecasting, contingency plans or a risk register
References
- Wack, P. “Scenarios: Uncharted Waters Ahead.” Harvard Business Review, September–October 1985, pp. 73–89; and “Scenarios: Shooting the Rapids,” November–December 1985, pp. 139–150. Primary practitioner accounts.
- Shell. “What are Shell Scenarios?” Shell Scenarios explainer (opens in a new tab). Authoritative organisational guidance on scenarios as multiple possible futures rather than predictions.
- Shell. 40 Years of Shell Scenarios. 2013. Shell publication (opens in a new tab). Organisational history and cases.
- van der Heijden, K. Scenarios: The Art of Strategic Conversation. 2nd ed., Wiley, 2005. ISBN 978-0-470-02368-6. Authoritative secondary guide.
Sources reviewed 27 July 2026.