DEV Community

CBT Tools
CBT Tools

Posted on Edited on Originally published at dev.to

Catastrophizing About Production Outages: A CBT Thought Record for On-Call Engineers

Catastrophizing About Production Outages: A CBT Thought Record for On-Call Engineers

Published on Dev.to | Tags: cbt, mentalhealth, productivity, webdev


You're on call. PagerDuty fires at 2 AM. Your heart races. Your mind goes blank. The first thought that hits you:

"This is it. The whole system is going down. It's all my fault."

If this sounds familiar, you're not alone. On-call anxiety is one of the most common — and most debilitating — experiences for developers. And it's not about skill. It's about catastrophic thinking about production outages.

The Catastrophizing Spiral

When an alert fires, your brain doesn't see a technical problem. It sees a threat:

  1. "This will bring down the company" — The alert is localized, but your mind makes it global.
  2. "I'm the only one who can fix this" — You're on call, so you're responsible. But you're not alone.
  3. "If I miss the SLA, I'm fired" — SLAs are targets, not threats. One miss ≠ termination.
  4. "PagerDuty is targeting me" — The rotation is random. You're on call because you're capable.
  5. "I must fix this RIGHT NOW or everything breaks" — Most outages are NOT emergencies. Breathe. Assess.
  6. "If something happens, it's my fault" — You're the firefighter, not the arsonist.

These are cognitive distortions — thinking patterns that feel true but aren't. CBT (Cognitive Behavioral Therapy) teaches us to identify and reframe these distortions.

The On-Call Thought Record

When PagerDuty fires, before you react:

  1. Stop. Don't touch the keyboard for 10 seconds.
  2. Write down your thought. "This will bring down the company."
  3. Find evidence FOR. "The alert is about the payment service."
  4. Find evidence AGAINST. "The system has redundancy. One service ≠ total failure."
  5. Reframe. "This is a LOCALIZED alert. I can assess and fix it."

6 Developer-Specific On-Call Distortions

1. The "This Will Bring Down the Company" Catastrophe

  • Thought: "If this alert fires, the whole company will go down."
  • Reframe: "Most alerts are LOCALIZED. The system has redundancy. One alert ≠ company failure."

2. The "I'm the Only One Who Can Fix It" Trap

  • Thought: "If I don't fix this, no one will."
  • Reframe: "You are part of a TEAM. Others can help. The system doesn't depend on one person."

3. The "If I Miss the SLA I'm Fired" Fallacy

  • Thought: "If I don't respond in 5 minutes, I'm getting fired."
  • Reframe: "SLAs are TARGETS, not threats. One missed SLA ≠ termination."

4. The "This Alert Is a Personal Attack" Error

  • Thought: "PagerDuty is targeting ME. It's always me."
  • Reframe: "PagerDuty is a SYSTEM. It rotates. You're on call because you're capable."

5. The "I Must Fix It Immediately or Else" Trap

  • Thought: "I must fix this RIGHT NOW or everything breaks."
  • Reframe: "Most outages are NOT emergencies. Take a breath. Assess. Then act."

6. The "If Something Happens It's My Fault" Fallacy

  • Thought: "If there's an outage during my shift, it's my fault."
  • Reframe: "Outages are SYSTEMIC. You're the firefighter, not the arsonist."

The 6-Card On-Call CBT Toolkit

🧘 On-Call Anxiety Thought Record

Write down your PagerDuty panic. Then reframe it using the steps above.

📊 SLA Reality Check

SLAs are targets, not threats. One miss ≠ failure. Keep a log — you'll see the pattern.

🤝 Team Reminder Card

You are not alone. The team has your back. Escalate when needed.

📈 Post-Incident Reframe

After the outage, write what you learned. Growth comes from incidents.

🔔 PagerDuty De-escalation

The alert is DATA, not a verdict. Respond, don't react.

🧘‍♂️ The 3-Breath Reset

Before you touch the keyboard: 3 deep breaths. Then act.

The Bottom Line

On-call anxiety is normal. It's not a sign of weakness — it's a sign that you care. But catastrophic thinking makes it worse.

CBT teaches us: the thought is not the truth. When PagerDuty fires, the thought "this will bring down the company" feels true. But it's a distortion. The reality is: you're capable, you have a team, and you can fix this.


This article is part of the **CBT×dev productivity-bridge series* — applying cognitive behavioral therapy to developer pain points. For more free CBT tools for developers, visit cbt-toolkit.*


If you found this helpful, follow for more CBT×dev articles. And remember: you're not alone on call.

Continue Reading — CBT for Developer Anxiety Series:


Free CBT Tools for Developers

Download my free CBT Thought Record Worksheet + distortion checker: Get the Toolkit

Built with vanilla JS. No signup. No backend. Privacy-first.

Top comments (0)