We're building the best way for your whole organisation to respond, review and learn from incidents. This is where we talk about how and why.
Learning from incidents - Formula 1
Picture the scene. You’re the head engineer at a Formula 1 racing team, and moments away from the start of a race when a minor mistake by your driver sees your car damaged on the way to the grid. You…
Industry Interviews: Colm Doyle, Incident Commander at Slack
Welcome to our Industry Interviews series, where we speak to a variety of interesting people about everything incident management. Who are you, and what do you do? My name’s Colm Doyle (@colmisainmdom…
One, Two, Skip a Few...
The other day, we started getting strange reports from some customers of incident.io. Their incident identifiers — unique numbers to identify each incident — appeared to have jumped unexpectedly. One…
What is an incident?
Webster's Dictionary defines 'incident' as... just kidding, I'm not going to do that to you. But really, in a world where things go wrong in organisations all of the time, what should our threshold be for defining an incident?
Why more incidents is no bad thing
For a long time we've anchored ourselves to the notion that we should have fewer incidents, or none at all. It's hard to argue against — why wouldn't we want to fewer things to go wrong?
Incidents are for everyone
We’ve spent our lives building products customers love, but we've also been pulled into more incidents than we can count, ranging from small blips quickly solved, to massive incidents that required…
Don't count your incidents, make your incidents count
We can't have more than two major incidents per quarter. It happens all the time: senior folks at your company feel like things are out of control, and they attempt to improve the situation by…
Hello, world 👋
We're Pete, Stephen and Chris, and we're building incident.io - the best way for you to respond to, review and learn from your incidents.