OLD SCRIPT DETECTED
“The pager going off at 3am feels like it's my fault before I even check”
Try this response:
“I haven't read the alert yet — I don't know whose problem this is.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“The pager going off at 3am feels like it's my fault before I even check”
YOUR RECORDED RESPONSE
“I haven't read the alert yet — I don't know whose problem this is.”
ONE PRIVATE MOVE
Privately write down the last three 3am alerts you remember and note whether each one turned out to be your service or not, just for yourself.
The Half-Second Before the Alert Loads
- 01 / The Buzz Against the Water Glass
The phone rattles against the water glass on your nightstand at 3am, the pager tone unmistakable even through sleep. You haven't opened your eyes yet and you already know: whatever broke, it broke because of you. The room is dark, your partner shifts under the blanket, and your thumb is reaching for the screen before your brain has caught up to the hour.
- 02 / Reading Slack Before Reading the Alert
You open Slack before you open the actual incident, scanning fast for your team's name, bracing for it. When the alert turns out to belong to another service, relief floods in hard — and that relief is exactly what keeps the guilt-first habit alive, because it feels like proof you were right to brace. The nights it really is your service just confirm the pattern further.
- 03 / The Line You Haven't Read Yet
There's a specific moment you skip every time: the actual text of the alert, the service name, the threshold that tripped. You've assigned yourself the blame before you've read any of it. Catching that gap — the fault landing before the facts do — is the one second where you can choose to read first and decide after.
TRACE · 01/04
How this script runs you
- You check the incident dashboard before finishing the alert itself, hunting for your team's name first.
- The pager tone alone can leave you awake at 4am even on nights nothing was wrong with your service.
- You keep a private tally of how many 3am pages 'were about you,' separate from the ones that weren't.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Incident Ledger
If a pager goes off in the middle of the night, the fault must belong to someone — and until proven otherwise, that someone is you, no matter what the alert text actually says.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- I haven't read the alert yet — I don't know whose problem this is.
- The pager doesn't know my name. The alert text does the naming, not my guilt.
- Being on call means being present, not automatically being the cause.
Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.
INSTALL · 04/04
The protocol, on one card
When I think
“The pager going off at 3am feels like it's my fault before I even check”
I say
“I haven't read the alert yet — I don't know whose problem this is.”
Then I do one thing
Privately write down the last three 3am alerts you remember and note whether each one turned out to be your service or not, just for yourself.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "The pager going off at 3am feels like it's my fault before I even check". Word for word — the wipe targets the sentence, not the vibe.
- Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
- Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
- Run the loop: play it every morning and night, log one proof action a day for 7 days.
Straight answers
Why do I feel guilty before I've even unlocked the phone?
Because some past pages turned out to be your service, the blame shows up first and the checking happens second — that's a habit of order, not a fact about who caused tonight's alert.
Does checking Slack before the alert make the guilt worse?
Scanning for your team's name first turns the alert into a verdict search rather than information. Reading the raw alert text first keeps the incident about the system, not about you.
Is it useful to track how many 3am pages were actually mine?
A private count can be clarifying, but only if you use it to notice how often you guess wrong before checking, not to build a bigger case against yourself.
Related old scripts
Related self-checks
Related science
Related mechanisms
The research behind this script
- Postmortem Culture: Learning from Failure — Google SRE, Google SRE Book, 2016
- Invisible Labor in Open Source Software Ecosystems — Champion et al., arXiv, 2024
- Stack Overflow 2025 Developer Survey: Trust in AI at an All-Time Low — Stack Overflow, 2025
- A Mosaic of Perspectives: Understanding Ownership in Software Engineering — arXiv, 2025