3 Tips for Flexible, Adaptive Incident Management
November 07, 2022

Emily Arnott
Blameless

Share this

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.

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," says 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," says 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. "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.

Emily Arnott is Community Relations Manager at Blameless
Share this

The Latest

March 04, 2024

This year's Super Bowl drew in viewership of nearly 124 million viewers and made history as the most-watched live broadcast event since the 1969 moon landing. To support this spike in viewership, streaming companies like YouTube TV, Hulu and Paramount+ began preparing their IT infrastructure months in advance to ensure an exceptional viewer experience without outages or major interruptions. New Relic conducted a survey to understand the importance of a seamless viewing experience and the impact of outages during major streaming events such as the Super Bowl ...

March 01, 2024

As organizations continue to navigate the complexities of the digital era, which has been marked by exponential advancements in AI and technology, the strategic deployment of modern, practical applications has become indispensable for sustaining competitive advantage and realizing business goals. The Info-Tech Research Group report, Applications Priorities 2024, explores the following five initiatives for emerging and leading-edge technologies and practices that can enable IT and applications leaders to optimize their application portfolio and improve on capabilities needed to meet the ambitions of their organizations ...

February 29, 2024

Despite the growth in popularity of artificial intelligence (AI) and ML across a number of industries, there is still a huge amount of unrealized potential, with many businesses playing catch-up and still planning how ML solutions can best facilitate processes. Further progression could be limited without investment in specialized technical teams to drive development and integration ...

February 28, 2024

With over 200 streaming services to choose from, including multiple platforms featuring similar types of entertainment, users have little incentive to remain loyal to any given platform if it exhibits performance issues. Big names in streaming like Hulu, Amazon Prime and HBO Max invest thousands of hours into engineering observability and closed-loop monitoring to combat infrastructure and application issues, but smaller platforms struggle to remain competitive without access to the same resources ...

February 27, 2024

Generative AI has recently experienced unprecedented dramatic growth, making it one of the most exciting transformations the tech industry has seen in some time. However, this growth also poses a challenge for tech leaders who will be expected to deliver on the promise of new technology. In 2024, delivering tangible outcomes that meet the potential of AI, and setting up incubator projects for the future will be key tasks ...

February 26, 2024

SAP is a tool for automating business processes. Managing SAP solutions, especially with the shift to the cloud-based S/4HANA platform, can be intricate. To explore the concerns of SAP users during operational transformations and automation, a survey was conducted in mid-2023 by Digitate and Americas' SAP Users' Group ...

February 22, 2024

Some companies are just starting to dip their toes into developing AI capabilities, while (few) others can claim they have built a truly AI-first product. Regardless of where a company is on the AI journey, leaders must understand what it means to build every aspect of their product with AI in mind ...

February 21, 2024

Generative AI will usher in advantages within various industries. However, the technology is still nascent, and according to the recent Dynatrace survey there are many challenges and risks that organizations need to overcome to use this technology effectively ...

February 20, 2024

In today's digital era, monitoring and observability are indispensable in software and application development. Their efficacy lies in empowering developers to swiftly identify and address issues, enhance performance, and deliver flawless user experiences. Achieving these objectives requires meticulous planning, strategic implementation, and consistent ongoing maintenance. In this blog, we're sharing our five best practices to fortify your approach to application performance monitoring (APM) and observability ...

February 16, 2024

In MEAN TIME TO INSIGHT Episode 3, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at Enterprise Management Associates (EMA) discusses network security with Chris Steffen, VP of Research Covering Information Security, Risk, and Compliance Management at EMA ...