Every crunch gets framed as temporary - ‘just this quarter’, ‘just this release’, ‘just until we hire’. Then eighteen months later the team is still working at an unsustainable pace (‘running hot’), having never decided to. Running hot gets rewarded now and punished later, so the ‘temporary’ pace quietly becomes normal. Nobody notices until something breaks - burnout, attrition or quality. This tool makes that pattern visible, then helps the team set a pace it can actually sustain.
Example: a platform team lays out its last six sprints. Sprint one: a weekend before the launch. Sprint two: two late nights, an escalation. Sprint three: another weekend, carry-over into four. Four, five and six look much the same. Asked which of the six was the temporary one, nobody can answer - because every single one was explained as the last one. The team hasn’t had a normal sprint in six months and had never seen it laid out.
Lay out the last five or six cycles using the crunch signals everyone remembers - late nights, weekend work, escalations, carry-over and missed commitments. Then ask one question: ‘which cycle was the temporary one?’ When nobody can answer, the pattern becomes obvious. Finally, agree a sustainable pace and a trip-wire (an early warning sign) that warns when the team starts drifting above it again.
This is a system, not a one-off. The reveal happens once; the sustainable line and the trip-wire stay in place - so ‘temporary’ can’t quietly creep back in.
Team: one person acts as the facilitator - they build the timeline and ask the question using the Facilitator Guide while everyone else takes part.
Team ✓ · About 30–40 minutes to set up - then an ongoing rhythm, with a facilitator.
The time required is indicative and will depend on how many cycles you plot.
The facilitator should read the short facilitation guide first - about 8–10 minutes. It is a downloadable PDF on this page.
Run it when the team has been in crunch for several cycles running, each one explained as temporary - and running hot has quietly become the unexamined normal.
Use it whenever:
Not the right tool if: one cycle is in trouble right now and needs rescuing - that’s Mid-Sprint Reset. If the problem is over-polishing rather than over-pacing, use Good Enough Line. And if there’s simply more work than the people can do, that’s a load problem before it’s a pace problem - use Capacity Triage first.
You’ve done it well when: someone says ‘this has been our normal pace for months’ - and the team sets a line and a trip-wire to hold a pace it can repeat.
The moment it lands: asked which of the last six cycles was the temporary one - and when exactly you were going to slow down - no one can answer. The temporary pace became permanent, and nobody chose it.
An unsustainable pace rarely feels dangerous while work is still shipping. Every push is explained as temporary, so nobody notices that temporary has become normal. Seeing several cycles together makes the pattern undeniable, and the agreed line and trip-wire stop it quietly returning.
The last 5–6 cycles, from memory. Sprints, months or releases - whatever the team runs in. You work from what people remember, not load data they don’t have.
One facilitator. They build the timeline, ask the unanswerable question, hold the silence, and help set the line and trip-wire.
Crunch-signal cards. One card for each signal the team remembers in every cycle - weekend work, late nights, escalations, emergency meetings, carry-over and missed commitments.
The line and trip-wire sheet. To record the pace the team agrees it can actually repeat (for example: no more than one weekend per cycle, recovery week protected after a release) and the signal that warns when crunch is returning.
Output / Takeaways
You leave with:
Important rules
Planning to facilitate this activity? Access the resources below to get started.