SuperAPI AI Directory

scenario-planning-skill

Agents & models

View repository

Updated 10-15 21:41

About this skill

Scenario Planning thinking tool

It is not about predicting the "most likely" future, but about constructing multiple possible futures, allowing decision-makers to experience different worlds and thereby change their mental models.


Activation Conditions and Trigger Words

Directly use trigger words

  • "Use scenario planning to analyze..."
  • "Help me construct several future scenarios"
  • "Cope with high uncertainty"
  • "Strategic foresight" "scenario planning"

Diagnostic recommendation trigger words

  • "The future is highly uncertain, and I don't know what to do"
  • "Cannot make only one forecast"
  • "Need to consider multiple possible futures"
  • "Want to respond to different situations in advance"

Overview of the Method Framework

Scenario planning is a strategic foresight method that, by constructing 3-4 structurally different future narrative scenarios, helps decision-makers identify key driving forces, challenge existing mental models, and formulate robust strategies under deep uncertainty. Its core value lies not in "guessing correctly" the future, but in changing decision-makers' cognitive framework for the world.


Core Principles

Principle 1: Mental Model Reframing

One-sentence definition: The purpose of scenarios is not to predict the future, but to change decision-makers' mental models.

Cross-domain evidence 1: [Corporate Strategy] Pierre Wack's practice at Royal Dutch Shell showed that the core goal of scenario planning has never been to "guess correctly" the future, but to enable Shell's management to "see" structural changes they previously could not see. In his 1985 HBR article "Scenarios: Uncharted Waters Ahead," Wack explicitly wrote that the value of scenarios lies in changing managers' "micros"—their internal assumptions and cognitive frameworks about the world. Through scenario work between 1971 and 1973, Shell's management recognized the structural change that Middle East oil supply could be interrupted, enabling Shell to leap from the weakest company among the "Seven Sisters" during the 1973 oil crisis to an industry leader. (Source:HBR, 1985)

Cross-domain evidence 2: [Public Policy] Since the 1980s, the Singapore government first introduced scenario planning in the Ministry of Defence, later expanding it to the entire government system. Singapore's Centre for Strategic Futures (CSF) uses scenario planning to change policymakers' cognitive framework regarding national security, and its SP+ (Scenario Planning Plus) methodology explicitly takes "challenging assumptions" as a core goal. (Source:OECD OPSI)

Application method: Construct 3-4 structurally different scenario narratives, forcing decision-makers to experience "future worlds" different from their existing cognition, thereby loosening rigid thinking frameworks.

Limitations: The effect is highly dependent on participants' openness and reflective capacity; when the power distance in organizational culture is too large, subordinates may not dare to truly challenge superiors' assumptions, and scenarios become superficial.

Principle 2: Identification of Predetermined Elements

One-sentence definition: Distinguish "certain forces" that have already occurred but whose consequences have not yet fully unfolded from truly uncertain factors.

Cross-domain evidence 1: [Energy Industry] Pierre Wack defined "predetermined elements" as "events that have already occurred but whose consequences have not yet fully unfolded." In Shell's scenario practice, Wack identified the wave of nationalism in Middle Eastern countries and the trend of growing oil demand in the 1970s as "predetermined elements"—these forces had already taken shape and would continue to exert influence regardless of short-term political events. (Source:ResearchGate)

Cross-domain evidence 2: [Climate Policy] The IPCC's Shared Socioeconomic Pathways (SSPs) framework treats population growth trends, the carbon emission lock-in effect of existing infrastructure, and similar factors as "predetermined elements," while treating policy choice pathways, the pace of technological breakthroughs, and similar factors as genuine dimensions of uncertainty. (Source:IPCC Emissions Scenarios)

Application method: Before constructing scenarios, first systematically sort out the "certain" forces (population trends, already invested capital, constraints of physical laws, etc.), use them as the "base" shared by all scenarios, and then construct differentiated scenarios around 2-3 key uncertainties.

Limitations: The judgment of "predetermined" itself may be wrong—some seemingly certain major trends may reverse in black swan events (such as the collapse of the Soviet Union overturning geopolitical "certainties").

Principle 3: Uncertainty Axes Matrix

One-sentence definition: Select the 2 driving forces with the highest impact and highest uncertainty as the coordinate axes to form a 2x2 scenario matrix.

Cross-domain evidence 1: [Business Strategy] In the scenario-building method promoted by Peter Schwartz at the Global Business Network (GBN), the classic step is: from all driving forces, select the 2 with the greatest impact and the greatest uncertainty as the X-axis and Y-axis, forming 4 quadrant scenarios. (Source:Schwartz, The Art of the Long View, 1991)

Cross-domain evidence 2: [Urban Planning] In the field of urban planning, the scenario matrix method is widely used in spatial dynamic planning. Research published in the SAGE journal combines scenario planning with spatial dynamic planning support systems, using "economic growth rate" and "intensity of environmental constraints" as the two axes to predict and simulate different scenarios of urban growth. (Source:SAGE Journals)

Application method: The steps are: (1) list all driving forces; (2) score them along the two dimensions of "degree of impact" and "degree of uncertainty"; (3) select the 2 forces in the upper right corner as the axes; (4) write a narrative scenario for each of the 4 quadrants.

Limitations: A strict 2x2 matrix may oversimplify reality—when there are more than 2 key uncertainties, the matrix will omit important dimensions; while expanding it to 2x2x2 or 3x3 will cause the number of scenarios to explode, making it difficult for decision-makers to digest.

Principle 4: Narrative-Driven Plausibility Over Probability

One-sentence definition: Scenarios pursue internal consistency and logical plausibility, rather than predicting the single most probable future.

Cross-domain evidence 1: [National Defense and Military] When Herman Kahn developed "scenario technique" at the RAND Corporation in the 1950s, its core innovation was to replace single predictions with multiple "thought experiment"-style stories. When analyzing the consequences of nuclear war, Kahn constructed multiple "unimaginable" but logically self-consistent scenarios—not to predict whether nuclear war would occur, but to enable decision-makers to still make rational judgments when facing "the unimaginable." (Source:RAND Corporation)

Cross-domain evidence 2: [Political Transition] In the 1991-1992 South African Mont Fleur scenario project, 22 South African leaders from different political camps constructed 4 narrative scenarios—"Ostrich" (refusal to change), "Lame Duck" (inability to transition), "Icarus" (unrealistic radical reform leading to collapse), "Flamingo Takes Off" (inclusive sustainable growth). The core value of these scenarios lies not in which one is "most likely to happen," but in helping participants understand the internal logic and causal relationships of each path. (Source:Reos Partners)

Application approach: Write each scenario as a complete narrative story (rather than a data table), including causal chains, key event nodes, and logical consistency checks, so that readers can "immerse themselves" in experiencing different futures.

Limitations: The judgment of "plausibility" is itself subjective; an overly compelling story may make people mistakenly believe it "should" happen, thereby reinforcing bias.

Principle 5: Weak Signal Detection & Strategic Radar

One-sentence definition: Continuously scan the environment for weak, unformed signals of change as early warning for scenario updates and strategic adjustments.

Cross-domain evidence 1: [Energy industry] Research published on ScienceDirect specifically explored the application of "weak signal" tools in scenario planning in the energy sector. Weak signals are defined as "early signs of emerging change"—they have not yet formed a clear trend, but may indicate acceleration or a turning point in some direction within the scenario matrix. (Source:ScienceDirect - Heliyon)

Cross-domain evidence 2: [National security] The Singapore government's RAHS (Risk Assessment and Horizon Scanning) project is a typical case of a national-level weak signal monitoring system. RAHS systematically scans early signals across global political, economic, social, technological, and other dimensions, providing input for national strategic planning. (Source:Singapore CSF)

Application approach: Set "indicators" (lead indicators) and "trigger conditions" for each scenario, establish a continuous monitoring mechanism, and regularly assess which scenario is becoming more "real."

Limitations: The false positive rate of weak signals is extremely high; organizations often only "see" those ignored signals after the fact (hindsight bias), but beforehand, the massive amount of noise makes true signals difficult to identify.

Principle 6: Diverse Participation & Adversarial Thinking

One-sentence definition: Introduce participants with different backgrounds, positions, and cognitive frameworks, and break groupthink through constructive confrontation.

Cross-domain evidence 1: [Political conflict mediation] In the Mont Fleur scenario project, Adam Kahane deliberately invited the most opposing political forces in South African society—ANC activists, National Party members, union leaders, business magnates—to jointly construct scenarios. This design of "letting hostile parties share one thinking space" made the scenarios no longer the vision of one side, but a narrative whose "possibility" all parties could acknowledge. (Source:Adam Kahane, Transformative Scenario Planning, 2012)

Cross-domain evidence 2: [Financial regulation] The Federal Reserve's CCAR (Comprehensive Capital Analysis and Review) stress testing framework adopts an "adversarial" scenario design—stress scenarios are designed by regulatory agencies rather than the banks themselves, precisely to avoid the problem of overly optimistic scenarios caused by groupthink within banks. (Source:Federal Reserve Stress Tests)

Application approach: The scenario team should include internal and external personnel, optimists and pessimists, different functional areas and different levels, and deliberately introduce a "Red Team" to challenge.

Limitations: Diverse participants increase coordination costs and conflict risks; in politically sensitive environments, participants may represent positions rather than genuine thinking, causing the scenario process to be hijacked by political maneuvering.


Operational Protocol (Agentic Protocol)

Step 1: Problem Classification — Determine the Applicability of Scenario Planning

First assess the characteristics of the problem to determine whether scenario planning is suitable:

Applicable scenarios:

  • Facing deep uncertainty (the strategic environment of the next 3-10 years)
  • The outcomes of key driving forces are highly uncertain and have major impacts
  • Multiple structurally different possible futures exist (rather than up-and-down fluctuations of a single trend)
  • The organization has the time and resources for forward-looking thinking

Inapplicable scenarios:

  • Short-term operational issues (time span < 1 year)
  • Highly certain routine decisions (such as conventional budget planning)
  • Regulatory/compliance scenarios that require precise probabilistic forecasts
  • The organization lacks a reflective culture or openness

Misuse detection: If the user asks to "predict the most likely future" or provides an "optimistic/baseline/pessimistic" three-scenario framework, warn that this is a misuse of scenario planning.

Step 2: Scenario Planning-Style Analysis — Systematically Construct Future Scenarios

2.1 Identify Predetermined Elements

Systematically sort out the forces that have already occurred but whose consequences have not yet fully unfolded:

  • Demographic trends (aging, urbanization, etc.)
  • Technological trajectories (R&D already invested, lock-in of existing infrastructure)
  • Policy/regulatory direction (policies already legislated but not fully implemented)
  • Physical constraints (resource limits, environmental carrying capacity)

Checkpoint: Are these elements truly "predetermined"? Is there any possibility of reversal?

2.2 Identify Key Uncertainty Driving Forces

List all important factors that may affect the future, and evaluate each factor:

  • Degree of impact: If this factor develops in different directions, how great is the impact on the problem?
  • Degree of uncertainty: Is the future outcome of this factor highly unpredictable?

Select forces with "high impact + high uncertainty" as candidate axes.

2.3 Construct a Two-Axis Uncertainty Matrix

Select the 2 most important forces from the candidates as the X-axis and Y-axis to form a 2x2 matrix:

  • Name each quadrant (metaphorical names are recommended, such as "Ostrich," "Lame Duck," "Icarus," "Flamingo")
  • Check whether the 4 quadrants truly represent structurally different worlds (rather than variations in magnitude of the same story)

Misuse detection: If the 4 quadrants are merely different values of the same trend (such as GDP growth of 3%, 2%, 1%, -1%), this violates the basic principles of scenario planning.

2.4 Write Scenario Narratives

Write a complete narrative story for each quadrant (500-1000 words recommended):

  • Set a specific point in time (usually a year within the next 3-10 years)
  • Describe what "daily life" in that world is like
  • Explain the causal chain: why would this world become like this?
  • Include specific details and contextual descriptions

Quality standards:

  • Each scenario is internally logically consistent
  • There are obvious structural differences among different scenarios
  • Vivid narrative that can make readers feel "immersed in the scene"

2.5 Introduce diverse perspectives challenge

Have people from different backgrounds examine the scenarios:

  • Do they consider these scenarios "reasonable"?
  • Are there any key uncertainties that have been overlooked?
  • Are there any scenarios that are "unimaginable" but worth exploring?

Step 3: Scenario planning-style output — robust strategy design

3.1 Strategic implications analysis

Answer for each scenario:

  • In this world, what strategy would succeed?
  • What strategy would fail?
  • Do our core capabilities have value in this world?

3.2 Design a robust strategy (Robust Strategy)

Identify strategic options that are viable in all scenarios:

  • Common options: Which actions are wise in all scenarios?
  • Options-style investments: Which small-scale investments can preserve for us the right to expand in some future scenario?
  • Hedging strategies: How can we design a portfolio that has both basic resilience and the ability to address specific risks?

3.3 Define a signal monitoring mechanism

Establish an early warning system for scenario updates:

  • Indicators: What are the key "signals" for each scenario? (e.g., policy changes, technological breakthroughs, social trends)
  • Trigger conditions: What events should make us reassess scenario weights?
  • Monitoring frequency: How often should the "plausibility" of scenarios be reviewed?

3.4 Output a structured report

Include the following sections:

  1. Executive summary: The core conclusions and strategic recommendations of scenario planning
  2. Scenario matrix: 2x2 uncertainty matrix visualization
  3. Scenario narratives: 3-4 complete scenario stories
  4. Strategic implications: The specific impact of each scenario on the organization
  5. Robust strategy: Action plans that are viable in all scenarios
  6. Signal monitoring: Early warning indicators and review mechanisms

Applicability/non-applicability assessment

Scenario Applicability Description
Long-term strategic planning (3-10 years) High A classic applicable scenario, such as Shell's energy industry scenarios
Periods of political/social transition High Such as the Mont Fleur scenarios for South Africa's transition
Industries with high regulatory/policy uncertainty High Such as energy, healthcare, and financial industries
Short-term operational decisions Low Uncertainty is low, and conventional analytical tools can be used
Compliance scenarios requiring precise probabilities Low Scenario planning does not provide probabilistic forecasts
Early-stage startups Medium Valuable but resource-intensive; a simplified version is needed

Misuse detector

Misuse signal Detection logic Warning message Recommended actions
The "three futures" trap Scenarios are named "optimistic/base/pessimistic," but in substance they are merely variations in magnitude along the same trend "This is not scenario planning, but sensitivity analysis—and a very poor sensitivity analysis at that" Use a 2x2 uncertainty matrix to force the construction of structurally different scenarios
Treating scenario planning as a forecasting tool The team discusses "which scenario is most likely to occur" or tries to assign probabilities "The power of scenario planning lies precisely in its acknowledgment that we cannot predict. Once you start choosing the 'most likely' scenario, you have fallen back into single-point forecasting thinking" Ban the word "most likely" in scenario discussions and design robust strategies
Too many or too few scenarios More than 7 scenarios were developed, or only 2 scenarios "7 scenarios means no one can remember any of them. 2 scenarios means you are just making a binary 'good versus bad' judgment. 3-4 is the sweet spot" Strictly limit to 3-4 scenarios, and use a nested structure to handle more dimensions
Confusing trends with uncertainties Treating a predictable megatrend (such as population aging) as an "uncertainty axis" in the scenario matrix "Global population aging is not an uncertainty—it is already happening. What you need to ask is: against the certain backdrop of aging, which factors' outcomes are truly uncertain?" First make a list of "predetermined elements" and remove trends from the pool of uncertainty candidates
Scenarios disconnected from strategy After the scenario report is completed, it is shelved and strategy proceeds as before "A scenario report that no one reads is not scenario planning—it is an expensive creative writing exercise. Scenarios must be embedded in the decision-making process, otherwise it is a waste" Involve decision-makers throughout the scenario-building process and embed scenario planning into the annual strategic planning cycle
Politicization of scenarios Participants use the scenario-building process as a tool to advance their own interests or agendas "When the scenario results happen to confirm exactly what the CEO most wants to hear, you should be wary—this may mean the process has been hijacked by politics" Bring in an independent external facilitator and use a "red team" role to challenge assumptions

Honest boundaries

  1. Unable to handle true black swan events: Scenario planning is based on "extrapolation and combination of existing signals"—it can reveal known unknowns, but by its nature it cannot handle unknown unknowns. Many specific mechanisms in the 2008 financial crisis (CDO squared, the chain collapse of subprime mortgages) exceeded the imaginative boundaries of mainstream scenario planning at the time.

  2. Lack of standardized methodology and effect evaluation systems: A review published in the journal Futures in 2023 pointed out that the field of scenario planning suffers from conceptual confusion, methodological confusion, and a severe lack of evidence on effects. At present, there is almost no rigorous empirical research proving that scenario planning actually improves organizational performance. A large number of "success stories" (such as Shell) are attributed after the fact—we cannot prove whether Shell's success was due to scenario planning or other factors.

  3. High dependence on organizational culture and leadership: Research by MIT Sloan Management Review points out that scenario planning often fails in organizations with a "strong operational culture"—such organizations value execution efficiency over exploratory thinking. After leaving Shell, Pierre Wack himself also admitted that the biggest obstacle to scenario planning is not a methodological problem, but that the task of "changing managers' mental models" is far more difficult than imagined.

  4. Resource consumption and diseconomies of scale: Effective scenario planning requires a large amount of time (usually a 3-6 month cycle), a highly qualified cross-functional team, an external expert network, and continuous signal-monitoring infrastructure. For small and medium-sized enterprises, a complete scenario planning process may be uneconomical—the input-output ratio is insufficient to support it.

  5. "False precision" risk and quantification trap: When organizations try to assign precise probabilities, timelines, or quantified impacts to scenarios, they easily produce "false precision"—a sense of precision that cannot be reasonably defended under deep uncertainty. Academic research by Hodgkinson & Healey (2008) points out that overly complex and excessively quantified scenarios may produce a dysfunction of "creativity superimposed on fantasy"—the seemingly rigorous numbers conceal the fragility of the underlying assumptions.


Research Sources

The design of this Skill is based on the following sources (partial):

  1. Pierre Wack, "Scenarios: Uncharted Waters Ahead", Harvard Business Review, 1985 — Primary source, core required reading
  2. Pierre Wack, "Scenarios: Shooting the Rapids", Harvard Business Review, 1985 — Primary source, core required reading
  3. Peter Schwartz, The Art of the Long View, Doubleday, 1991 — Primary source, core required reading
  4. Paul Schoemaker, "Scenario Planning: A Tool for Strategic Thinking", MIT Sloan Management Review, 1995 — Primary source, core required reading
  5. Paul Schoemaker, "Twenty Common Pitfalls in Scenario Planning", in Learning from the Future, Wiley, 1998 — Primary source
  6. Adam Kahane, Transformative Scenario Planning, Berrett-Koehler, 2012 — Primary source
  7. Herman Kahn, On Thermonuclear War, Princeton University Press, 1960 — Primary source, classic
  8. Herman Kahn, Thinking About the Unthinkable, Horizon Press, 1962 — Primary source, classic
  9. Royal Dutch Shell, "40 Years of Shell Scenarios", Shell official publication, 2012 — Primary source
  10. Reos Partners, "Mont Fleur Scenarios" project document — Primary source
  11. Federal Reserve, "Policy Statement on Scenario Design Framework for Stress Testing", 2013 — Primary source
  12. IEA, World Energy Outlook Annual series — Primary source
  13. IPCC, Shared Socioeconomic Pathways (SSPs) — Primary source

Proportion of primary sources: About 77% (10 primary sources, 3 secondary sources)


This Skill was automatically generated by the Forge Skill forging engine. GitHub: https://github.com/peterfei/forge-skill Based on structured distillation of methodological literature and triple-validation extraction.