DevOps for Crisis Communication: Five Steps to Prevent a Crisis from Becoming a Disaster
June 08, 2016

Jason Hand
VictorOps

According a recent IDC report, the average total cost of unplanned application downtime per year is between $1.25 billion to $2.5 billion, and the average hourly cost of an infrastructure failure is $100,000. What's more, a recent report by IHS about the cost of server, application and network downtime revealed that downtime is costing North American organizations $700 billion per year. We do everything we can to learn from these failures and improve our processes and tools along the way, but something many companies fail to address as a problem is often the most important: crisis communication.   

Using DevOps principles when dealing with incidents and outages can help organizations avoid common pitfalls many companies encounter when a disruption in service inevitably occurs. Here are five DevOps practices that can keep a crisis from getting worse:

1. Practice empathy

Empathy is at the heart of the DevOps movement. Unfortunately, it is one of the hardest practices to implement. The middle of a crisis is a difficult time to start working on this, but by thinking about how others might respond to news of an outage before an incident occurs, you can build a solid communication foundation with empathy as a building block.

2. Organize your information

During a crisis, every passing second is critical. Having helpful information organized and readily available can make a huge difference in not only repairing system issues, but communicating clearly with those who need to be "in the know." Step-by-step instructions and checklists known as runbooks will go a long way in quickly triaging issues and making sure all important items are addressed and in the correct order.

3. Be transparent

DevOps is all about collaboration, which translates to real-time team communication. Communication is even more important during a crisis, but communication is only useful if it is completely transparent and provides accurate and up-to-date information. Event timelines and "persistent group chat" tools should be leveraged for teams to discuss their findings and efforts, but it is equally important for organizations to display operational transparency to their end users.

4. Conduct post-mortems

In complex system environments, the only way to fully and accurately understand the details and contributing factors to a disruption in service is to retroactively analyze what took place during the disruption. As soon as stakeholders can be assembled, a post-incident analysis should take place to document, discuss, and understand the sequence of events and actions.

4. Learn from others

Outages happen all the time. The best and most respected companies realize that any attempt to hide or deny information about an issue can quickly become a blemish on the company's brand. The good news is that there is no need to reinvent the wheel. Instead, check out how other companies in similar industries deal with these same issues. For instance, customer-facing post-mortems are made public in a reasonably short amount of time to provide more transparency. Pick up best practices on how to address the problem from those who've done so successfully.

By keeping these tips in mind during your next crisis, not only can internal teams repair problems more quickly, but end users can be made aware of the situation in a timely manner that reinforces your position that satisfying the customer is priority number one. This demonstrates that you understand how much customers rely on and consider the availability of your service to be one of the core features you offer.

Jason Hand is a DevOps Evangelist at VictorOps.

The Latest

January 17, 2017

Blueprint predicts that application development will become more complex through 2017 as new processes and technologies change the way organizations develop products and engage with markets. As the volume and complexity of development projects grow, enterprises will continue to shift toward Agile and continuous delivery, and new technologies that enable collaboration between stakeholders will be essential. Here are Blueprint's top four predictions for enterprise software development in 2017 ...

January 13, 2017

What I think we will see in 2017, is an acceleration of the adoption of DevOps, especially within enterprises as the largest enterprise software companies continue developing their DevOps tool set ...

January 11, 2017

If there's any consistent criticism that's been leveled at the DevOps movement, it's that the term comprises such a wide range of concepts to so many different people, and that it's become more closely associated with marketing than real-world adoption. So how do you overcome such critiques? Obviously the onus is upon those of us working in the space — especially on the provider side — to put a finer point on what DevOps (currently) encompasses in a practical sense. A big part of this must be found in highlighting those real-world use cases where DevOps is having the most significant impact ...

January 09, 2017

The following are 2017 predictions for DevOps from the executive team at XebiaLabs, covering Analytics, Monitoring, Big Data, Serverless, Container Orchestration and more ...

January 06, 2017

The following are 2017 predictions for DevOps from the executive team at Electric Cloud, covering Application Release Automation, Microservices and Containers, Continuous Testing, Secure DevOps and more ...

January 04, 2017

The rapid expansion of production container deployment in enterprises worldwide has led to a movement toward containers-as-a-service (CaaS) over traditional Platform as a Service (PaaS) solutions. Advances in container management tooling are leading operations to embrace CaaS as a solution to enable developers to containerize their legacy applications and then build microservices around them. This trend will rise rapidly in 2017, driven by increased collaboration across IT disciplines and enthusiasm surrounding containerization even at the board level ...

December 30, 2016

A lot of time, resources and energy has been invested over the past few years on de-siloing development and operations. And with good reason. DevOps is enabling organizations to more aggressively increase their digital agility, while at the same time reducing digital costs and risks. But as 2017 approaches, the hottest trends in DevOps aren’t specifically about dev or ops. They’re about testing, security, and metrics ...

December 27, 2016

The advent of the Holiday Season means it is time for the annual list of Application Performance Management (APM) predictions, the most popular post on APMdigest, viewed by tens of thousands of people in the IT community around the world every year. Industry experts offer predictions on how APM and related technologies will evolve and impact business in 2017. A forecast by the top minds in Application Performance Management today, here are the predictions ...

December 19, 2016

DevOps experts — analysts and consultants, users and the top vendors — offer thoughtful, insightful, often controversial and sometimes contradictory predictions on how DevOps and related technologies will evolve and impact business in 2017. Part 6, the final installment, covers DevOps tools and DevOps people ...

December 16, 2016

DevOps experts — analysts and consultants, users and the top vendors — offer thoughtful, insightful, often controversial and sometimes contradictory predictions on how DevOps and related technologies will evolve and impact business in 2017. Part 5 covers the many facets of DevOps including analytics, security, collaboration and more ...

Share this