Operations | Monitoring | ITSM | DevOps | Cloud

Incident.io

Why "why" is the wrong question to be asking after incidents with Dennis Henry of Okta

In last week’s episode of The Debrief, we had on Colette Alexander, Director of Engineering at HashiCorp, to discuss some of the myths around incident response. In that conversation, one of the myths we spoke about was the idea that asking “why” is better than asking “how.” And how, in reality, asking "how" allows you to focus more on the contributing factors that led to an incident happening, whereas “why” tends to single out a person, which can lead to a lot of blame.

Recapping our live event: On-call as it should be, present and future

The launch of On-call was an integral part of the incident.io mission to become the single place you turn when things go wrong, and recently we hosted a live virtual event to show how it all came together. In this event, incident.io Co-founder and CTO Pete Hamilton sat down with incident.io Product Manager Megan McDonald, Product Engineer Rory Bain, and fellow Co-founder and CPO Chris Evans to demo the product, discuss the journey of the creation, and expand on what’s next.

Why action items shouldn't be the goal post-incident #incidentmanagement #podcast

In this clip, Colette explains why focusing on coming up with a list of action items post-incident is a big mistake. About the episode: What if we told you that everything you thought you knew about incident response was wrong. Well, at least some of it. That some of the things you’ve been doing for years might not actually be having the impact you thought they did. Or, even worse, that some of the assumptions you’ve been making have actually been having a negative impact on you, your team and your organization.

The issue with DORA metrics #incidentmanagement #podcast

In this clip, Colette explains what the underlying issue is with DORA metrics. About the episode: What if we told you that everything you thought you knew about incident response was wrong. Well, at least some of it. That some of the things you’ve been doing for years might not actually be having the impact you thought they did. Or, even worse, that some of the assumptions you’ve been making have actually been having a negative impact on you, your team and your organization.

Our customers aren't just numbers-they're a priority

At incident.io, “We care about our customers” isn’t just a talking point. It’s a core part of how we operate. Whether it’s a big feature request or a small bug fix, we’ve been intentional about making sure that customers always feel heard and seen—no matter the ask. But it’s not just that.

The Debrief: Building a strong culture of engineering #incidentmanagement #softwareengineer

Whether you’re a seasoned company with 10+ years of operations, or a startup that’s just getting off the ground, making sure you have a good culture of engineering is really important. Not only will this have a significant impact on the folks on your team, it’ll make a big difference with hiring. When everyone knows that your company is the place to be when it comes to culture, attracting really good talent becomes that much easier.