Adaptive Execution System

Rebuild your plan so it keeps working when things change.

Adaptive Execution System

What this fixes

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.

How this works

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.

Time required

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.

When to use

Bring one real plan you’re working on now - a sprint, a delivery plan, a roadmap - not a hypothetical one.

Use it whenever:

  • you’re planning work in conditions that keep changing - shifting requirements, moving deadlines, fluid priorities
  • the last few plans failed on the first change and had to be rebuilt from scratch
  • you’re about to commit to a plan and want it to survive the quarter, not just the kick-off
  • change keeps getting treated as failure rather than the normal run of things
  • a new project, team, or planning cycle is the moment to build resilience in from the start

What you get

  • The assumptions your plan depends on, named and made visible
  • The fragile ones redesigned - each with an early warning signal and a pre-agreed response
  • A plan that continues to work even when conditions change

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.

What you’ll notice

  • The “unexpected” change was sitting inside an assumption nobody named
  • Change stops feeling like failure and starts feeling planned-for
  • Less scrambling when conditions shift

Why this works

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.

What you need

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.

Steps

  1. Set up (5 min). Team: appoint a facilitator first. They run the activity and handle the Shock List. Lay out your real plan where everyone can see it. Place the assumption cards and capture space beside it. Solo: lay out your plan and the cards, then begin.
  2. Name the assumptions (12–15 min). For each part of the plan, write what it takes for granted - one assumption per card. Don’t discuss them until they’re all visible. Examples: “The lead developer is available all month.” “Requirements stay stable.” “The API is delivered before integration begins.” Be specific. Place each card beside the part of the plan it supports until the major assumptions are visible.
  3. Introduce a shock (5 min). The facilitator draws one shock from the Shock List and reads it aloud as if it has just happened. Treat the shock as real, even if it seems unlikely - the goal is to test the plan, not to predict the future.
  4. Test the assumptions (8–10 min). Starting with the first card, check whether it still holds under the shock. If it survives, leave it. If it no longer holds, mark it as failed and move it to the capture space. Continue until every assumption has been tested. The plan fails where assumptions fail.
  5. Redesign the fragile parts (18–22 min). Take each failed assumption one at a time. Ask: “What would tell us this assumption is starting to fail?” As a group, agree on an early warning signal, a response you’ll take if it changes, and a way to reduce or remove dependence on it. Record the redesign beside the failed assumption until everyone has a response.
  6. Re-test the plan (8–10 min). Re-read the same shock. Test the redesigned assumptions against it again. Ask: “If this shock happened tomorrow, would the plan still work?” If it still fails in the same place, strengthen the redesign and test again. The goal is not to eliminate risk; it is to make the plan adapt instead of fail.
  7. Commit (5–7 min). Lock the redesigned plan. Name the early warning signals you’ll monitor, who monitors them, and what action follows if they appear. Stop there - don’t redesign the whole plan from scratch. The goal is a more adaptive plan, not a new one.

Output / Takeaways

  • The assumptions your plan depends on, named - and which ones are fragile
  • Each fragile assumption has an early warning signal and a pre-agreed response
  • The reusable question for next time: “Which part of this plan assumes nothing will change?”

Important rules

  • Name the assumption before you redesign - you can’t protect what you haven’t surfaced
  • A shock must be plausible for your world, not a freak event
  • Redesign means an early warning signal plus a pre-agreed response - not just “be ready”
  • Re-test every redesign against the same shock
  • This builds the plan to absorb change - it is not a full replan after change has already landed

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

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