The archive
Comic cover for issue 009: On-Call Without The Dread
Issue #009
CTO Survival Tips 6 min read· 28 Mar 2026

On-Call Without The Dread

Nine engineers, one pager, and a rotation people volunteered for. It took four changes, none of them technical.

Share
The strip
Panel 1 · Before
Whose week is it? Nobody knows. Everyone's anxious.
Panel 2 · Change #2
Every page must be actionable. Delete the rest.
Panel 3 · After
Two pages a month. People swap shifts as a favour.

On-call dread is rarely about the incidents. It's about ambiguity: not knowing whether you'll be woken, not knowing whether you'll be able to fix it, and not knowing whether anyone will help.

We removed the ambiguity in four steps. Published rotation a quarter ahead. Deleted every alert that had fired more than twice without action. Wrote a runbook for the top five real pages. Guaranteed a second responder, always.

If a page doesn't require a human decision, it isn't an alert. It's noise with a phone number.

Alert volume dropped by eighty percent, which sounds like a monitoring win but was really a psychological one. When a page means something, answering it feels like work rather than punishment.

Delete alerts aggressively. Silence is a feature.

The last change was the important one: time off after a bad night, taken visibly, by senior people first. Culture is what leadership does when it's inconvenient.

CTO takeaway

The lesson, minus the scar tissue.

  • Every alert must map to a documented human action, or be deleted.
  • Publish rotations far ahead — predictability is most of the relief.
  • Guarantee a second responder and visible recovery time after bad nights.
Comments

War Stories.

Survived something similar? Add it to the record — the best lessons in this archive came from other people's outages.

  • Priya · CTO, logistics startup

    We had the exact same Friday. Except ours was a DNS TTL of 86400 and we spent the weekend explaining caching to the board.

  • Marcus · Founder

    Read this on a Monday morning and immediately cancelled a rewrite. Three seams, not a clean slate. Thank you.

Never miss an issue

Get the next Chronicle in your inbox.

A comic, a story and a takeaway every other week. Written for founders who inherited a codebase they didn't choose.

Free forever. Unsubscribe in one click.

Related Chronicles.