@inproceedings{raptors2026-c091,
  title     = {{From Firefighting to Foresight: Re-engineering Our P1 Incident Response Pipeline}},
  author    = {Balaji, Rajesh},
  booktitle = {Proceedings of the Raptors Conference},
  volume    = {1},
  year      = {2026},
  publisher = {Hackathon Raptors},
  address   = {London, United Kingdom},
  doi       = {10.68495/rc.2026.C091},
  url       = {https://doi.org/10.68495/rc.2026.C091},
  abstract  = {This paper is a candid account of how a recurring pattern of P1 incidents was traced back to gaps in deployment hygiene and incident visibility, and how those gaps were closed with a unified incident dashboard, a deployment tracker, and a checklist that survived contact with real release pressure, which is the only test a checklist has to pass. It covers what broke, what went wrong at first, and the three problem-statement framework that emerged as the work moved from hackathon prototype to internal adoption. The central finding is stated plainly: P1s recur rarely because of the code and usually because of process visibility, which means the fix is rarely where the postmortem first points. Readers take away a reusable framework for diagnosing why serious incidents keep returning, together with a checklist and dashboard pattern they can adapt for their own deployment pipelines regardless of stack.}
}