Requirement Drift Simulator

See when the baseline needs to change.

Requirement Drift Simulator

What this fixes

The requirements changed. The baseline didn’t. The project became unstable. Each change was reasonable - a customer learnt something, a dependency appeared, a new need surfaced. Accepting those changes wasn’t the mistake. The mistake was continuing with the original scope, timeline and resources as though nothing had changed.

This tool makes the accumulated drift visible - so the team can decide when the work deserves a new baseline. Re-baselining means formally adjusting the original scope, timeline or resources to match what’s actually been accepted.

How this works

Imagine this: a customer portal starts as a simple self-service site. Over several months, the team accepts analytics, approval workflows, audit logging, multi-language support and SSO. Every request makes sense on its own, so the team says yes each time. The original schedule and staffing never change - and the project now feels far harder than anyone expected.

You build a tower - the original baseline, complete and stable - then run your accepted changes through it. For each change the team has said yes to (every ‘small’ scope addition, new requirement or extra stakeholder ask), someone pulls a block out. Each pull looks survivable. But the tower gets visibly less stable with every reasonable change, until one small pull brings it down.

The wobble makes the accumulated load visible - the delay, complexity and coordination cost you couldn’t see one change at a time. The tower doesn’t judge the changes; it shows what they add up to against a baseline that never moved.

Every change pulls one block, whether large or small. The point isn’t to measure the size of each change - it’s to make the build-up visible. What matters is that the baseline needed to move and didn’t.

Team: one person acts as the facilitator - they run the activity using the Facilitator Guide while everyone else takes part.

Time required

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

The time required is indicative.

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

When to use

Bring one real piece of work whose scope has been drifting - a project, release or deliverable that keeps absorbing ‘just one more’ change while the baseline stays fixed.

Use it whenever:

  • a project has absorbed a series of reasonable changes and now feels unstable
  • the work is harder than the original scope explains, and no one can say why
  • you suspect you’re no longer building the project you originally committed to
  • you need to decide - at a leadership level - whether the accumulated changes now require a new baseline

What you get

  • The accumulated changes, made visible as one picture
  • A felt sense of how far the work has already drifted from its baseline
  • A leadership decision: re-baseline, freeze, remove, or grow the foundation - with an owner

You’ve done it well when: the team can say “not one of those changes was unreasonable - and together they mean we’re no longer building the original project, so the baseline has to change.”

What you’ll notice

  • Each pull feels fine - until the tower starts to lean
  • The warning signs were gradual - the recognition is sudden
  • The question shifts from “was that change okay?” to “is this still the original project?”

Why this works

Teams judge changes one at a time, so each one feels reasonable, and the baseline is never questioned. Making the build-up physical lets everyone see and feel the structure weaken with every addition. And because the tower never blames a single change, the conversation shifts from “was that change okay?” to “does this work now deserve a new baseline?”

What you need

One real project whose scope has changed over time. A real project or deliverable that’s absorbed a series of changes - and its original baseline (the scope, timeline and resources you first committed to), written down. Keep the baseline visible the whole time; it’s the reference everything else is measured against.

One facilitator. They guide the discussion, tag each block with a real change, keep the baseline visible, and let the tower fall when it falls - the collapse is the lesson.

The block tower. A stacking-block tower (Jenga-style). Each block represents one accepted change; pulling it stands for the load that change added to a baseline that never moved.

The change cards (write-on cards). Name each real change before it’s pulled, so the tower tells the team’s actual story - not a generic game.

Steps

  1. Name the work - and make the baseline visible (4–5 min). Team: appoint a facilitator first. Write the project whose scope has been drifting and its original baseline - the original scope, timeline and resources you first committed to. Keep the baseline in view throughout the whole activity: it’s the original intent that everything has drifted from.
  2. List the changes (8 min). Together, list every change the work has absorbed since the baseline. Capture every accepted change, even the small ones - and don’t judge whether it was justified; just capture it.
  3. Build and load (5 min). Build the tower. Then read each change card aloud and pull one block for each accepted change. Notice that every single pull looks survivable - because every change was reasonable.
  4. Feel the drift (10 min). Keep pulling, change by change, until the tower visibly leans or falls. Stop and look: this is how far the accepted changes have moved the work from its baseline.
  5. Re-baseline - a leadership decision (10 min). Decide whether this is still the original project or whether today’s work deserves a new baseline. Choose one response only: freeze scope, agree on a new baseline, remove work, or add the extra time, people or budget the new work requires. Record the owner.

Output / Takeaways

You leave with:

  • The full list of accumulated changes, in one place
  • A shared, felt sense of how far the work has drifted from its baseline
  • One leadership decision - freeze, re-baseline, remove, or grow - with an owner

Important rules

  • One block per real, accepted change - no generic pulls.
  • Read each change aloud as it’s pulled, so the story is the team’s own.
  • Let the tower actually fall - the collapse is the lesson, not a near-miss.
  • End with a re-baseline or a stop decision, not just the realisation. The collapse isn’t the output - the re-baseline is.

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

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