Scenario Split

Prepare for the two or three futures that matter — so you’re ready whichever one arrives.

Scenario Split

What this fixes

Teams naturally plan for the future that they expect to happen. Once work begins, that expectation quietly becomes the plan - and by the time the uncertainty resolves, you’ve already committed the effort.

You made a forecast and called it a plan. When the future genuinely isn’t under your control - the customer’s decision, the supplier’s delivery, the regulator’s ruling - betting everything on the one you hope for is a guess, not readiness.

This forces the single assumed future to split into two or three genuinely different branches, each with something you’d do differently now. When the future isn’t under your control, don’t bet everything on one prediction.

How this works

Example: you’re planning a release that depends on a supplier. The assumed future is “they deliver on time.” Split it: they deliver on time · they deliver two weeks late · they withdraw. Each demands something different of you this week - carry on · line up a contingency build · start qualifying a second supplier. Three futures, three different actions, all prepared for.

You split the assumed future into two or three branches. Not an exhaustive list - a small, genuinely distinct set. You can’t proceed with just one.

Now run the gate. If two branches lead to the same readiness action, they’re really the same branch - reject one. A branch earns its place only if it changes what you’ll do now. Plausible isn’t enough.

Each branch gets a readiness action - and a trigger. The action is what you’d do now to be ready. The trigger is the signal that tells you this branch has become the real one - otherwise, you prepare for three branches and never notice which arrived.

Team: one person acts as the facilitator - they force the split and hold the gate, using the Facilitator Guide, while the team takes part.

Time required

Team ✓   About 45–60 minutes, with a facilitator.

The time required is indicative and will depend on how many branches survive the gate.

The facilitator should read the short facilitation guide first - about 8–10 minutes. It is a downloadable PDF on this page.

When to use

Use it at a genuine fork - where you can’t control which future arrives, and different futures would change what you do now.

Use it whenever:

  • a decision you don’t control will shape your plan - funding, a customer’s choice, a regulator’s ruling
  • you’re about to commit effort against a future you’re only assuming
  • the team keeps planning for the outcome it hopes for
  • a supplier, partner or dependency could go several ways

Not this tool: don’t build scenarios for ordinary uncertainty. Use it only when different futures would genuinely change today’s decisions. And this is a delivery tool, not a strategy workshop - the question is “what do we do this week if any of these happen?”, not “what does the world look like in 2035?”

What you get

  • Two or three genuinely distinct branches - not one plan plus vague hedging
  • A readiness action for each - something different you’d do now
  • A trigger for each - the signal that tells you which branch has arrived

You’ve done it well when: every branch changes what you’d actually do, and you’d be ready whichever one turns up.

What you’ll notice

  • How many “branches” collapse into one when you ask what you’d do differently
  • That the team had already started executing against the hoped-for future
  • Preparing for three futures costs less than being wrong about one

Why this works

Teams naturally settle on the future they expect and quietly turn that forecast into the plan. Splitting it into a few genuinely different branches makes that assumption visible. The distinctness gate keeps the exercise honest by rejecting branches that don’t change today’s actions - so the discussion ends with concrete preparation instead of speculation, and the trigger tells you when to switch.

What you need

One real decision you don’t control. A genuine uncertainty - a pending approval, a supplier, a market move - where you can’t determine which way it goes, and the difference matters to your plan.

The assumed future, named out loud. The one the team is quietly planning for. You can’t split a future you haven’t admitted you’re assuming.

A whiteboard or capture sheet. With space for three branches, three readiness actions and three triggers - so the split is visible while you work.

A facilitator who holds the gate. One person forces the split and rejects branches that don’t change today’s action - the socially hard part.

Steps

  1. Name the assumed future (6 min). Team: appoint a facilitator first. State the fork you don’t control and the one future the team has quietly been planning for.
  2. Split it into two or three branches (12 min). Force it open: “the customer approves funding this month, next quarter, or not at all.” Two or three only - more dilutes readiness into paralysis. Don’t let the team jump to actions yet; finish defining the branches first.
  3. Give each branch a readiness action (15 min). For each: what would we do <i>now</i> to be ready for this one? Something you could actually start this week - not a strategy.
  4. Run the distinctness gate (10 min). Compare the actions. If two branches produce the same action, they are the same branch - <b>reject one</b>. Every surviving branch must change what you’d actually do.
  5. Name the trigger for each (8 min). What signal tells you this branch has become the real one? Without a trigger, you’ll prepare for three futures and never notice which arrived.

Output

You leave with:

  • Two or three distinct branches - each one changes what you’d do
  • A readiness action per branch - concrete, and for this week
  • A trigger per branch - the signal that this branch has arrived

Important rules

  • The distinctness gate. If two branches produce the same readiness action, they are the same branch - reject one. This is the rule that makes the tool work.
  • Decision-relevant, not merely plausible. A scenario earns its place only if being ready for it requires doing something different now. Plausible isn’t enough.
  • Two or three only. More than three branches dilute readiness into paralysis. A prepared few beats an exhaustive list.
  • Name the trigger for each branch. Otherwise, you prepare for several futures and never know when one has actually arrived.

Planning to facilitate this activity? Access the resources below to get started.

MIndn
Execution must be smooth. Not chaotic or stressful.
Built by Witmer.