Most plans break for one simple reason: they assume only one future. I'm a Leading SAFe trainer at StarAgile, and I see this in almost every planning session I run. In this blog, I'll show you a simpler way to plan, so the next surprise doesn't throw your team off track.
What Is Scenario Planning?
Scenario planning is a strategic method that builds several plausible futures instead of a single forecast, so organisations can test their decisions against each one and prepare responses before events force their hand. Rather than asking "what will happen?", it asks "what could happen, and are we ready for each version?" The goal isn't to predict correctly. It's to avoid being surprised.
Who Developed It and Why?
The approach took shape in military planning at the RAND Corporation in the 1950s, where Herman Kahn used it to think through possible conflicts. Pierre Wack and his colleagues then adapted it for business at Royal Dutch Shell in the early 1970s. Shell had considered the possibility of an oil supply shock before the 1973 crisis hit, and that preparation is widely credited with helping the company respond faster than its rivals.
How Is It Different From Forecasting?
| Aspect | Forecasting | This Approach |
| Core question | What will most likely happen? | What could happen, and how do we respond? |
| Output | One projected number or trend | Several distinct, plausible futures |
| Handles surprises | Poorly, since it assumes continuity | Well, since it expects disruption |
| Best used when | The environment is stable | Uncertainty is high and stakes are large |
What Is a Scenario Planning Framework?
A scenario planning framework is the structure that turns open-ended uncertainty into a small set of distinct, usable futures, usually by finding the forces that matter most and combining them in different ways.
What Are the Core Components of the Framework?
-
A focal question, such as "What should our product portfolio look like in three years?"
-
Driving forces, meaning the trends, technologies, regulations, and behaviours that shape the answer
-
Critical uncertainties, the few forces that are both high-impact and genuinely unpredictable
-
Scenario narratives, short stories describing how each future unfolds
-
Signposts, early indicators that tell you which scenario is emerging
-
Strategic responses, the decisions you'd make in each future
A good one stays deliberately light. Six moving parts are enough, and teams that add more usually spend their time polishing documents instead of making decisions.
How Does the 2x2 Matrix Work?
You pick the two most critical uncertainties and place each on an axis, say "customer adoption: slow or fast" and "regulation: loose or strict". The four quadrants become four scenarios, and you give each a memorable name. Most teams start here because it's the simplest scenario planning framework to facilitate in a single workshop, and it forces a useful discipline: you can only choose two uncertainties, so you must decide which ones truly matter.
What Is the Scenario Planning Process?
The scenario planning process moves through six stages: define the focal question, identify driving forces, choose the critical uncertainties, build the scenarios, test your strategy against each one, and monitor the signposts.
What Are the Key Steps?
-
Frame the question: Agree on what decision the exercise is meant to inform.
-
Scan for forces: List everything that could shape the answer, from market shifts to technology.
-
Rank by impact and uncertainty: Keep only the forces that score high on both.
-
Build the scenarios: Write a short narrative for each future, including how it starts.
-
Stress-test your strategy: Ask what you'd do differently in each scenario, and which moves work in all of them.
-
Track signposts: Agree which early signals trigger a change of course.
Run properly, the scenario planning process is a loop, not a one-off event. You revisit it whenever a signpost fires or the focal question changes.
How Long Does the Process Take?
A focused workshop can produce draft scenarios in one to two days. A full organisation-wide programme, with research and interviews, can run for several weeks. Teams new to this often try to do too much, and a lightweight first pass that takes half a day will teach them more than a polished one that never ships.
What Are the Types of Scenario Planning?
The main types of scenario planning are exploratory, normative, qualitative, and quantitative, and most organisations blend more than one.
How Do Exploratory, Normative, Qualitative and Quantitative Approaches Compare?
| Type | Core Question | Best For |
| Exploratory | What could happen from where we are now? | Mapping a range of possible futures |
| Normative | What must happen to reach the future we want? | Working backwards from a target outcome |
| Qualitative | What story does each future tell? | Building shared understanding in workshops |
| Quantitative | What do the numbers look like in each future? | Testing budgets, capacity, and financial impact |
Which Type Suits Agile Organisations Best?
Of the four, a qualitative-led blend usually fits Agile organisations best. Narratives are quick to build and easy to discuss, and you can add quantitative backing for the parts that touch budget and capacity.
What Are Some Scenario Planning Examples?
Well-known scenario planning examples include Shell's preparation for an oil supply shock in the early 1970s, and everyday cases such as a product team planning for fast, slow, and stalled adoption of a new feature.
What Does a Business Example Look Like?
Picture a retail chain asking how it should invest over the next three years. It crosses two uncertainties, consumer demand (strong or weak) and supply chain stability (stable or disrupted), and gets four futures. In the strong-demand, disrupted-supply scenario, it might invest in supplier diversity. In the weak-demand, stable-supply scenario, it might protect cash and trim stock. Moves that appear in several quadrants, like better demand data, become the safe bets.
What Does an Agile or SAFe Example Look Like?
Imagine a Lean Portfolio Management group preparing for next year's funding. These scenario planning examples are illustrative, but the pattern is real.
| Scenario | Funding Signal | Portfolio Response |
| Funding contracts | Budget cut mid-year | Pause lower-value epics, protect the core value streams |
| Funding holds steady | Budget unchanged | Continue the current roadmap, review quarterly |
| Funding expands | Extra investment released | Pull forward the highest-ranked epics, add capacity gradually |
Which Scenario Planning Methodology Do Agile Teams Use?
Agile teams rarely adopt one formal scenario planning methodology. They borrow the core logic and fold it into the planning cadences they already run, and SAFe doesn't prescribe a single method either.
How Does It Connect to PI Planning and Lean Portfolio Management?
-
PI Planning: the ROAM approach to risks (resolved, owned, accepted, mitigated) is a natural place to ask "what if this goes wrong?" and agree a fallback plan
-
Lean Portfolio Management: strategic themes and lean budget guardrails give you the decisions to test across scenarios
-
Portfolio Kanban: epics can be re-ranked quickly when a different scenario starts to emerge
-
Inspect and Adapt: a regular moment to check your signposts and update the scenarios
A lightweight scenario planning methodology like this costs a few hours a quarter, and it turns planning from a yearly ritual into a living habit.
What Are the Best Scenario Planning Tools?
The best scenario planning tools fall into three groups: whiteboards for facilitation, spreadsheets for modelling, and portfolio platforms for capacity and funding what-ifs.
Which Tools for Scenario Planning Suit Agile Teams?
| Category | Examples | Best For |
| Digital whiteboards | Miro, Mural | Running the 2x2 workshop and building narratives |
| Spreadsheets | Excel, Google Sheets | Modelling budget, capacity, and cost per scenario |
| Visualisation | Power BI, Tableau | Power BI, Tableau |
| Portfolio platforms | Planview Portfolios, Jira Align | Large-scale capacity and funding what-ifs |
Most teams need only two tools for scenario planning: a whiteboard for the workshop and a spreadsheet for the numbers.
How Do You Choose the Right Tool?
-
Start with what you already own, since a spreadsheet handles more than people expect
-
Match the tool to the scale of the decision, not the other way round
-
Check whether it connects to your existing delivery data in Jira or similar
-
Keep scenarios easy to compare side by side, because that's where the value is
-
Avoid expensive scenario planning tools until you've run the process manually at least once
Conclusion
The point of this practice isn't to guess the future; it's to make sure your team isn't paralysed by whichever one arrives. Start with a single focal question, build four honest scenarios, and write down the signposts that tell you which way things are heading. You can run the whole exercise on a whiteboard and a spreadsheet before spending a penny on software. If you want to practise this alongside PI Planning and Lean Portfolio Management with a trainer, Leading SAFe Training is a good place to start. Revisit your scenarios every quarter, and treat any signpost that fires as a reason to talk, not to panic. Teams that do this stop being surprised, and that alone changes how they plan.
Frequently Asked Questions
1. Is scenario planning the same as risk management?
No. Risk management focuses on specific events that could harm a plan, while this approach explores whole alternative futures and how your strategy holds up in each.
2. How many scenarios should you build?
Most teams work with three or four. Fewer than that leaves you with a best and worst case, and more than that becomes too hard to remember or discuss.
3. How often should scenarios be revisited?
Quarterly works for most organisations, and immediately whenever a signpost fires or a major assumption changes.
4. Can small teams use it?
Yes. A half-day workshop with a whiteboard is enough, and small teams often benefit most because they have less margin for surprises.
5. Who should be in the room?
A mix of leadership, delivery, and customer-facing people. Diverse viewpoints surface uncertainties that a single department would miss.
