Want to up-level your reliability program? Let's start by identifying your opportunities for growth.
How much time are engineering teams spending on incidents?
Are you trying to set your engineering team free to do their best work? Read our new case study to learn how Blameless can help you do that.

3 tips for flexible, adaptive incident management

Aaron Lober

Incidents should be your best friend. It sounds like a controversial statement. It sounds like a lot of unnecessary work. The truth is, for companies engaged in delivering any online or digital experience, taking this point of view is absolutely E-S-S-E-N-T-I-A-L. Apart from the cost of an outage in production, unplanned work created by incidents will begin to hamper feature velocity if you don’t approach addressing them in the right way and there’s no faster way to damage your customer relationships than recurring product outages. 

Whether we like it or not, responding effectively to unexpected incidents is central to modern IT Operations. Having an integrated, evolving approach to managing incidents can unlock the agility and velocity of a DevOps team and can improve the overall quality of the software they’re developing. A rigid, dogmatic approach can leave that same team mired in tech debt and struggling to stay above water. 

The key is in viewing incidents as an opportunity to learn something new about your product and your process. If delivering a reliable product that customers will love is your goal, then how you build and operate the product is just as important as what you build. Having the right structure and process can help your engineering team stay aligned at scale. Good incident management practices can be a mechanism for interrogating the effectiveness of that structure.  That’s true for companies embracing ITIL, DevOps or SRE.

Developing a strong incident response process is key to minimizing downtime and learning from each incident. This takes time, practice and the right tooling. So to help you get started, we’ve got 3 tips for creating a more flexible, adaptive framework for incident management.

1. Where you manage incidents matters

There is no shortage of software solutions that claim to support incident management. That should be no surprise, managing incidents involves a complex set of tasks that include monitoring, alerting, and paging. However, to really be effective at managing incidents, a command center of sorts is needed to organize the people responsible for achieving resolution. There is no better place to locate that command center, than in the team's preferred chat bot. These offer unparalleled flexibility to recruit and coordinate the right experts. This is where targeted incident management solutions begin to separate themselves from more generic IT solutions like ITIL software.

“Incident Management solutions help DevOps or SRE teams create consistent incident workflows that map to their unique needs. Those workflows can then be easily activated within their chat system and can have wide cascading effects across multiple other systems once they’re activated” says Kurt Andersen, SRE architect at Blameless. 

“Having a well defined process is valuable, that’s why we built Blameless to guide teams through their incident response. Once the incident kicks off, everything needs to operate around or through the chatbot until the incident is resolved. That’s the best way to ensure good stakeholder visibility, performance tracking and limited toil.”

Incident management products like Blameless integrate with a wide array of supporting technologies beyond Slack or Microsoft Teams.  Allowing you to work within the chat app while sending and receiving data from products like PagerDuty, OpsGenie, StatusPage, Jira, or ServiceNow. Blameless helps centralize and stitch together all the moving parts of managing incidents and by collecting and surfacing critical data, everyone on your team is updated with a rich unique data.

2. Never forget “Communication is key”

“The worst case scenario for many SRE leaders is a large Sev0 incident with multiple customers impacted. CEO, VPs, and CS are all reporting customer issues and asking for status updates, while it looks like there are no engineers building or executing a plan to restore service. Then the scenario repeats the next day.” - Aaron Bento, Principal SRE for Arkose Labs

When an engineering incident is underway, ensuring stakeholder communication is the most important responsibility of an incident commander, next to resolving the incident itself. They can handle the communications themselves or delegate to a communications lead. This may sound simple but it’s anything but. Large organizations are likely to have a diverse set of stakeholders who need to be informed, not the least important of which are their customers.

“Having too many cooks in the kitchen can cripple your incident response. That’s why it's so important to communicate effectively, to the right stakeholders throughout the incident” says Vincent Rivellino, Head of Reliability and Developer Platforms at Mission Lane.

“Also, If customers are impacted there can be a serious hit to your company’s reputation. We lean into IM even for incidents where we’re not breaking technology SLAs. We often need swift incident resolution followed by coordinated execution of customer remediation. For us that often involves non-technical stakeholders who are communicating with our customers. At the end of the day, the most important thing is our customers know we have their back.” 

Whether managing internal stakeholder communications or communicating with customers, having clearly defined expectations for update cadences and automated reminders to follow up is really helpful. These are unique capabilities of modern incident management tools like Blameless that alternatives don’t provide. 

3. Treat incidents as opportunities

“The benefit of a more mature incident management process is identifying where the hot spots are in your product and where you as an engineering leader need to invest your team's engineering hours or budget”  

  • Elisa Binette, Director of Engineering and Site Reliability at VMWare. 

If your team is interested in driving development velocity, it’s not enough to try to eliminate toil from the incident response process. You need to go a step further and begin to leverage incidents proactively to identify points of weakness in your product and engineering process. This means running clear, effective retrospectives, tagging and capturing all the relevant incident data available and surfacing that back to the right stakeholders. Over time, this can help reduce the load on your entire team by making your process more efficient, your product more robust, and reducing the number of repeat incidents that your team has to manage.

“If you look at incidents as an opportunity to learn about what’s weak or broken in your product, and commit the right resources to addressing those weaknesses, you can quickly begin to reduce the number of repeat incidents your team encounters. Says Aaron Bento, Principal SRE for Arkose Labs, the global leader in bot mitigation. “Repeat incidents can be a killer for morale because they’re a sign that we’re not identifying the source of our problem. Taking a more proactive approach to incident management can really make a big difference.”

To maximize the value of the incident management process, your team needs opportunities to experiment, learn and iterate. With the right tooling and the right approach, you’ll soon be turning disruptive incidents into valuable insights. Incidents can be your best friend and Blameless is here to help.

For more information on IM best practice and to learn how Blameless is offering a modern approach to incident management, download the “Blameless Complete Guide To Incident Management” part 1.  Or sign up for a free trial of Blameless today.

Book a blameless demo
To view the calendar in full page view, click here.