Time Compression Drill

When the deadline won’t move, cut the work until the core fits the time.

Time Compression Drill

What this fixes

The deadline won’t move, but the work won’t fit. So teams do the natural thing: they try to work faster while keeping the full scope. The result is predictable - everything ends up half-finished, and the deadline is missed.

The real block isn’t belief in speed - it’s that cutting scope feels like giving up. Deleting work feels like admitting defeat, so the team keeps everything and quietly misses. This drill changes that instinct. A shorter deadline is a smaller scope in disguise: it changes the question from “how do we work faster?” to “what can we remove so the essential still ships?”

How this works

Example: a team has three weeks of work and a ten-day deadline. Instead of promising to “move fast,” they name the one thing that must be delivered, then run the clock down in rounds - full time, half, a quarter. Each round forces another cut. By the end they’ve committed to a core that ships in ten days, with everything else explicitly deferred.

First, protect the core (the safeguard). Name the non-negotiable core - the minimum that must ship - before any cutting. The clock then compresses only the negotiable, never the essential.

Then run timed compression rounds. A shrinking timer intensifies the pressure - it is the amplifier, not the method. Each round gives radically less time (Full Build → Half Time → Critical Core) and forces another scope cut, while the core stays protected.

The cutting is the engine - it’s what delivers. By the end, the team has a plan that fits the deadline instead of hoping speed will make it fit. The drill teaches cutting, not trying to go faster.

Time required

Team ✓   About 30–45 minutes, with a facilitator. Genuinely quick and light - set a timer, run the rounds, protect the core.

The time required is indicative and will depend on the size of the scope and the number of people in the room.

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

When to use

Bring a real deadline that won’t move and a scope that won’t fit - a live situation, not a hypothetical.

Use it whenever:

  • the deadline is fixed, and the full scope genuinely won’t fit
  • the team plans to “work faster,” and you can feel it won’t be enough
  • you’d rather ship something real than miss with everything half-done
  • cutting scope feels like a failure, so no one will name what to drop

What you get

  • A compressed plan: the core that will ship in the time available
  • An explicit list of what’s been cut or deferred - decided, not dropped by accident
  • A scope that is aligned to the time on hand

You’ve done it well when: the team commits to a core that fits the time - rather than a full scope that it silently won’t finish.

What you’ll notice

  • The moment the room stops saying “faster” and starts saying “less”
  • How much can be cut while still shipping something real
  • That the clock made the cut - not anyone’s judgement being questioned

Why this works

Under a tight deadline, the instinct is to work faster because cutting scope feels like giving up. So the team keeps the whole scope and quietly misses the deadline. Protecting the core first means the pressure compresses the negotiable, never the essential - so the drill produces an intentional plan, not a panicked one. The clock makes the cut, so no one has to defend their judgement - the timer did.

What you need

A real piece of work. A live project or deliverable with a fixed deadline and more work than the available time.

A defined core. The minimum outcome that must be delivered - agreed before any scope is removed. The whole drill rests on this.

A timer. Any phone or stopwatch. You’ll use it to run the compression rounds - Full Build, Half Time, Critical Core.

A facilitator. One person keeps the team reducing scope - not promising greater speed - and records the final plan.

Steps

  1. Define the core (5 min). Agree on the minimum outcome that must be delivered. Write it down; it cannot be reduced during the drill. Test it: if you removed everything else, would this still deliver meaningful value? If not, your core is still too large.
  2. List the full scope (5 min). Write down everything currently planned for delivery. This is the Full Build - what you’d deliver with unlimited time.
  3. Round one - Half Time (8 min). Set the timer to half the time you think you need. Remove enough work that the remaining scope could realistically be completed in that time. The core stays intact.
  4. Round two - Critical Core (8 min). Halve the time again. Remove everything except the protected core and the work absolutely required to deliver it. This is where “faster” finally runs out.
  5. Finalise the plan (6 min). Record what will ship, what is deferred, and what the team commits to delivering - a plan that fits the time, not a full scope you’ll silently miss.

Output

You leave with:

  • The shippable core - what will actually be delivered in the time
  • The explicit cuts - what’s been dropped or deferred, on purpose
  • A plan the team commits to, because it fits the deadline instead of defying it

Important rules

  • Protect the core before you cut. Name the non-negotiable core first, always. Without this, panic produces fast, confident, wrong cuts - dropping essentials because they’re hard, keeping the minor tasks. After all, it’s easy. This one rule separates intentional delivery from panic prioritisation.
  • Cut scope; don’t promise speed. The drill teaches cutting, not trying to go faster. If the room’s answer is “we’ll work faster,” the drill hasn’t landed - push back to “what disappears completely?”
  • Let the clock make the cut. The compressing timer is the amplifier, not the method - but let it do its job. The pressure is what makes “less” feel necessary instead of like failure.
  • End explicit, not vague. Name what ships and what’s cut. A compressed plan the team can see beats a silent hope that it’ll all somehow fit.

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

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