Scenario Planning for Programmes That Cannot Predict Their Way to Certainty

The programme forecast was credible when the board approved it. Six months later, a supplier has changed its roadmap, a policy decision is delayed, and a shared platform team has lost capacity. The forecast is now wrong—but nobody can say which assumption failed first, what to watch next, or who should decide whether to re-sequence, invest more, narrow the outcome, or stop.

The usual response is a new forecast. That is necessary, but it is insufficient. A forecast tells the organisation what it currently expects. It does not prepare the organisation for the materially different conditions that could change the programme’s value or feasibility.

Scenario planning is useful here when it is tied to current decisions. Its purpose is not to predict the future more accurately. It is to identify a small number of plausible conditions, test the programme’s choices against them, notice relevant signals early, and agree what action is warranted before options close.

First, separate four tools that are often conflated

Scenario planning is often dismissed because teams have already produced a forecast, a risk register, or a contingency plan. Each is useful. None does quite the same job.

Tool	Question it answers	Typical output	What it cannot do alone
Forecast	What do we currently expect to happen?	A planned date, cost, demand estimate, or delivery path	Explore a coherent break from current assumptions
Sensitivity analysis	How does an outcome change if one input changes?	A range around a cost, date, or benefit estimate	Show how several uncertainties interact to create a different operating context
Contingency	What will we do if a known risk materialises?	Reserve, fallback, recovery action, or workaround	Reveal an uncertainty the team has not yet recognised as a discrete risk
Scenario	What could the programme face if several consequential conditions develop together?	A plausible, internally coherent future context	Predict which future will occur or replace the forecast

The distinction matters because “best/base/worst” is usually arithmetic, not scenario planning. It changes the amount of one or two variables while leaving the programme’s world largely intact. A scenario changes the context in which decisions are made: the availability of skills, a regulator’s position, customer behaviour, a partner’s strategy, a technology constraint, or the readiness of a dependent service.

The UK Government Office for Science is explicit that scenarios are not plans or predictions. They are multiple possible futures used to explore how choices might work under different conditions. UK Government, The Futures Toolkit The OECD similarly describes strategic foresight as exploring plausible futures and their implications for choices in the present, rather than extrapolating one knowable future. OECD, Strategic Foresight

Only model uncertainties that can change a decision

Not every uncertainty deserves a scenario. Teams can generate an endless inventory of trends, risks, and speculation; that creates debate without changing the programme.

Start with a consequential uncertainty: a condition that, if it developed differently, would change a material decision about value, feasibility, timing, funding, scope, service readiness, or dependency management.

Ask four questions.

1. What decision could change? A funding tranche, go-live date, supplier commitment, benefit hypothesis, release condition, capability investment, or operating-model choice.
2. What assumption makes that decision sensible today? For example: a dependency will be ready, demand will reach a threshold, a policy will remain stable, or specialist capacity will be available.
3. What makes the assumption both important and uncertain? Importance without uncertainty is a fixed constraint; uncertainty without consequence is background noise.
4. What evidence would tell us that the assumption is changing? If no signal is conceivable, the programme may need a reversible commitment or an explicit judgement rather than a false trigger.

The answer should be specific enough to be governed. “The economy may change” is not a programme uncertainty. “A demand contraction could make the planned regional rollout unable to meet its benefit threshold before the next funding decision” is. It identifies the condition, the affected outcome, and the decision at risk.

Build a few coherent worlds—not a gallery of extremes

Choose two or three critical uncertainties and build three or four distinct, plausible conditions around them. The purpose is not to cover every permutation. It is to create enough contrast that leaders can see where today’s plan is robust, brittle, or dependent on a choice they have not yet made.

A good scenario is:

• Plausible: grounded in real drivers and constraints, even when uncomfortable.
• Internally coherent: its events can coexist; it is not a list of unrelated bad things.
• Consequential: it changes the attractiveness, feasibility, or sequence of an actual programme choice.
• Distinct: it challenges a different assumption from the other scenarios.
• Actionable: it permits a present action, a monitoring signal, or a contingent decision.

The government toolkit uses critical uncertainties to construct scenarios, then recommends stress-testing options against them to find where a policy, strategy, or project plan is robust and where it needs modification. UK Government, The Futures Toolkit This article adapts that logic to programme delivery. It does not require a programme team to recreate a national foresight exercise.

Avoid naming scenarios “best,” “base,” and “worst.” Those labels invite people to defend the base case and treat the others as odds around it. Names such as “Stable integration,” “Constrained transition,” and “Fragmented dependency” encourage the group to discuss the operating conditions and their consequences instead.

Turn each scenario into a decision system

The useful unit is not a scenario slide. It is a record that links a possible condition to a present decision. Use this proposed scenario-to-decision worksheet for every scenario that survives the initial workshop.

Worksheet field	What to record	Example question
Critical uncertainty	The condition that could alter value or feasibility	Will the shared identity platform be ready for the planned transition window?
Scenario	A coherent description of the conditions if the uncertainty develops in one direction	The platform is available late, supplier capacity is constrained, and operations cannot support a dual-running period.
Programme implication	Effect on benefits, milestones, cost, risk, dependencies, and operations	The planned rollout sequence no longer protects the benefit threshold or service resilience.
Leading signals	Observable evidence that conditions may be moving toward the scenario	Missed integration entry criteria; supplier vacancy rate; failed rehearsal; operational-readiness defects.
Trigger	The threshold at which a decision must be made	Two missed entry criteria, or no confirmed cutover capacity by the latest useful decision date.
Decision and owner	The choice and the authority accountable for it	Sponsor board decides whether to re-sequence, fund dual running, or defer a region.
No-regret action	A move worth doing across several scenarios	Complete interface discovery, preserve a fallback service path, and qualify an alternative supplier resource.
Contingent action	A move taken only if the trigger is crossed	Fund dual running and change the rollout sequence.
Review date	When the evidence and relevance of the scenario will be reconsidered	Before the next funding tranche and after the integration rehearsal.

The difference between a signal and a trigger is important. A signal prompts attention and investigation. A trigger requires a defined decision or escalation. “Monitor supplier health” is neither. “If the supplier’s confirmed specialist capacity falls below the agreed minimum for two reporting periods, the commercial lead escalates options to the sponsor board within five working days” is governable.

This structure reflects a wider principle: scenarios have no value until they change present actions. The Futures Toolkit calls policy stress-testing a way to identify robust options and contingency plans across changing conditions. UK Government, The Futures Toolkit The worksheet makes the required programme choices, evidence, and ownership visible.

Connect scenarios to the programme’s real levers

Scenario work becomes decorative when it sits in a strategy deck, separate from the mechanisms that govern the programme. Each worksheet should connect to four ordinary management systems.

Funding tranches. Tie the next commitment to the assumption that matters. If the programme needs evidence that demand, readiness, or a dependency has reached a threshold, do not release the irreversible funding tranche as if that evidence already exists. This is not a demand for endless gates; it is a way to match the size of the commitment to what is known.

Benefits. A benefit hypothesis often assumes adoption, capacity, policy, or operating behaviour. State which scenario threatens that assumption, the measure that would show erosion, and the authority that can revise, protect, or retire the benefit. A date can remain technically achievable while the benefit no longer justifies the work.

Dependencies. A dependency record should show more than a traffic-light status. For each material scenario, name the provider, receiver, readiness condition, consequence, buffer, and latest useful decision date. That changes a generic concern into a choice that someone can make.

Risk and governance. A scenario does not replace a risk register. It clusters interacting risks and external conditions around a material decision. The programme’s risk process can own individual responses; the sponsor or board should own the trade-off when a trigger crosses delegated tolerance.

PMI’s 2026 complexity report places scenario planning alongside practices that help teams identify emerging threats, map interdependencies, and prepare responses early in complex work; it reports use by about one in five practitioners. PMI, Pulse of the Profession 2026 This is a professional-body report of association research, not proof that scenario planning causes stronger programme results. Its practical implication is narrower: the work must connect uncertainty, interaction, and response before disruption compounds.

A bounded public illustration—and a worked example

The current NISTA Major Projects Annual Report data includes a Matrix programme record that describes structured scenario planning among mitigations supporting an informed decision on revised go-live dates. The entry links the work to testing, data migration, training, and dependencies outside the programme’s direct control. NISTA, Major Projects Annual Report 2025–26 data It does not disclose the scenarios, the decision process, or a measured outcome. It is evidence that a public programme has reported using scenario planning in a replanning context—not evidence that the approach succeeded.

Consider instead a hypothetical transformation programme that is replacing a claims platform and expects a benefit from reducing manual processing. It faces two critical uncertainties: whether the regulator will require additional evidence before release, and whether the operations team can recruit enough specialists to run the new and legacy services in parallel.

Its initial plan assumes timely clearance and full transition capacity. The programme develops three scenarios:

• Clearance and capacity hold: the expected release sequence remains viable. The no-regret action is to validate the evidence pack early and rehearse operational handover.
• Evidence expands: additional assurance requirements delay a release, but transition capacity is available. The trigger is a regulator request that cannot be met within the existing release buffer. The accountable authority decides whether to re-sequence lower-risk capabilities while evidence is completed.
• Constrained transition: clearance and capacity both become uncertain, making a full cutover unsafe. The trigger is an unresolved assurance issue plus a confirmed shortage of dual-running staff by the latest useful decision date. The sponsor board chooses among funding temporary capacity, narrowing the release, extending the legacy arrangement, or deferring the tranche.

The value of the exercise is not that one scenario “wins.” It is that the programme starts evidence work, handover rehearsals, and capacity options before it knows which condition will emerge. It also agrees who will make the hard trade-off before it becomes an emergency.

Review, retire, and resist the urge to ritualise

Review scenarios at moments when a decision could still change: before a funding tranche, after a major dependency test, when an external policy decision lands, or when a benefit assumption is due for reassessment. A monthly review with no decision horizon becomes another status meeting.

Retire a scenario when its uncertainty is resolved, its implication is no longer material, or its trigger has been absorbed into normal risk and delivery control. Add a new one when the programme’s value or feasibility depends on a condition that the existing set does not illuminate. Keep the set small enough that leaders can remember the signals and owners without consulting a slide library.

Do not use scenario planning to avoid a decision that is already available. If evidence establishes a likely course and the organisation has authority to act, act. Nor is it a substitute for a validated forecast, a safety case, formal regulatory analysis, contractual advice, or disciplined risk management. Use it when uncertainty is real, consequential, and connected—and when preparing a decision now is better than discovering the choice after it has disappeared.

Sources and editorial limits

• UK Government, The Futures Toolkit and OECD, Strategic Foresight — public foresight guidance used for definitions and methods, principally in policy/strategy settings rather than as direct programme-performance evidence.
• PMI, Pulse of the Profession 2026 and PMI, The Roles of Scenario Planning in Project Management — professional-body material; the latter is a 2009 conference paper and is used only for conceptual context.
• NISTA, Major Projects Annual Report 2025–26 data — current public programme record that reports, but does not independently evaluate, use of structured scenario planning.

The worksheet and hypothetical programme are Strategica synthesis. The article lacks interviews and a public case with independently verifiable scenario design and results. It should not be used as a substitute for statutory, safety, security, regulatory, contractual, financial, or formal risk-management controls.