DEV Community

CBT Tools
CBT Tools

Posted on Originally published at alexcoledev.github.io

On-Call Anxiety: Why PagerDuty Makes Developers Panic — and CBT Reframes That Help

On-call duty is part of the job for most developers. But when PagerDuty goes off at 3 AM, it's not just the alert that causes panic — it's the cognitive distortions that fire alongside it.

After working with 850+ developers on CBT techniques, I've identified 6 specific distortions that hit during on-call rotations.

The 6 On-Call Cognitive Distortions

1. Catastrophizing the Alert

Thought: "This alert means everything is broken."

Reality: Most alerts are noisy. 80% are non-actionable.

Reframe: "This is a signal to investigate, not a verdict on the system."

Tool: On-Call Thought Record — write down what the alert ACTUALLY means before responding.

2. Personalization ("It's My Fault")

Thought: "The database is slow — I must have broken something."

Reality: Correlation ≠ causation. The DB could be having issues unrelated to your deploy.

Reframe: "I'll investigate without assuming fault. Root cause analysis comes after mitigation."

3. Mind Reading ("My Team Thinks I'm Incompetent")

Thought: "They'll think I can't handle on-call if I escalate."

Reality: Your team WANTS you to escalate. Silence causes incidents.

Reframe: "Escalating is responsible, not weak. My team trusts me to know my limits."

4. All-or-Nothing On-Call

Thought: "I'm either fully on-call or completely off. I can't handle this."

Reality: On-call is shared. You have backup. You're not alone.

Reframe: "I'm part of a rotation. I handle what I can, escalate what I can't. That's the system working."

5. Fortune Telling ("This Will Be a Major Incident")

Thought: "This alert means we're going to have a 4-hour outage."

Reality: You can't predict the future. Most alerts resolve in minutes.

Reframe: "I'll take it one step at a time. Mitigate first, investigate after."

6. Should Statements

Thought: "I should have caught this in testing."

Reality: Hindsight bias. You did what you could with the information you had.

Reframe: "I'll add this to the postmortem action items. For now, focus on mitigation."

A Practical Tool: The Pre-Page Thought Record

Before you respond to the next alert, take 60 seconds to:

  1. Write down the automatic thought — "This is a catastrophe"
  2. Identify the distortion — Catastrophizing
  3. Challenge it — "80% of alerts are non-actionable. I'll investigate before assuming."
  4. Choose a reframe — "This is a signal to investigate, not a verdict."

I built a free On-Call Anxiety Thought Record that guides you through this process. No signup, no tracking — just a tool to help you think clearly at 3 AM.

Why This Matters

Burnout in DevOps is real. 42% of on-call engineers report burnout symptoms. The distortions above are the cognitive fuel for that burnout.

CBT techniques don't make the alerts quieter. But they do change how you respond to them — with clarity instead of panic.


Free CBT tools for developers: cbt-toolkit

Top comments (0)