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.
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.
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.
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:
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.
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.
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.
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.
You leave with:
Important rules
Planning to facilitate this activity? Access the resources below to get started.