Why Planning for One Future Is Planning to Fail
Traditional risk identification asks: What could go wrong with our plan? Scenario planning asks a fundamentally different question: What if the world in which our plan exists changes beyond recognition?
The distinction matters. Conventional risk tools — checklists, brainstorming, cause-and-effect analysis — are powerful for identifying risks within a broadly stable operating environment. But when the environment itself is uncertain — when trade agreements shift, technologies emerge or collapse, climate patterns change, or political landscapes transform — those tools cannot capture the full range of threats and opportunities facing a project.
Scenario planning was developed and famously applied by the large energy organisation in the early 1970s. While competitors built their strategies around a single forecast of stable oil prices, a large energy organisation constructed multiple scenarios of how the future might unfold — including scenarios involving dramatic oil price shocks. When a major oil-market disruption quadrupled oil prices in 1973, a large energy organisation was the only major oil company positioned to respond effectively, and it rose from one of the weakest to one of the strongest companies in the industry within a decade.
For project managers — particularly those operating in defence, heavy engineering, and long-duration programmes — scenario planning is not a luxury. It is the only rigorous method for stress-testing plans against the kind of environmental uncertainty that single-point risk assessments cannot capture.
What Is Scenario Planning?
Scenario planning is not forecasting. Forecasting attempts to predict the most likely future. Scenario planning constructs multiple plausible futures — typically an optimistic, a pessimistic, and one or two intermediate scenarios — and then tests current plans and strategies against each one.
How Scenarios Differ from Risk Events
A risk event is a specific, identifiable occurrence (e.g., "the primary supplier fails to deliver materials on schedule"). A scenario is a coherent narrative describing a plausible future state of the world in which multiple interconnected factors have changed simultaneously. Scenarios capture systemic, correlated risks that individual risk events cannot.
| Dimension | Risk Event | Scenario |
|---|---|---|
| Scope | Specific, isolated occurrence | Broad, interconnected set of conditions |
| Time Horizon | Near to medium term | Medium to long term (5–30 years) |
| Correlation | Independent or weakly linked | Multiple factors changing together |
| Purpose | Identify and mitigate specific threats | Stress-test strategy and plans against systemic uncertainty |
| Output | Risk register entry with P×I score | Narrative-driven "alternative world" with cascading implications |
How to Apply Scenario Planning: A Step-by-Step Framework
Step 1: Define the Strategic Question
What is the fundamental question your project needs to answer? For a 10-year defence infrastructure programme, this might be: "What conditions will determine whether this project delivers value to the Commonwealth over the next two decades?"
Step 2: Identify Key Drivers of Change
Through workshops, expert interviews, and environmental scanning (see Article 2 in this series), identify the major forces that will shape the project's operating environment. Common drivers include:
- Government policy and regulatory direction
- Climate and environmental conditions
- Technology adoption and disruption
- Economic cycles and trade relationships
- Social and demographic trends
- Geopolitical stability and international relations
Step 3: Determine Critical Uncertainties
Not all drivers are equally uncertain. Some trends are relatively predictable (e.g., population ageing); others are deeply uncertain (e.g., future government policy on defence spending). The two or three most uncertain and most impactful drivers become the axes around which scenarios are constructed.
Step 4: Construct Plausible Scenarios
Typically, three to four scenarios are developed, each representing a distinct combination of how the critical uncertainties might resolve. Scenarios must be:
- Plausible — grounded in reality, not science fiction
- Coherent — internally consistent; the elements of the story fit together logically
- Challenging — they should stretch thinking beyond comfortable assumptions
- Distinct — each scenario should describe a meaningfully different future
Step 5: Assess Impacts and Identify Vulnerabilities
For each scenario, the project team asks: If this future materialised, what changes would we need to make to our plan? What aspects of our current approach would fail? What opportunities would emerge?
Step 6: Develop Robust Strategies
The goal is not to predict which scenario will occur. It is to identify strategies that perform reasonably well across all scenarios — and to build early-warning indicators that signal which scenario appears to be emerging.
Scenario Planning and the Risk Identification Toolkit
Scenario planning does not replace conventional risk identification techniques — it complements them. Brainstorming, checklists, and cause-and-effect diagrams identify risks within the assumed operating environment. Scenario planning identifies risks that emerge when that operating environment itself changes.
The relationship between tools can be understood as operating at different levels of uncertainty:
| Level of Uncertainty | Appropriate Tools |
|---|---|
| Known knowns — risks we have identified and understand | Checklists, document review, lessons learned |
| Known unknowns — risks we know exist but whose details are uncertain | Brainstorming, SWOT, cause-and-effect, expert judgement |
| Unknown unknowns — risks we have not yet identified or imagined | Scenario planning, assumption testing, red-teaming |
The Pitfalls: Where Scenario Planning Goes Wrong
1. Treating scenarios as predictions. Scenarios are not forecasts. The moment a team begins debating which scenario is "most likely," the process has been derailed. The value lies in planning for all of them. 2. Constructing scenarios that are too similar. If all four scenarios describe variations of the status quo, they will not stretch thinking or reveal hidden vulnerabilities. At least one scenario should be uncomfortable. 3. Stopping at the narrative. A beautifully written scenario that does not get translated into specific risk register entries, response plans, and monitoring triggers adds no operational value to the project. 4. Excluding diverse perspectives. The regional irrigation district project involved a broad stakeholder group from farming, processing, environment, business, welfare, and government. Scenario quality depends directly on the diversity of perspectives informing the process. 5. Conducting the exercise only once. Scenarios should be revisited and refreshed as new information emerges, particularly at major phase gates or when trigger indicators suggest the environment is shifting.
Key Takeaways
- Scenario planning addresses a category of risk that conventional tools cannot: systemic, correlated uncertainty about the future operating environment.
- Scenarios are not predictions — they are plausible, coherent narratives of alternative futures used to stress-test plans and identify vulnerabilities.
- The process follows a structured sequence: define the strategic question, identify key drivers, determine critical uncertainties, construct scenarios, assess impacts, and develop robust strategies.
- The the regional scenario initiative case study demonstrates best practice: diverse stakeholder engagement, multiple distinct scenarios, structured impact assessment, and cross-scenario synthesis to identify robust actions.
- Scenario planning complements — but does not replace — conventional risk identification tools. Use it to address the "unknown unknowns" that brainstorming and checklists cannot reach.
- The ultimate output of scenario planning must be actionable risk register entries with owners, response plans, and early-warning indicators — not merely a set of interesting stories.