May 5 · 5 min read · The Folder Full of Stale Runbooks Every engineering org has a Confluence folder of incident runbooks. Every runbook was written during or after an incident. Each is a snapshot of how to fix one specific thing. After 2 years, the folder has 400 runboo...
Join discussion
May 2 · 4 min read · Why Severity Is Broken at Most Companies Everyone has severity levels. Almost nobody agrees on what they mean. Ask ten engineers what SEV-2 means and you'll get eight different answers. This causes: Under-paged incidents (people thought SEV-3 meant ...
Join discussionApr 20 · 3 min read · Everyone's Debugging, Nobody's Leading Five engineers in an incident channel. All debugging independently. Nobody coordinating. Three people checking the same dashboard. Two trying conflicting fixes. Customers waiting. This is what incidents look lik...
Join discussionApr 20 · 3 min read · What you'll learn: How to identify the root causes of AI agent failures before they impact users A structured incident response framework specifically designed for autonomous agents How to implement monitoring strategies that catch anomalies in real...
Join discussionApr 19 · 4 min read · MTTR Is a Lagging Indicator Everyone tracks Mean Time to Resolve. Few understand what actually drives it. MTTR isn't one metric — it's four: MTTR = MTTD + MTTA + MTTI + MTTF MTTD: Mean Time to Detect (monitoring fired) MTTA: Mean Time to Acknowl...
Join discussionApr 18 · 3 min read · Every Vendor Claims AI Magic Open any monitoring vendor's website and you'll see: "AI-powered incident detection!" "ML-driven root cause analysis!" "Intelligent alerting!" After evaluating a dozen AI ops tools and running three in production, here's ...
Join discussionApr 15 · 3 min read · The Post-Mortem Nobody Learns From I've sat through hundreds of post-mortems. Most follow the same pattern: something breaks, someone writes a Google Doc, we have a meeting, we list action items, nobody follows up, the same thing happens again in 3 m...
Join discussionApr 13 · 3 min read · The First 5 Minutes Matter Most I've been paged over 200 times in my career. The pattern is always the same: the first 5 minutes determine whether you resolve in 15 minutes or 3 hours. Here's what I've learned. The 3am Brain Problem At 3am, your cogn...
Join discussionMar 21 · 6 min read · A release broke payments for 10 minutes. So I added a meeting. Release retrospective. Every deployment gets a review. Sounds like leadership. Here's what actually fixed the problem. I got into the logs with the developer who shipped the feature. It w...
Join discussion
