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.
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.
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.
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:
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?”
You’ve done it well when: every branch changes what you’d actually do, and you’d be ready whichever one turns up.
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.
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.
Output
You leave with:
Important rules
Planning to facilitate this activity? Access the resources below to get started.