Chris Evans's posts

incident.io on Ship It!

A few weeks ago, Stephen and I had the pleasure of talking to @Gerhard on changelog’s Ship It! Podcast. We chatted about incident workflows, our relentless focus on simplicity, and how incident.io uses incident.io when we have incidents ourselves.

We’ve raised $4.7 million from Index Ventures, Point Nine, and a host of incredible angels

We’re delighted to announce we’ve teamed up with Index Ventures and Point Nine to supercharge the next stage of growth and development at incident.io. With the support of number of angels, many of whom are customers too, we’re in the perfect position to deliver on our mission of world-class incident management for the whole organization 🚀

The things we find hardest in incident response

No matter how good your tooling is, how experienced you are, or how much you've prepared, incidents can still be hard. Despite the five of us at incident.io racking up some serious incident hours, we didn’t struggle to come up with a lengthy list of things we still find difficult in incidents.

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.

Fixing a Formula 1 car in under eight minutes

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

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?