Skip to the ideas
Scenarios

How to Build Two Scenarios Around One Clear Difference

Learn how to build two scenarios around one clear difference, trace its consequences and see which decisions remain useful across both futures.

The Lively Future Guide desk6 min read
Group of diverse volunteers planning at a table and unloading fresh vegetables from a van outdoors

The common mistake in scenario building is to change the mood rather than the conditions: one future feels hopeful, the other grim, but both follow the same path. That contrast can leave a team’s assumptions untouched. To build two scenarios that inform a decision, give them one clear difference and trace what follows from it.

What decision should the scenarios inform?

Start with a choice that has real consequences. A local food organisation, for instance, might be deciding whether to rely on one distribution hub or keep several smaller routes available. Its question is not “What will happen to food distribution?” but “Which operating choices remain useful if access to the hub changes?”

A scenario is a coherent account of how relevant conditions might develop. It is not a prediction, and it need not describe every part of life. For this decision, road access, local demand and delivery arrangements may matter; unrelated changes may not.

Write down the decision question before drafting either future. If a contrast would not change what the organisation needs to consider, it is probably not the right contrast.

How do you choose the difference between two scenarios?

Choose one condition that could plausibly develop in more than one direction and would affect the decision. This is the branching condition. For the food organisation, it might be whether local delivery partners remain available or become difficult to rely on.

Then trace consequences rather than merely changing a detail. If partners are less available, route coordination may become harder, the organisation may need relationships with other groups, or it may need to adjust what it promises residents. Each consequence should connect to the condition instead of being added for drama.

Think of the branching condition as a hinge: one point allows a door to open into different spaces. In the same way, one change can lead to distinct operating environments, as long as each consequence follows from the starting condition.

Which approach suits how to build two scenarios?

When does a single-condition contrast work best?

Use it when one major uncertainty shapes the decision and a clear comparison is useful. Hold the decision question steady, describe each direction the condition could take, and trace the implications for people and resources.

When should you use a scenario matrix?

Use a matrix when several uncertainties may interact. A team could consider both the reliability of local partners and the level of demand, then compare combinations rather than assuming that one condition determines everything.

When is a narrative-led approach useful?

A narrative-led approach can clarify how change might affect people in different roles or places. Keep the branching condition constant, then describe its possible implications for a coordinator, a delivery partner and a resident without presenting any viewpoint as a forecast.

How do you choose between these approaches?

Choose a single-condition contrast for clarity, a matrix for interacting uncertainties, or narrative-led development when human context makes the implications easier to see. You can combine approaches, but keep the central difference visible.

How can you build a distinct pair?

Say a neighbourhood food group must decide how much to depend on its usual delivery partners. It chooses partner availability as the branching condition. In one scenario, the partners remain dependable; in the other, they become intermittently available. The group traces what each condition could mean for coordination, communication and commitments to residents.

In the first future, the group might make shared routes easier to coordinate. In the second, it might consider a more flexible arrangement with several local organisations. These are possible responses, not automatic outcomes; the scenario needs to explain why each could make sense.

Use the following checks to keep the work tied to a decision. For each item, the observation determines whether to keep the draft as it stands or revise it:

  • Decision question: If the draft names a specific choice, keep it; if it names only a broad topic, rewrite it as a decision the organisation must make.
  • Branching condition: If the condition could plausibly develop in different directions and affect the choice, keep it; if not, select a more relevant uncertainty.
  • Starting point: If each scenario clearly states how the condition develops, keep the distinction; if either relies on a vague label, describe the condition plainly.
  • Comparable focus: If both scenarios examine the same decision area, compare them; if one shifts to an unrelated issue, bring it back to the shared focus.
  • Causal links: If each consequence follows from the stated condition, retain the link; if a step is missing, add the intermediate change or remove the unsupported consequence.
  • Responses: If a choice remains sensible in both futures, mark it as a possible robust response; if it works in only one, note the condition on which it depends.

The checks do not require equal detail in both scenarios. They help you spot when one has a credible chain of events while the other has been reduced to a label.

How do you check whether the contrast is real?

Read each scenario on its own, then compare the decisions it makes relevant. If the same actions seem sensible for the same reasons in both, the difference may be too shallow. If the decisions differ, check that the change follows from the branching condition rather than from an extra assumption that has slipped in unnoticed.

Write a short causal chain for each future: condition, immediate effect, wider implication, decision consequence. For example, “Partners are less available, so route coordination becomes less predictable” makes the link visible without claiming that the whole food system will fail.

Check that the comparison is fair. A difficult operating environment should not be set against a future where every uncertainty resolves favourably. The aim is not equal tone; it is a clear contrast that shows what one changed condition might mean.

What questions help you use the pair?

What is a branching condition?

It is an uncertain condition that could develop in different directions and affect the decision under discussion. Naming it makes clear what separates the scenarios.

Do two scenarios need equal detail?

No. Give each enough detail to show a coherent chain from its starting condition to its implications. Add detail where a causal link is unclear, not simply to make both accounts the same length.

Can scenarios include more than one uncertainty?

Yes, especially when uncertainties interact. A matrix can help organise combinations, but keep the decision and the important differences clear enough to compare.

Are scenarios predictions?

No. They are plausible accounts used to examine choices under different conditions. Treating one as the expected future would narrow the purpose of the comparison.

What should you do with the pair?

Use the scenarios to identify choices that remain useful across both, choices that depend on the branching condition, and signs that might prompt a review. Do not pick the more comfortable story as the forecast. The value lies in making assumptions visible and considering a decision in more than one plausible context.

When someone searches for how to build two scenarios, the useful starting point is the decision, not two contrasting moods. A clear branching condition keeps each future connected to a question that someone needs to answer.

Our point of view

One future is never the only one worth seeing.

We treat forecasts as prompts for thought, not promises. Looking across possibilities can make present-day choices easier to examine.

About our approach