Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

A Coordinated Response Culture for Incident Management

DZone's Guide to

A Coordinated Response Culture for Incident Management

An organizational culture that prioritizes coordinated response to incidents is vital for monitoring and managing an IT infrastructure. Incident management won’t go smoothly if teams don’t want to or know how to coordinate their response to alerts.

· DevOps Zone
Free Resource

Download the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.

An organizational culture that prioritizes coordinated response to incidents is vital for monitoring and managing an IT infrastructure. Incident management won’t go smoothly if teams don’t want to or know how to coordinate their response to alerts.

What Is a Coordinated Response?

To break it down simply, a coordinated response in the IT world generally involves notifying the right people and mobilizing teams immediately, providing access to contextual information for seamless alignment, and getting the team onto the right conference bridge or communication channel of choice. A well-coordinated response enables organizations to jump in and resolve incidents quickly and efficiently.

Let’s take a look at some of the challenges to response coordination, then examine strategies and tools that allow organizations to overcome these challenges and optimize incident management.

Coordination Challenges

A coordinated response culture rarely breeds itself within an organization. By default, there are obstacles in place that make coordinated response difficult. The biggest challenges include:

  • RECRUITMENT: The difficulty of recruiting additional people to help manage an incident. This challenge arises when you need to bring others in to help put out a fire, but the additional people you need didn’t receive the original alert. Unless you have an incident management platform like PagerDuty, there is no efficient way to request help from others when an incident occurs. You could email or call, of course, and hope the people respond quickly, but emails and calls are not always the fastest way to get in touch or the best way to get someone’s attention quickly, especially outside of normal business hours
  • COMMUNICATION: Too many communication channels give too many options. Multiple communication channels are available for incident management, from email to video chats to Slack. Depending on the type of incident at hand, one channel may make more sense than another. What you don’t want to do is waste time in the midst of an incident figuring out which channel to use and making sure all your team members are on it.
  • TOOLS: Most organizations have some mode of coordination and collaboration. To create an effective coordination culture, it’s best to work with the tools already on hand, and integrating them with a central incident management platform.

Increasing Coordination

Fortunately, these challenges can be solved easily enough by taking advantage of the features very recently released in PagerDuty. With Response Mobilizer and Response Bridge organizations can:

  • RECRUIT: Recruit additional teammates to help solve a particular incident. The best way to do this is to build the recruitment of additional help into your incident management workflow. That’s better than relying on manual, ad-hoc ways of asking for help in the midst of an incident, and you’ll know you have the experts you need there to help you.
  • COMMUNICATE: Integrate existing and most preferred communication tools with your incident management workflow; whether it be email, SMS, Slack, existing conference bridge from WEBEX, GoToMeeting or Skype. Trying to impose a new communication tool on the team will often disrupt the established workflow and incur resistance from staff. The better approach is to integrate your existing communication tools into your incident management solution.
  • HAVE CONTEXT: Include right contextual information to address business-critical issues in real-time. Providing rich contextual information about the incident and including a brief message to responders detailing why they are needed enables responders to prepare and immediately be aligned.

If you’re seeking to build a better-coordinated response culture for incident management within your organization, take advantage of the new features to make the most of the collaboration and coordination resources available to you, without forcing your team to overhaul its communication workflow.

Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.

Topics:
conference ,workflow ,solution ,incident management ,management ,response ,culture ,platform

Published at DZone with permission of Christopher Tozzi, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}