Hey Hackernews! I work at incident.io, where we’re building an incident management platform that helps your organisation deal with incidents at scale. Today,

Hey Hackernews! I work at incident.io, where we’re building an incident management platform that helps your organisation deal with incidents at scale. Today, we’re launching a set of resources intended to help those building their own incident processes that we’re calling the practical guide to incident management. It includes chapters on: - On-call, what it means, who’s involved, and how it should be compensated - Foundations, defining an incident, and advising on how you measure them - Response, for how to nail actually responding to the incident - Learning & Improving, with pragmatic tips on how you can level up and learn from your past incidents If you want to adopt pragmatic, battle-tested incident processes, or are looking to fine-tune an existing process, this guide is for you. For those familiar with the content, this guide differs from the Atlassian and PagerDuty response content in that it: - Acknowledges the way companies are working today: distributed teams, reliant on tools like Slack. - Focuses on process and practice outside of just responding to an incident - Provides actionable advice: real steps you can take right now - Extends beyond engineering, reflecting our belief that incidents are an entire company affair Very complementary content, but with different aims. We hope you find it useful! https://incident.io/guide https://incident.io/guide