AI Prompts for Scenario Planning in Operations

Scenario planning is not forecasting with three cases. A good set of scenarios describes genuinely different worlds — driven by the uncertainties that matter most and are least predictable — so that a supply chain can be tested against each and the decisions that hold up in all of them can be separated from the ones that depend on a bet.

The method here follows the classic sequence: list driving forces, sort them by impact and uncertainty, pick the two that define the scenario axes, build the scenarios, work out what each means for sourcing, capacity, inventory and logistics, then define signposts — observable events that tell you which world you are entering. AI is helpful for breadth in the early steps and discipline in the later ones.

Before you use these

Have these ready to replace the highlighted [variables]:

• The decision or plan the scenarios must inform (e.g. a 3-year network design, a supplier concentration policy)
• Your current assumptions about demand, cost, supply and regulation
• Time horizon

The prompts

• 1. Identify the critical uncertainties
• 2. Build the scenarios and their operational implications
• 3. Define signposts and a trigger-based playbook

1. Identify the critical uncertainties

Act as a scenario planning facilitator working with an operations leadership team.

Decision the scenarios must inform: [decision]
Horizon: [years]
Business context: [industry, geographies, main supply sources, cost structure]
Current planning assumptions: [list]

1. List 12–20 driving forces across demand, supply markets, technology, regulation, cost inputs, labor and geopolitics that could affect this decision.
2. For each, rate impact on the decision (high/medium/low) and predictability (predetermined trend / uncertain / highly uncertain), with one sentence of reasoning.
3. Separate predetermined elements (things that will happen in most futures and belong in every scenario) from critical uncertainties.
4. Propose two critical uncertainties as scenario axes. They must be high impact, genuinely uncertain, and largely independent of each other. Explain why each alternative pair you considered was rejected.
5. Name the four resulting scenario quadrants neutrally (no 'good' or 'bad').

Do not present a company-specific assumption as an external force. If my planning assumptions already contain an implicit bet on one of the uncertainties, point it out.

2. Build the scenarios and their operational implications

You are developing four operating scenarios from two axes.

Axes: [uncertainty A: end states] × [uncertainty B: end states]
Predetermined elements present in all scenarios: [list]
Current supply chain: [sourcing footprint, capacity locations, inventory strategy, main logistics lanes, key suppliers]

For each of the four scenarios:
1. A 150-word narrative describing how the world got there by [horizon year], internally consistent with both axis end states.
2. Implications table: demand level and mix; input costs; supplier availability and risk; lead times; capacity needs; inventory policy; logistics network; regulatory constraints.
3. The two biggest stress points for our current design in this scenario.
4. The moves that would perform well in this scenario.

Then across all four:
- Robust decisions: moves that are sensible in every scenario (do these regardless).
- Contingent decisions: moves that pay off only in some scenarios (prepare, but wait for signposts).
- Regret analysis: the current plan's worst-case scenario and what it would cost.

Keep the four scenarios genuinely distinct — if two imply the same operational response, revisit the axes and say so.

3. Define signposts and a trigger-based playbook

Act as a supply chain risk manager converting scenarios into an early-warning system.

Scenarios: [names and one-line descriptions]
Contingent decisions: [move, which scenario it belongs to, lead time to execute]
Data we already monitor: [list sources]

1. For each scenario, propose 3–5 signposts: observable indicators whose movement suggests that scenario is becoming more likely. Each must have a named source, a measurable threshold, and a lead-time advantage (how far ahead of the impact it typically moves).
2. Distinguish leading indicators from confirming indicators.
3. Build the playbook: signpost trigger → contingent action → owner → time to execute → cost of acting early if the signpost turns out to be a false alarm.
4. Set a review cadence and who reports the signpost dashboard.
5. Identify any contingent decision whose execution lead time is longer than the signposts' warning — those need either a robust hedge now or a faster execution path.

Do not propose indicators we cannot actually observe. Prefer fewer signposts with clear thresholds over a long watchlist.

Illustrative scenario matrix

For a mid-sized manufacturer deciding whether to regionalize sourcing over three years. Axes chosen by the first prompt; quadrants named neutrally.

Related prompts

• a Supply Chain Risk Register
• Supply Chain Disruption Response
• Sales & Operations Planning (S&OP)
• Capacity Planning
• Sourcing Strategy
• Operations Strategy Review

Logical next step

After this, most operations teams move on to a Supply Chain Risk Register.

All Operations & Supply Chain prompts · Search the full library