The latest news from incident.io HQ

Do I need an incident debrief?

The dust has settled after your efforts to get things back on track during your last incident, and everything's once again working as it should. Time to get back to work? Possibly, but you might want to pause and take the time to look more deeply at what happened, and whether it's worth seeking out and socialising learnings more widely.

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...

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.