How to use a scenario plan (and when to take it off the shelf)

A scenario plan is not a prediction and it's not a report. It's a decision instrument — and like any instrument, it has to be read correctly to be useful. Here's how.

How to use a scenario plan (and when to take it off the shelf)

The analysis is done. The four futures are on the page. The strategies are listed. And there's a quiet, familiar moment that follows: now what, exactly, do I do with this?

It's the right question, and it deserves a direct answer. A scenario plan is not a prediction — and it's not a report that goes in a drawer after the strategic planning cycle. It's a decision instrument, and like any instrument, it has to be read correctly to be useful. This article walks through what a completed scenario analysis contains, what each part is actually telling you, and — critically — the signals that tell you when to pull it back out.

What a completed scenario plan contains

A scenario analysis built on the Alternative Futures framework moves through four phases. What you get at the end is not a single document — it's a layered set of outputs, each answering a different question.

The first output is a sharpened focal question: the specific strategic decision or challenge the entire analysis is built around. If that question drifted or was never quite right, everything downstream is off. Before reading anything else, re-read the focal question and ask: is this still the question that matters most?

The second output is a driving forces map: the factors that, if they shifted, would materially change the answer to your focal question. These are not trends — they are the mechanisms underneath trends. Your PESTEL analysis and Impact/Uncertainty matrix live here. The forces in the high-impact, high-uncertainty quadrant are the ones your strategy needs to be honest about. The ones in high-impact, low-uncertainty belong inside every scenario as a given.

The third output is four scenarios: genuinely different worlds built from your two most critical uncertainties. Read each one as a real operating environment, not as a probability. Ask: if I woke up three years from now inside this world, what would feel obviously right about our current strategy — and what would feel obviously wrong?

The fourth output is a strategy portfolio: moves sorted by how they perform across the four futures. This is where the plan becomes operational. The strategies that hold in every future are your no-regret foundation. The ones that only work in one or two futures are your hedges. Both are present in the output — the value is in knowing which is which.

How to read the scenarios

The four scenarios are the hardest section to use well, because the instinct is to find the "right" one and plan for it.

That instinct is worth resisting. The point of the analysis is to stop betting on a single future. Reading the scenarios as a ranking — most likely to least likely — reinstates exactly the problem the exercise was designed to break.

Read them instead as a diagnostic. Each scenario is a lens. The growth scenario tells you what your strategy looks like when its best assumptions hold — useful, but not the hard work. The discipline and collapse scenarios tell you where the strategy breaks. The transformation scenario tells you which of your current advantages depend on the rules staying the same.

The scenario your organisation finds most uncomfortable to discuss is almost always the most valuable one to spend time in. That discomfort is not a reason to move on. It's the reason the exercise exists.

How to read the strategy portfolio

The strategy portfolio is the operational output — the section that should change what happens on Monday.

Read it in three passes.

First pass: identify your no-regret moves — the strategies that hold in every future. These deserve full, confident commitment. Don't qualify them, don't hedge them, don't treat them as provisional. They hold regardless of which world arrives.

Second pass: identify your hedges — strategies that only survive in one or two futures. These are legitimate, but they need explicit conditions written alongside them: the specific signal that would trigger a review, and what you've already decided to do if that signal appears. A hedge managed explicitly is sound strategy. The same hedge managed as if it were a certainty is a liability building quietly.

Third pass: look for the gaps. What does the uncomfortable scenario demand that isn't in the portfolio at all? That absence is usually the most important finding in the whole analysis. A strategy tested against only the futures you find plausible hasn't been tested.

The part most teams skip: installing the signals

A scenario plan that sits on the shelf is not a scenario plan — it's a document. The output only earns its cost if it changes how you respond to what arrives. That means defining, before you close the project, what you're watching for.

Every scenario contains early signals: observable events that would indicate that world is beginning to unfold. Read them literally. For each signal, answer three questions before the planning session ends:

Who in the organisation is responsible for watching this? Not "the strategy team" — a named person.

What threshold makes it worth bringing to leadership? Not "when things look concerning" — a specific observable state: a regulation entering consultation, a cost threshold crossed, a market indicator moving below a defined line for two consecutive quarters.

What does the team already know to do when that threshold is crossed? The decision made now, before the signal appears, costs nothing to make and may be impossible to make under pressure later.

These are your tripwires. Without them, the plan gets reviewed when things go wrong — which is too late. With them, the plan gets activated on evidence, while there's still time to adjust.

When to pull it back out

The scenario plan is not a quarterly deliverable. It's a reference point for specific moments.

A driving force shifts. One of the forces in your high-impact, high-uncertainty quadrant starts moving. Pull out the relevant scenario and ask: what does it say our strategy should do now?

A major commitment is under review. Any time capital allocation, a significant hire, or a structural decision is being debated: is this a no-regret move or a hedge? Which future does it depend on? Is that future still plausible? A commitment made without answering those questions is a sunk cost in formation.

The environment feels different. Not a specific signal — a shift in texture. Conversations changing, assumptions that felt solid starting to feel uncertain. That's the moment to re-read the uncomfortable scenario. Not to predict. To orient.

The annual planning cycle. Before next year's plan is built: is the focal question still the right one? Are the driving forces identified still the relevant ones? Has any scenario moved from "plausible" to "emerging"?

The question worth asking

The plan is done. The scenarios are on the page. The strategies are listed.

Which of those scenarios are you watching for right now — and who is watching?

IGNISDRACO builds this process in four structured phases, with the outputs organised for exactly this kind of use. See a complete project in the interactive demo.