Midsprint Reset

Stop a failing cycle, drop what won’t save it, and restart.

Mid-Sprint Reset

What this fixes

A sprint, project phase or release is losing pace. The team works harder because stopping feels like losing time. But the longer you keep executing a plan that isn’t working, the more effort goes into work that won’t actually save the cycle.

This tool pauses the work, separates what will save the cycle from what won’t, and restarts with a simpler plan. The halt buys time - it doesn’t cost it.

How this works

Imagine this: a sprint has three days left. The team is behind; people are multitasking across bug fixes, feature work and documentation, and everyone is busy - but the release still looks unlikely. Instead of pushing harder, the team stops for twenty minutes, lists everything currently consuming effort, and asks one question: will this actually save the sprint? Half the work is dropped or deferred, the remaining work becomes the only priority, and the sprint restarts with a realistic chance of succeeding.

You call a tight, time-boxed halt - about twenty minutes. You list everything the team is currently spending effort on, then sort it against one test: would this actually save the cycle, or not?

The gap between the two piles is the moment of recognition. Most of the effort is usually going into work that won’t save the cycle - and the team had quietly stopped believing the plan a while ago.

Then you re-baseline. The work that will actually save the cycle becomes the whole focus, everything else is dropped or deferred out loud, and the team restarts.

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

Time required

Team ✓   A time-boxed halt of about 20 minutes, with a facilitator.

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

When to use

Run it when a cycle is nominally ‘on track’ on paper, but the team is firefighting, pace is collapsing, and effort is scattering across work that won’t save it.

Use it whenever:

  • a sprint, phase or workstream is sagging partway through
  • the team is behind and instinctively grinding harder on the same plan
  • there’s a quiet sense the plan isn’t working, but no one has stopped
  • momentum is collapsing, and the deadline is still ahead

Not this tool: if the current plan is fundamentally wrong because reality has changed, use Replan the Plan. If the plan is still valid but the team has lost focus during the cycle, use Mid-Sprint Reset.

What you get

  • A fast, honest picture of where the team’s effort is actually going
  • The must-win work is separated from the work that won’t save the cycle
  • A re-baselined cycle - fewer things, restored momentum, a clean restart

You’ve done it well when: the team stopped, saw the gap, and re-focused - the halt took twenty minutes and bought back the rest of the cycle.

What you’ll notice

  • Most of the remaining effort wasn’t going to save the cycle
  • The team had quietly stopped believing in the plan a while ago
  • Stopping to see that was the fastest way forward

Why this works

When a cycle starts slipping, teams usually work harder instead of stopping to rethink the plan. A short, deliberate halt interrupts that instinct. Sorting work by one question - “will this save the cycle?” - makes wasted effort visible and permits the team to restart with a simpler, more realistic plan. The obstacle was never an inability to prioritise; it was an inability to stop.

What you need

One real cycle that’s currently slipping. Not finished, not yet collapsed - the team must feel the pace slipping now.

One facilitator. They call the halt, keep it tight, run the sort, and protect the restart - so it doesn’t become a retro.

A visible timer. The halt is time-boxed. Visible time pressure keeps the reset fast and stops it sprawling into a meeting.

Two labelled columns and cards. “Will save the cycle” and “Won’t save the cycle” - with one work item per card. The sort is where the recognition happens.

Steps

  1. Call a halt (2 min). Team: appoint a facilitator first. “We’re behind - so we’re stopping for twenty minutes instead of grinding on.” Start the timer.
  2. List current effort (5 min). Everything in flight right now - one work item per card. Capture honestly, including the polishing and nice-to-haves. Don’t judge value yet.
  3. Sort (6 min). Take each card and ask: would this actually save the cycle, or not? Ask the team to agree on each card before it moves - no silent sorting. See the gap between the two columns.
  4. Re-baseline and restart (7 min). The must-win work is the whole focus. Drop or defer everything else - out loud. Assign owners, then restart work immediately using only the must-win list.

Output / Takeaways

You leave with:

  • The must-win work, re-focused and owned
  • A named list of what’s been dropped or deferred
  • Restored momentum for the rest of the cycle

Important rules

  • Call a real halt - don’t just ‘re-prioritise quickly’ in the grind.
  • “Save the cycle” is the only sort test - not ‘useful’ or ‘nearly done’.
  • Drop work out loud. Quiet de-prioritising lets it creep back.
  • Keep it to about 20 minutes - past that, it’s the meeting you were avoiding.

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

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