StrategyFramework / modelModelAccessible

Scenario analysis

How can scenario analysis support strategic choice or positioning?

AccessibleStrategicTeam2 min read

Contents

Scenario analysis, also known as horizon analysis or total return analysis, is a method of projection.

Scenario analysis examines how a decision performs under several internally consistent sets of assumptions. It is a projection and stress-testing method: instead of relying on one forecast, it makes uncertainty visible and compares outcomes, implementation demands and vulnerabilities.

When to use it

Use scenario analysis when a decision is consequential, difficult to reverse or exposed to several uncertain drivers. It can compare strategic directions, countries, locations, markets, capital choices or operating plans.

It is especially useful for questions such as:

Which strategic direction remains viable across plausible conditions?

Which country or region offers an acceptable balance of opportunity and exposure?

Should the organisation open a location, expand an existing one or wait?

Should it enter a new market or deepen its current position?

A simple optimistic, pessimistic and base case can test a financial plan, but richer strategic scenarios should differ in causal structure rather than merely applying high and low values to one forecast.

Origins

Scenario analysis has no single origin. It draws from military planning, decision analysis, financial stress testing and the scenario-planning work associated with Herman Kahn and later Royal Dutch Shell. In finance, the term can refer to recalculating value or return under defined changes; in strategy, it often examines coherent external futures and their implications.

What it is

The method specifies a set of conditions, calculates or narrates what follows and compares the decision across cases. It can reveal whether a plan depends on one fragile assumption, requires capabilities not yet available or creates an unacceptable downside.

Scenario analysis does not eliminate uncertainty and it does use historical evidence where relevant. Its distinction is that it does not assume history will repeat mechanically. The scenario logic should combine data, causal reasoning and explicit judgement.

How to use it

Use a five-stage process:

Define the decision and success criteria.

Gather evidence and map drivers.

Separate predetermined elements from critical uncertainties.

Develop and quantify coherent scenarios.

Compare choices and integrate the result into planning.

Define the problem. State the decision, owner, deadline, time horizon, alternatives and consequences that matter. Include the status quo.

Gather the data. Identify external drivers, internal constraints and dependencies. PESTLE can help scan political, economic, social, technological, legal and environmental factors. Use current evidence, reference cases and expert judgement with sources and confidence.

Separate certainties from uncertainties. Few future conditions are truly certain. Label predetermined elements, trends with bounded variation and critical uncertainties separately. Challenge what the team believes it knows, but do not assume the most cautious estimate is always the most accurate.

Develop scenarios. Combine a small number of high-impact uncertainties into distinct, plausible cases. Write the causal path, quantify material variables, test consistency and include leading indicators. Avoid cases that differ only in tone.

Use the scenarios in planning. Evaluate every option in every scenario. Identify no-regret moves, hedges, options to preserve, contingent actions and thresholds that would trigger a change. Assign owners to monitor indicators.

Practical example

A new consultancy plans to help clients implement specialised software and wants £1 million in turnover within five years.

The team maps demand, recession effects, the vendor’s upgrade, consultant availability and competitive entry. It verifies what it can about the beta release and separates evidence from assumptions. Three cases are developed:

Favourable: the economy recovers, the software performs well and no major rival overtakes it.

Constrained: recession persists for another two years and at least 25 per cent of prospective clients defer investment.

Disrupted: a global software company enters and establishes a strong position within two years.

Across the scenarios, the largest short-term exposure is fixed capacity and dependence on one vendor. A more robust strategy combines core staff with contractors, monitors rival products, cross-trains consultants and sets decision triggers for scaling. The value lies in these changed commitments, not in selecting one story as the forecast.

Top practical tip

Evaluate the same decision and metrics across every scenario. This reveals which actions are robust, which are contingent and which assumptions deserve early-warning indicators.

Top pitfall

Do not call a best, base and worst spreadsheet a complete view of uncertainty. Correlated drivers, discontinuities and competitor responses can create structurally different futures; challenge assumptions and causal consistency.