Scenario Planning

Concept of the skill

What it is: Scenario planning is a strategic-foresight method for making decisions under deep uncertainty by constructing several plausible future worlds and testing choices against them.

Mental model: Start with a decision, not a generic future. Gather forces that could shape the environment, split relatively predetermined elements from high-impact uncertainties, combine the strongest uncertainties into scenario logics, write coherent narratives, and use those narratives to identify robust actions, contingent moves, hedges, signposts, and research needs.

Why it exists: Agents often collapse uncertainty into a single forecast or fabricate probabilities. This skill keeps uncertainty explicit long enough for the strategy to become more resilient.

What it is NOT: It is not PESTEL scanning alone, expected-value math, Bayesian updating, Three Horizons portfolio allocation, SWOT/TOWS inventory, or the full strategy cascade.

Adjacent concepts: strategic foresight, horizon scanning, critical uncertainties, driver mapping, policy stress-testing, robust strategy, contingency planning, weak signals, no-regret moves, option value, early-warning signposts.

One-line analogy: Scenario planning rehearses several credible future worlds before committing the strategy.

Common misconception: Scenario planning is not optimistic/base/pessimistic forecasting. The useful output is a set of distinct, plausible, internally consistent futures that expose different strategic consequences.

Scenario Planning

Domain Context

Use scenario planning for business strategy, product strategy, market entry, nonprofit planning, public policy, transformation planning, risk review, capital allocation conversations, and strategy reviews where the future environment could change in structurally different ways. Use public, aggregate, or synthetic examples only. Do not include personal data, customer records, payment data, secrets, confidential deal details, private forecasts, or sensitive business facts in examples or evals.

Scenario planning is strongest when the decision owner faces uncertainty that cannot credibly be reduced to a single forecast or probability-weighted payoff table. It is weaker when the task is only to gather macro facts, update a known probability, compare options with reliable probabilities and payoffs, or choose a complete strategy cascade.

The output should change a decision. If the scenarios are interesting but do not affect choices, investments, policies, research priorities, monitoring, timing, or fallback plans, the work is incomplete.

Coverage

This skill teaches agents to:

1. Frame the focal decision, decision owner, time horizon, scope, stakeholders, and deadline.
2. Gather drivers from evidence, research, PESTEL scans, horizon scanning, stakeholder interviews, market signals, technology shifts, regulation, competition, economics, social change, and operational constraints.
3. Separate predetermined elements from critical uncertainties.
4. Choose scenario axes or scenario logics that are high-impact, genuinely uncertain, relevant, and not redundant.
5. Build two to four scenarios that are plausible, internally consistent, distinct, decision-relevant, and neither utopian nor dystopian by default.
6. Write scenario narratives with causal logic, stakeholder behavior, timing, constraints, and consequences.
7. Test existing or candidate strategies against every scenario.
8. Identify robust actions, contingent actions, hedges, options to preserve, bets to delay, and decisions that need more evidence.
9. Define signposts and monitoring triggers that show which scenario logic may be emerging.
10. Route adjacent tasks to the right strategy method instead of stretching scenario planning beyond its mechanism.

Philosophy of the skill

Scenario planning is useful because uncertainty is not only a data shortage. Sometimes the system itself can evolve in several plausible directions: regulation can tighten or fragment, a technology can commoditize or remain scarce, customers can change behavior, capital can become cheap or expensive, and public trust can rise or collapse. A single forecast hides those branches.

The method deliberately resists premature convergence. It asks the agent to hold multiple futures in mind long enough to see which strategies are fragile, which actions are useful across worlds, and which signals deserve monitoring. The goal is not prediction. The goal is a better present decision.

Good scenarios are disciplined stories. They are not fiction for its own sake and not generic trend prose. Each scenario should have a causal chain from drivers to outcomes, a time horizon, actor behavior, constraints, and implications for the focal decision. The names should help people remember the logic without smuggling in a preferred future.

Workflow

1. Frame the focal decision

Start by naming the decision that the scenarios must inform.

Decision owner:
Focal decision or strategic question:
Decision deadline:
Time horizon for scenarios:
Geography / market / system boundary:
Stakeholders:
Existing strategy or options to test:
Evidence available:
Evidence missing:
Constraints:

Reject scenario work that has no decision owner or decision use. If the user only asks "what could happen in the future," produce a lightweight exploration and state that it is not decision-grade scenario planning until the focal decision is named.

2. Gather drivers and evidence

Use evidence before imagination. Gather drivers from sources that fit the scope:

Separate evidence into:

Relatively predetermined elements:
High-impact uncertainties:
Low-impact uncertainties:
Known unknowns requiring research:
Weak signals:
Assumptions:

3. Select critical uncertainties

Critical uncertainties must be both important to the focal decision and genuinely uncertain within the time horizon.

When using a 2x2 matrix, avoid axes that are simply good/bad versions of the same preference. "Regulation tightens vs loosens" and "AI adoption fast vs slow" can be useful. "Success vs failure" cannot.

4. Build the scenario set

Most strategy work benefits from two to four scenarios. Four scenarios are natural for a 2x2 matrix; two or three can work when the uncertainties are not cleanly matrix-shaped. More than four usually becomes hard for decision-makers to use.

For each scenario, define:

Scenario name:
Core logic:
Critical uncertainty outcomes:
Predetermined elements present in all scenarios:
Key actors and incentives:
Causal chain from today to the scenario:
What changes for customers, users, citizens, competitors, partners, suppliers, regulators, funders, or employees:
Opportunities:
Risks:
Strategic questions:
Evidence gaps:
Signposts:

Do not title scenarios "best," "base," and "worst." Use neutral names that preserve the scenario logic without declaring a favorite.

5. Check scenario quality

Before using scenarios, test them.

If a scenario fails internal consistency, revise the causal logic or replace the axis. If all scenarios recommend the same action, either the action is robust or the scenario set is not challenging enough; name which is true.

6. Stress-test strategies

Use scenarios to evaluate existing or candidate strategies.

Stress-test template:

Strategy or option:
Scenario 1 result:
Scenario 2 result:
Scenario 3 result:
Scenario 4 result:
Robust actions:
Contingent actions:
Hedges:
Options to preserve:
Assumptions to test:
Signposts:
Decision owner and review date:

7. Define signposts and monitoring

Signposts are observable indicators that a scenario logic may be emerging. They are not vague watchwords.

Good signposts name:

• The indicator
• Source or collection method
• Direction or threshold
• Review cadence
• Owner
• Decision that changes if triggered

Examples:

8. Produce a decision-grade output

Use this answer structure for most scenario-planning tasks:

Focal decision:
Scope and horizon:
Evidence used:
Evidence missing:
Predetermined elements:
Critical uncertainties:
Scenario set:
Scenario narratives:
Strategy stress-test:
Robust actions:
Contingent actions / hedges / options:
Signposts and monitoring:
Research needs:
Downstream method handoff:

Keep the output explicit about uncertainty. Do not imply that the scenarios are exhaustive, mutually exclusive in a formal probabilistic sense, or predictive.

Boundary Routing

Verification

• The focal decision, decision owner, horizon, and scope are explicit
• Predetermined elements are separated from critical uncertainties
• Scenario axes or logics are high-impact, uncertain, relevant, and not redundant
• Scenarios are plausible, distinct, internally consistent, and decision-relevant
• Scenario names do not encode a preferred future or best/base/worst pattern
• Narratives include causal logic, actors, timing, and consequences
• Strategic implications include robust actions, contingent actions, hedges, options, or stops
• Signposts have observable indicators, thresholds or directions, owners, cadence, and linked decisions
• Facts, assumptions, weak signals, and invented examples are clearly separated
• Adjacent methods are routed correctly

Do NOT Use When