Your team works in conditions that keep changing - requirements move, priorities flip, people get pulled away - and every change forces a painful replan. You build a detailed plan, it fails on the first change, and everyone calls it bad luck or scope creep.
The real problem isn’t bad planning. It’s hidden assumptions. Every plan depends on things staying true. When one changes, the plan fails exactly there.
Picture a sprint plan that depends on your lead engineer being available all month. Three days into the sprint, they’re pulled onto a production incident. The sprint stalls while everyone scrambles to reassign work. The plan didn’t fail because someone left - it failed because nobody had recognised “the lead engineer stays available” as a critical assumption.
In this activity, you first identify the assumptions your plan depends on, then test them against a realistic workplace shock. Finally, you redesign only the assumptions that fail by adding an early warning signal and a pre-agreed response.
First, identify the assumptions your plan depends on. Next, test them against a realistic change - a shock. Finally, redesign only the assumptions that fail by adding an early warning signal and a pre-agreed response.
A shock is any possible change - a person pulled away, a deadline moved up, a priority flipped - applied to the plan as if it had just happened.
Team: one person acts as the facilitator - they run the activity using the Facilitator Guide while everyone else takes part.
Solo ✓ Team ✓
Solo: 30–40 minutes. Team: 60–75 minutes.
The time required is indicative and will depend on the nature of the problem and the size of the team.
The facilitator should read the short facilitation guide first - about 10 minutes. It’s a downloadable PDF on this page.
Bring one real plan you’re working on now - a sprint, a delivery plan, a roadmap - not a hypothetical one.
Use it whenever:
You’ve done it well when: the team can point to where its plan would have failed, has named the assumption behind it, and leaves with a plan that adapts rather than fails when that change arrives.
Every plan depends on assumptions, whether they’re written down or not. When those assumptions change unexpectedly, the plan appears to fail. By naming and testing them in advance, you can redesign the plan before real life exposes its weakest point.
Everything is simple and on hand. Here is each piece, and when you use it:
Your real plan. The plan you’re actually working on - a sprint board, a delivery plan, a roadmap.
Assumption cards. Blank cards or sticky notes. Write one assumption per card - something the plan depends on staying true.
Shock List. A set of realistic workplace changes, provided as a PDF on this page. Draw one at random and treat it as if it has just happened.
Capture space. A board or wall to lay out assumptions, mark which ones fail under a shock, and capture the redesigned version.
Roles - Team: a facilitator (runs the activity and keeps the team focused on assumptions) and participants (name assumptions, test them, and redesign the plan). Solo: you run it yourself from this page.
Planning to facilitate this activity? Access the resources below to get started.