Why does on-call just mean firefighting, never fixing?
Your pager goes off. You patch it. You go back to bed, or back to your real work. Next week, the same system fails the same way. You call this on-call. It is actually a loop your team built, and keeps feeding. No one chooses to get paged at 3am. But your pod chooses, every single week, what happens in the hour after. You can write a fix that removes the cause. Or you can close the ticket and wait for it to happen again. That choice is yours. The outage was not. Stop asking how to handle the stress better during an incident. Ask what your pod decided not to fix last time, and why you let it slide.
The stress is not your real problem. The real problem is your pod treats every fire as new, when most are old fires coming back. On-call will not improve because you get calmer during it. It improves when your team chooses, every week, to fix one cause instead of only patching the symptom.
What changes unlock by starting
- Fewer repeat pages for the same root cause within a few weeks.
- A real list of fixes your pod has finished, not just logged.
- Less dread before on-call shifts, because fires shrink instead of multiply.
- A team that treats incidents as information, not just interruptions.