The rota that burns out your best engineer.
The scenario:
Look at who resolved the last ten out-of-hours escalations. It is the same name, is it not.
Skill concentrates load. The engineer who fixes things fastest becomes the one everyone calls, the rota bends around their competence, and eighteen months later you are reading their resignation and calling it a surprise.
The cost of losing them is worth writing down. Recruiting a senior engineer runs to months of searching, a salary premium, and a year before they carry the same context. The rota fix costs a fortnight of planning. Reading the two numbers side by side is usually all the argument the change needs.
The prompt:
You are rebalancing an out-of-hours on-call system for an MSP.
Context: [team size, current rota shape, escalation counts per person if known, compensation model]
Build:
The load audit: escalations handled per person over 90 days, including informal “quick calls” outside the rota
The rebalance: rota changes plus the capability fixes so the load spreads, runbooks for the top five night issues, and shadowing pairs
The protection rule: what a person on a heavy week is excused from during the day
The compensation check: whether pay matches reality, and the retention cost comparison against replacing the person