Skip to content
All insights
OperationsCulture5 min read

The on-call rotation that doesn't burn you out

On-call doesn't have to ruin your week. The teams who get it right share a few habits that most others don't.

On-call is one of the highest-friction parts of engineering culture. Done badly, it's the reason people leave. Done well, it's a privilege — and there's a clear gap between those two extremes.

What separates good on-call

  • Alerts that mean something. False positives get fixed within a week.
  • Runbooks for the top 10 most common pages.
  • Time off after a bad on-call week, not just "thanks."
  • Postmortem actions that actually get done.

The compounding fix

Every page is a chance to make the system less noisy. Track it. Each rotation should leave on-call quieter than they found it. That habit alone is what separates teams that burn out from teams that don't.

On-call gets better when every page makes the next on-call's life easier.

Most operations are behind where they could be.

Book a strategy call. We'll map one system worth automating in the next 30 days. No pitch, just the plan.