Field notes on staying on-call.
Guides on escalation, rotations, and incident response — for engineering teams, MSPs, healthcare, and families.
On-Call When You're a Team of One: What Actually Matters for Solo Founders
Escalation policies, rotations, handoffs — most on-call guidance assumes a team. None of it applies when you're the entire on-call schedule.
Read the postOn-Call Overrides: Handling Vacation, Sick Days, and Holiday Coverage Without a Scheduling Mess
The on-call schedule that works fine for eleven months a year is the one that falls apart every December — unless overrides are built in as a first-class feature, not a workaround.
Read the postOn-Call Burnout: Early Warning Signs and How Rotation Design Prevents It
Burnout doesn't start with someone quitting — it starts with paging patterns that are visible months earlier, if you know where to look.
Read the postHow Small Teams Handle On-Call Compensation
There's no universal standard for paying on-call — but there are a handful of models small teams keep converging on, for good reasons.
Read the postOn-Call Schedule Best Practices for Small Teams
A rotation that works for a 20-person SRE org will burn out a 4-person team fast. Here's what actually fits a small team.
Read the post