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.
Industry Interviews: Colm Doyle, Incident Commander at Slack
We talk to Colm Doyle about his experiences as an Incident Commander at Slack.
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.
What is an incident?
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 think there's a better version of the world out there, where the same principles that help the world's best technology teams can be enjoyed by **the entire organisation**. We also think we know why it's not happening, and what can be done about it.
Don't count your incidents, make your incidents count
Whilst setting incident targets might work in some organisations, it's worth considering whether they provide the signal you expect, and whether the implications of doing so have been properly considered.
Hello, world 👋
We're Pete, Stephen and Chris, and we're building [incident.io](https://incident.io) - the best way for you to respond to, review and learn from your incidents.
Stay in the loop: subscribe to our RSS feed.