Explain Scenario Planning: Process and Logic | Lucid
Explain Scenario Planning: Process and Logic
8 min read
A SaaS team commits to a new market on one demand forecast, then a hosting rule changes the launch economics. To explain scenario planning, build distinct, plausible futures around uncertainties that could change the decision, and test the same options in each. This guide shows how to construct those futures, check their logic, and set action triggers.
Key Takeaways
1Start with a decision and its deadline. A scenario that cannot change an action is too broad to be useful.
2Separate known commitments from critical uncertainties, then check whether each combination of assumptions could actually occur.
3Choose an option that survives several futures, or make a staged commitment with observable triggers for changing course.
How do you explain scenario planning clearly?
Scenario planning is a method for testing decisions against several plausible ways the operating environment could develop. It starts with a focal question, such as whether to enter a market before the next funding review. The team then identifies external uncertainties, builds coherent accounts of how those uncertainties might unfold, and asks what it would do in each case.
A forecast estimates an outcome under a set of assumptions. Scenario planning challenges the assumptions themselves. If a team merely labels its revenue forecast “high,” “base,” and “low” while keeping the same regulatory rules and buyer behavior in every column, it may still miss the change that makes its launch plan unworkable. Paul Schoemaker’s account of scenario planning as a strategic thinking tool describes scenarios as distinct, internally consistent views of the future.
Method
Question it answers
Where it stops
Forecast
What outcome do current assumptions imply?
It depends on those assumptions holding.
Sensitivity analysis
Which input most changes the result?
Inputs often move without a full account of why.
Stress test
What breaks under a severe condition?
It may examine one shock without a broader future.
Simulation
What range of outcomes follows from modeled inputs?
It cannot cover changes the model leaves out.
Contingency plan
What will we do if a named event occurs?
It may skip the forces that could create the event.
Scenario planning
Which decisions hold up across different plausible conditions?
It requires judgment about which futures deserve attention.
These methods can work together. A team can run a cash-flow forecast inside each scenario or stress-test the preferred option after choosing it. The distinction is whether it has questioned the future operating conditions, rather than only changing numbers in one model.
Why are critical uncertainties more useful than predictions?
A critical uncertainty is an unresolved factor whose different outcomes would change the choice. Market growth may be uncertain, but if the team would take the same action at either end of its plausible range, it does not need to define a scenario. A potential local-hosting requirement matters more if it determines whether the company must sign an expensive infrastructure contract.
Begin by separating predetermined elements from uncertainties. An existing contract renewal date is known. The content of a pending rule is not. Driving forces, such as procurement behavior, regulation, and competitor moves, help explain what could change; the team should narrow them to the forces that affect its focal decision. The UK government’s Futures Toolkit for policy makers and analysts provides methods for examining drivers of change rather than treating a single projection as settled.
Two well-chosen scenario axes can make the differences visible. For a SaaS market-entry decision, consider whether buyers show enough willingness to pay and whether a binding rule requires local hosting before launch. Test the axes for dependence. A hosting rule could slow procurement, so “high demand with a hosting mandate” needs an explanation, perhaps that regulated buyers actively want a compliant provider. An assumption log should record that explanation and mark it for review. Otherwise, the team can quietly rewrite the story to favor its preferred investment.
How are coherent scenarios constructed and tested?
The scenario planning process needs an order because each choice constrains the next. A useful working method is:
State the focal decision and review date. For example: “Should we fund market entry at the next investment review?”
Record what is already known. Include contract dates, committed costs, and rules already in force. Separate evidence from assumptions.
Choose uncertainties that change the answer. Give each axis distinct plausible outcomes; reject variations that lead to the same action.
Write a short causal account for each future. Explain how buyers, regulators, partners, and competitors behave. Check for contradictions and second-order effects.
Test the same options in every future. Record consequences, observable signposts, and the conditions that would trigger a different action.
A scenario needs more than a label. If local hosting becomes mandatory, a partner might make entry possible but take margin and complicate support. If demand is strong without that requirement, selling directly may be faster, yet a rushed hiring commitment could make withdrawal expensive. Those consequences are what make the futures useful to a decision-maker.
Run a consistency check before comparing options: Could the stated rule and launch date coexist? Is a proposed partner available on the assumed terms? Does the demand story explain who signs and why? Keep unresolved points in the assumption log with an owner and a way to check them. Shell’s published scenario work illustrates the value of exploring different future conditions without presenting a scenario as a prediction. For a worked layout, a step-by-step scenario planning sample can help turn the logic into a comparison the team can revisit.
How do you explain scenario planning through a real decision?
A scenario planning example should show an action changing, not merely describe four possible futures. Suppose a SaaS company must decide now whether to fund entry into a new market. It can run limited paid pilots before its next funding review, but signing a local-hosting contract or hiring a full market team would be harder to reverse.
For this hypothetical company, management defines strong demand as at least three signed paid pilots by that review. That is a proposed decision threshold, not an industry benchmark. “Hosting required” means a binding rule applies before launch; a draft consultation is only a signpost.
Future at the review
What changes
Defensible action
Strong demand; no hosting mandate
Direct delivery remains available.
Fund a staged launch; pace hiring against signed contracts.
Strong demand; hosting mandate
A compliant delivery route becomes necessary and may reduce margin.
Confirm partner terms and unit economics before committing to expansion.
Weak demand; no hosting mandate
Entry is possible, but buyer evidence is thin.
Continue narrowly scoped discovery; defer the market-team commitment.
Weak demand; hosting mandate
Fixed costs rise while sales remain unproven.
Pause entry and preserve the option to return if conditions change.
Signposts show which future may be emerging; triggers authorize an action. Draft regulatory guidance is a signpost. Publication of a binding hosting requirement is a trigger to revise the delivery plan. Pilot conversations are signposts; signed paid pilots reaching the agreed threshold at the funding review trigger an investment decision. Assign someone to check both streams of evidence so the comparison does not become a risk matrix nobody updates.
The initial choice could be to fund pilots while avoiding an irreversible hosting contract. That is an adaptive plan: it buys evidence before committing further. Real options analysis for staged investments is useful when the value of waiting must be weighed against the cost of entering late. A decision matrix example can then compare direct delivery, a local partner, and delayed entry within each future, provided the team recalculates costs and constraints when conditions change.
Lucid turns free-form dilemmas into option maps that can be refined as constraints change; the team still has to agree on the evidence and triggers behind each path. When approval is needed, analysis of options and recommendation examples can help document why the selected commitment remains defensible, including the conditions under which the recommendation would change.
Frequently Asked Questions
What are the five steps of the scenario planning process?
Define the decision, separate known facts from assumptions, select critical uncertainties, construct coherent futures, and test options with signposts and action triggers. Record an owner for checking each consequential assumption.
What are the three types of scenarios?
There is no universal three-type standard. “Optimistic, base, and pessimistic” can be useful for forecasts, but scenario planning works better when futures differ in the forces shaping the decision, such as regulation and buyer behavior.
What is another word for scenario planning?
Strategic foresight is a broader term that can include scenario planning. “Contingency planning” is related, but usually concentrates on a response to a specified event rather than exploring several coherent futures.
Can you give a simple example of scenario planning?
A SaaS company considering market entry tests its launch plan under strong or weak buyer demand and with or without a local-hosting requirement. It funds pilots first, then uses signed contracts and binding regulatory guidance to decide whether to expand, partner, or pause.
A sound scenario exercise ends with a decision rule someone can use when new evidence arrives. Write down the choice, the assumptions that support it, and what would cause you to change course. If your options are still tangled together, register for Lucid to map them before the next decision review.
