Page 194 · Module 08, Decide with Confidence · this screen continues that page

All 108 frameworks
8.5AdvancedModule 08 · Decide with Confidence

Scenario Planning

Plan for the futures that haven't happened yet, including the ones you're not expecting

The prompt

Copy & paste ready
8.5Scenario Planning
Act as a scenario planning strategist. My business : [DESCRIBE YOUR COMPANY AND CORE STRATEGY] Planning horizon : [1 YEAR / 3 YEARS / 5 YEARS] Key uncertainties : [WHAT 2–3 EXTERNAL FACTORS COULD MOST CHANGE YOUR BUSINESS ENVIRONMENT] Build 3 distinct scenarios. For each scenario: NAME : A memorable, descriptive title DESCRIPTION : What this future looks like in 2–3 sentences KEY DRIVERS : What causes this scenario to unfold IMPACT : How does this affect my business specifically? STRATEGY : What should I do differently in this scenario? EARLY SIGNAL : What would I see in the next 90 days that tells me this scenario is emerging? After the three scenarios: Which elements of my current strategy work across all three? Which are scenario-specific bets? Scenario planning matrix based on market growth and regulation. Slow Fast Scenario 1 Scenario 2 Scenario 3 Scenario 4 Minimal government Heavy government High market Limited market oversight control competition opportunities
LabelsReplace theseSwap the role below

LabelsReplace theseSwap the role below

Pro tip, from the book

The real value in scenario planning isn't the scenarios, it's the early warning signals. Once you know what each future looks like in its early stages, you know what to watch for. Build a simple 3–5 signal dashboard and review it quarterly. Founders who see change coming are the ones who defined what it would look like before it arrived.

Who should run this prompt

Module role profile

Who should stress-test your most important decisions? Most bad decisions were not obviously bad at the time — they had a good first-order case and a hidden second-order cost. The roles on this page are designed to surface what you cannot see from inside your own reasoning. Some will challenge your logic. Some will challenge your assumptions. One will challenge whether you are even asking the right question.

Choose any role to drop it into the prompt above. Only the highlighted opening clause changes — the rest of the prompt stays exactly as printed.

Internal rolesThink from inside the organisation
Outside perspectivesChallenge your blind spots

◆◆◆◆◆ → ◆ seniority, board level down to specialist outside the organisation

How to make any role sharper

  1. Add years of experience: "...with 15 years in enterprise SaaS" produces different depth than just the title.
  2. Add what they care most about: "You care most about [X]" shapes every word of the output.
  3. Add their communication style: "Be direct. Flag risks first. No jargon." changes the tone entirely.
See also: 1.3 Role Prompting - The Expert Chair

Use this when

The problem it solves

You plan for one future: the one you expect. When the market shifts, a competitor moves, or an external event disrupts your assumptions, you are caught without a contingency. You are not naive, you just haven't built the habit of planning for multiple futures.

How the framework works

From the printed page

Scenario Planning was pioneered by Herman Kahn at the RAND Corporation and developed into a strategic tool by the Shell Oil planning team in the 1970s, most famously used to prepare for the 1973 oil crisis before it happened. The method builds three to four internally consistent, plausible futures based on the key uncertainties in your environment. You then stress-test your strategy against each scenario. The goal is not to predict which future will happen, it is to build a strategy that is robust across multiple futures and to identify the early signals that tell you which future is emerging.

The method, in four moves

Do these in order
1

Identify your two most critical and most uncertain variables, these become the axes of your scenario matrix.

2

Build scenarios that are plausible, distinct, and internally consistent not best/worst/base.

3

Name each scenario memorably, it makes them easier to reference in team conversations.

4

Define the early warning signals for each scenario before you need them. A named scenario is worth nothing without a defined trigger. If "Downturn" and "Boom" don't come with the specific early signals that tell you which one is arriving, you've built a story exercise, not a strategy tool.

Where the framework comes from

Herman Kahn, RAND Corporation · Shell Oil planning team, 1970s

When this page changes, your copy of the book does not have to.

The book prints the framework. This page keeps it — and keeps the prompt current, because prompting technique moves faster than print does. When it moves, this page is rewritten and the code in your copy keeps pointing at it. No second edition, no replacement purchase, no account.

If something here looks wrong — a prompt that does not match its framework, a figure that reads oddly — tell Raphy. That correction reaches every printed copy at once.

Framework8.5 of 108
Printed onPages 193194
Prompt extracted18 Sept 2026
Costs to readNothing, no account

Copying is free. An account keeps them.

Nothing on this page is behind a login and nothing ever will be. Save any prompt to your own list, pick up on another device, and send a colleague a link with your name on it. No card, no trial, no paywall on the prompts themselves.

See how it works
Save this framework to your own list
Pick up where you left off on another device
Send a colleague a link with your name on it