Give people weeks where nobody will call them, and the on-call week becomes something they can survive.
Fixed escalation lists are one of the quiet cruelties of operations work, and I think most managers who run them have never carried the phone under one. The list looks tidy. What it does in practice is take every evening, every weekend and every night of sleep from people who may never get a single call, and it keeps doing it for years.
What is wrong with calling people in a fixed order?
Everybody carries the phone and nobody is ever free of it.
Give people weeks where nobody will call them, and the on-call week becomes something they can survive.
Before the rotation, we had four people running the primary infrastructure and a simple escalation order. Call the first person. If no answer, the second. Then the third. Then the fourth. That arrangement looks fair on paper and it’s not. Person one takes almost every call and gets destroyed. Person four is almost never reached and learns nothing.
The worse problem is what it does to the other three. Any of them might be next, so all four keep their phones on them all the time. Four people carry the burden and only one of them gets the calls.
That’s the manager’s fault, every time. The people on the list didn’t design it, and they can’t opt out of it without looking like they don’t care about the systems. The burnout that follows comes from a scheduling decision somebody could have fixed in an afternoon, and the job takes the blame for it.
How should an on-call rotation work?
One person, one week, then the next person. Nothing else to it. During your week you’re the one who gets called. During the other weeks you’re not. Nobody found this appealing at first. My team hated it, because what they saw was a week where every call was theirs with no one to pass it to. The week they were on had become harder. That part of their reaction was correct.
Why do people come around to a rotation?
Because they work out what happens during the other three weeks. Off rotation, they didn’t have to keep their phones with them. They didn’t have to answer. They could go somewhere without coverage, have dinner without checking, and sleep without listening for anything.
That had never been available under the old arrangement, and none of them had noticed it was missing until they got it. An on-call week is a cost. Three weeks of freedom is what you buy with it, and the trade is a good one as long as the freedom is real.
The off weeks are the best part of a rotation. Somebody who has had three weeks of real rest walks into their on-call week sharper and calmer, and a team that gets that rest stops updating their résumés.
What happens in a genuine emergency on an on-call rotation?
Anyone can be reached, and that path has to exist.
I put procedures in place so a real disaster could still reach anybody. Not everything is survivable by one person on duty, and a rotation that pretends otherwise will get broken on the first bad night. That destroys it permanently.
The distinction I drew is the part that makes it work. Off-rotation people didn’t need to be on call and didn’t need to be in a position to answer.
They might get reached. They weren’t required to be reachable. That’s a different thing and it’s the whole difference between a rotation and a schedule that exists on paper.
When is it acceptable to break an on-call rotation?
When the situation requires more than one person, and almost never otherwise.
The escape hatch is the most fragile part of the whole arrangement. Used for real emergencies, it costs nothing and preserves the boundary. Used because the person on duty was unsure and wanted company, it teaches everyone that off weeks aren’t real.
Two or three casual uses and the rotation is decoration. People go back to carrying their phones, because they’ve learned that not being on call doesn’t mean anything. I’d come down hard on anyone who reaches for the escape hatch out of nerves. It sounds harsh, but every casual call to an off-week person takes something from the whole team, and the person calling rarely sees that cost because they aren’t the one whose dinner got interrupted. Protecting that boundary is the manager’s job and it costs something. Occasionally the person on duty struggles alone with something a colleague could have solved faster, and that’s the price of everyone else having a real week off.
My take
Rotations work because of the weeks you’re off. My team hated the one I set up until they noticed they could put the phone down three weeks out of four. Those off weeks have to stay off, or people stop believing the schedule. Keep a path for true disasters to reach anyone, and use it rarely. Break the boundary for a routine problem once and nobody trusts the rotation again.
Why does schedule predictability matter more than pay?
Because nobody leaves over the night they got called.
They leave over two years of never being able to put the phone down. The particular Tuesday isn’t what wears people out. The absence of any period where the phone doesn’t matter is what does it.
That’s the entire argument about operations burnout without using the word. A team with real weeks off can sustain a hard on-call week indefinitely. A team where every week is a low-grade on-call week runs down slowly and nobody can point at when it started.
For a small company this is one of the few retention levers available that costs no money. A rotation with a real boundary is a scheduling decision and a discipline, and it changes how the job feels considerably more than a raise does.
Too many companies still grind good operations people down with always-on escalation, a lazy failure when the fix costs nothing but discipline. A manager who won’t set up a real rotation and defend it is choosing to burn out their best people, and they’ll deserve every resignation letter that follows.
Fourteen chapters of Street-Smart Management Wisdom follow three managers who have already faced what you’re about to face, told so you’re the hero instead of the student.
