Scan & Sense method guide
Scenario Analysis
Scenario Analysis tests options, risks, triggers and responses across a set of plausible futures.
Beginner-friendly guide · 4 min read
What Scenario Analysis does
Scenario Analysis tests options, risks, triggers and responses across a set of plausible futures.
Scenario analysis starts after plausible future worlds have been created. It compares the same strategic options across each world so that hidden dependencies and vulnerabilities become visible.
The result is not a single average score. It is a distinction between robust moves, scenario-dependent bets, useful hedges and choices that should wait for more evidence.
This is the decision-oriented follow-on to scenario development. It preserves the distinction between plausible futures and commitments while turning scenario discussion into explicit strategic choices.[1][2][3]
Rows are strategic options and columns are scenarios. Look for robustness and meaningful variation.
| Option | Stable demand | Regulated shift | Supply shock |
|---|---|---|---|
| Efficiency programme | |||
| Platform investment | |||
| Partnership hedge |
Robust: performs acceptably across contrasting scenarios. Conditional: needs a trigger or hedge.
InnovationFlow explanatory schematic, synthesised from the method sources[1][2][3].
Understand the method
The parts in plain language
When to use it
- Once a team has coherent scenarios and candidate options.
- Before committing to a large, hard-to-reverse investment under uncertainty.
A practical workflow
- 1
Select the options or commitments to test.
- 2
Assess each option in every scenario using consistent criteria.
- 3
Identify vulnerabilities, hedges, triggers and no-regret moves.
- 4
Move agreed responses into assumptions, monitoring or the roadmap.
Fictional worked example
Example: choosing a platform route
This example is illustrative rather than a reported case. A team tests build, partner and wait options across three industrial-data scenarios.
Observation:Strong control but high cost and slow learning.
Implication:Viable only where proprietary integration is strategically critical.
Observation:Fast in most futures but creates supplier dependence.
Implication:Use contractual exit rights and retain architecture knowledge.
Observation:Preserves cash but loses learning and customer access.
Implication:Replace passive delay with a small, reversible pilot.
From analysis to decision
How to interpret the result
- 1Do not average scores if the difference between futures is the point.
- 2Make the conditions behind conditional choices explicit.
- 3Move robust and hedging actions into the roadmap, and triggers into monitoring.
The interpretation guidance is an InnovationFlow synthesis of[1][2][3].
What a useful output looks like
Common pitfalls
- Do not average away meaningful differences between scenarios.
- Record why an option was judged robust or vulnerable.
References and method basis
- [1]Schoemaker, P.J.H. (1995). Scenario Planning: A Tool for Strategic Thinking. Sloan Management Review, 36(2), 25-40. Source ↗Original method source
- [2]Shell (n.d.). What are Shell Scenarios?. Shell Scenarios. Source ↗Originating institution
- [3]Phaal, R. and Muller, G. (2009). An architectural framework for roadmapping: Towards visual strategy. Technological Forecasting and Social Change, 76(1), 39–49. Source ↗Peer-reviewed research
This guide synthesises the named sources into practical questions for strategy and innovation work. It does not claim that using a tool by itself produces a successful decision.