The latest news from incident.io HQ

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 organization**. 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 organizations, 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.

Optimizing incident response: Understanding DORA's Time to Restore Service metric

By using DORA's time to restore service metric, organizations can reduce downtime through meaningful improvements to their response processes.

Development efficiency: Understanding DORA's Mean Lead Time for Changes

By using DORA's Mean Lead Time for Changes metric, organizations can increase their speed of iteration

6 strategies to help you improve, and future-proof, your service level agreement metrics

With these strategies, you’ll be able to set SLAs that ensure the best results for your customers and organization.

10 service level agreement practices you should implement

When you’re crafting SLAs, it’s important to make sure that you’re including sensible targets that you’re well-equipped to honor.

What are runbooks and how do they fit into the incident management picture?

In this article, we'll dive into the world of runbooks and explain how they fit into incident management workflows.