The 2 AM Pager Test: Is Your Team's Ops Runbook Actually Good Enough? (Checklist Inside)

The 2 AM Pager Test: Is Your Team's Ops Runbook Actually Good Enough?

Here's a brutal question: if your on-call engineer got paged at 2 AM, could they fix the incident using only your documentation?

Most teams can't answer honestly. So here's the 2 AM Pager Test — run it this week.

The Test (Score Each Item 0-2)

1. One-line service map — Can anyone find "what talks to what" in under 60 seconds?
2. Top 10 failure modes documented — with the exact first command to run for each
3. Rollback procedure — copy-paste ready, tested in the last 90 days
4. Escalation chain — names + numbers, not "the platform team"
5. Backup restore drill — an actual restore was performed recently, not just assumed
6. Incident timeline template — one file, fills itself in, no blank-page panic
7. Postmortem template — blameless, one page, done in 30 minutes

Score 12+ out of 14: you'll survive a bad night.
Below 12: you're one incident away from a very expensive lesson.

The Fix Is Cheaper Than You Think

You don't need enterprise tooling. You need battle-tested templates — the same ones incident commanders use — adapted for small teams.

I packaged the exact set: runbooks, incident checklists, DR plan templates, and the 30-minute postmortem framework.

👉 Ops Starter Kit — everything on the checklist above, filled in for you.

Why "We'll Write It After the Next Incident" Fails

Because after the incident you're exhausted, and the knowledge evaporates in 72 hours. The teams that survive document before they need it — 20 minutes a week, done.

Run the test. If you scored below 12, you already know what to do.

---

More field notes: The First 30 Minutes After Ransomware