LEARN. PRACTICE. GROW.Concept and mechanism
A team plan needs to account for operations, absence, learning, maintenance, and project work. Available headcount does not automatically equal delivery capacity. Frequent interruptions reduce focus time and can prevent improvements that would reduce future load. Gather work data and listen to the team’s experience before concluding that effort is insufficient or hiring alone will solve the problem. Toil describes operational work that is often manual, repetitive, and automatable, without enduring improvement. An intervention eliminating a recurring cause can be engineering even when it initially requires manual effort. Administrative tasks unrelated to running the service are overhead, not automatically toil.
Guided application
In an original exercise, four people have ten working days each, but half the capacity is already allocated to operations and absence. Twenty person-days remain for other activities before new commitments. If the project requires twenty-eight, an eight-day gap needs a decision. Expose scope, sequence, timing, or capacity options to those able to decide. Protect time to reduce repeated alerts and manual requests, measuring the effect after the change. Google SRE’s stated goal of 50% engineering work belongs to its context; it does not replace a hybrid APS role allocated 75% to support and 25% to projects. Reported overload deserves investigation even when ticket counts appear stable.
4 × 10 × 50% = 20 person-days; 28 requested leaves a gap of 8.
Common pitfalls
Maximum utilization treated as productivity; ignoring interruptions; automating without measurement; imposing external ratios.
Related topics: Mandate, autonomy, and delegation · Feedback and skill development · Technical decisions and quality
Make demand visible and invest in reducing repeated load.
Reference: Identifying and Recovering from Overload · GitLab Handbook 2026; DORA current five-metric model; SRE and engineering guidance reviewed 2026-09-30