Whether you’re a seasoned vet when it comes to incident response, or just getting started out, it can be easy to fall into the trap of doing too much all at once.
And it just makes sense.
Incident response is one of those things that doesn’t have a single, perfect formula, so teams can be left doing a little bit of everything in an effort to get it right.
That said there are some fundamentals that, regardless of how mature your organization is, can be a great launching off point to better incident response.
And that’s exactly what we’ll be talking about in today’s episode of the Debrief.
This time around, we’re joined by Viktor Stanchev of Anchorage Digital, to chat about actionable advice for responding to incidents—from declaration to post-mortem. We cover what having a good incident response even means, why it’s important to declare incidents early, how to better communicate during incidents and a whole lot more.
If you’ve been looking for practical advice for running incidents from a veteran in the space, you’re in the right place.
In this episode, we chat about why it's so important to building a strong culture of engineering at your organization.
This week, we're talking to Sabin Roman from Linear, to talk about how they build teams, their zero bugs policy and heaps more.
This week we sit down with Hank Jacobs, Staff Site Reliability Engineer at Netflix to discuss their deployment of incident.io across their organization.
Ready for modern incident management? Book a call with one our of our experts today.