Execution Pacing System

Set a pace your team can repeat, cycle after cycle.

Execution Pacing System

What this fixes

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.

How this works

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.

Time required

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.

When to use

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:

  • each crunch is framed as ‘just this one’ - and there’s always a next one
  • the team keeps saying it’ll slow down ‘after’ a milestone that keeps moving
  • weekend work, late nights and escalations have become routine
  • you sense the pace can’t hold but no one has called it

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.

What you get

  • A timeline of your real pace, built from the signals you remember
  • The recognition that the ‘temporary’ pace became the baseline
  • A sustainable line you can repeat - plus a trip-wire that protects it

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.

What you’ll notice

  • You can’t point to the cycle that was actually temporary
  • ‘We’ll slow down after this’ has been true for a long time
  • Nobody consciously chose the pace you’re running. It wasn’t a bad decision - it was no decision at all.

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.

Why this works

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.

What you need

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.

Steps

  1. Name the cycles (4 min). Team: appoint a facilitator first. Lay out the last five or six cycles on a timeline, one slot each.
  2. Fill in the crunch signals (8–10 min). For each cycle, from memory: weekend work, late nights, escalations, emergency meetings, carry-over, missed commitments.
  3. Ask the question (4–5 min). ‘Which cycle was the temporary one - and when were we going to slow down?’ Then stop talking. Let the silence land.
  4. Set the sustainable line (8–10 min). Define a pace with recovery built in - something you could actually repeat, not your ideal pace. For example: one weekend maximum per cycle, a protected recovery week after a release, no two cycles running with carry-over.
  5. Install the trip-wire (6–7 min). Pick one early crunch signal that flags when the pace creeps back, and name who watches for it.

Output / Takeaways

You leave with:

  • A timeline that shows the ‘temporary’ pace became permanent
  • A sustainable line the team can repeat, with recovery built in
  • A trip-wire and a named watcher to hold it

Important rules

  • Plot remembered signals - not load percentages no one has
  • The reveal is the question - ask it, then let the silence sit
  • Set a line you can repeat - not one you’d aspire to
  • Install a trip-wire and a watcher - or the pace creeps back (gradually returns)

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

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