The Quiet Rotation Pattern: Protected Deep Work
Treating on-call as ‘capacity 0’ for the week formalizes what already happens. Output goes up; burnout goes down.
Why on-call kills deep work
On-call engineers cannot focus. Background expectation of pages; can’t commit to multi-day work; default to small tasks.
The team plans around them having capacity that they do not have.
Four properties
- 1. No sprint commitments.
- 2. Default: code review, runbook updates, observability work.
- 3. Permission to refuse meetings.
- 4. Time-off if a week is heavy.
Capacity math
Lose: 20% of one engineer’s capacity.
Gain: focused work the rest of the team produces; reduced burnout retention.
Net: positive within a quarter.
Cultural shift
Manager has to defend the rotation in planning. Without that, ‘quiet’ gets eroded by ‘just one quick task.’
Cultural shift takes 2-3 cycles to stick.
Antipatterns
- Sprint commitments while on-call. Defeats the purpose.
- Quiet rotation only on paper. Manager pressures into work.
- No quiet rotation at all. Burnout grows quietly.
What to do this week
Three moves. (1) Apply this practice to your next on-call rotation. (2) Survey the team after one cycle. (3) Iterate based on feedback; the discipline is the cadence.