Incident management: Communication best practices

Share on linkedin
Share on facebook
Share on twitter
IT Asset Security: Major incident effects are visible as operational impacts but lasting impacts are the company’s reputation with stakeholder and customers.

Major incidents are a normal part of business, particularly for companies with a large dependency on technology and data.

When major incidents happen, business processes, the ability to deliver products and services to customers and/or the ability to ensure the security and integrity of company data are often compromised.

The effects of major incidents may be most immediately visible in the form of operational impacts, but the big and lasting impacts are your company’s reputation with shareholders, regulators and customers.

Managing reputational impact effectively must be a central goal of a company’s major incident management processes. Studies have shown that the perception of how you manage a major incident is often more meaningful to stakeholders than the technical details of the incident itself.

This is good for incident managers because perception is entirely within their control.

Why stakeholder communications are important

The reason you must be diligent and deliberate about your stakeholder communications during a major incident is because you are controlling the narrative and version of events to which people can respond.

Virima will help your incident responders identify the stakeholders who must be engaged and how to communicate, so the interactions can be direct and consistent and will develop stakeholder trust.

Without clear and organized stakeholder communications, everyone will seek his or her own version of the facts, develop opinions on the impacts/implications of the event and spin the narrative based on his or her perspective and biases. This can be dangerous because you have little if any control of the perceptions of the incident and how it is managed.

Communication plan

An effective stakeholder communication strategy is intended to guide perception by:

  1. Invoking a calm response to the situation — balancing a healthy sense of importance and urgency with a sense of controlled restraint.
  2. Instilling confidence in the team working on the issue that they know what they are doing and have control of the situation.
  3. Developing a common understanding of the technical issues and business impact of the situation to support thoughtful decision-making about actions that may need to be taken.

High quality major incident communication

To achieve these objectives and manage perceptions effectively, stakeholder communications must be targeted to the right audience, include the right amount of information, and communicate the impact and technical details of the situation in a way that allows recipients to understand what is occurring without being overwhelmed or mired in details.

They must also be able to trust the information they are receiving is complete, current and accurate — avoiding the need to search for supplemental information from other sources. How information is presented influences quality factors more than the content itself.

Using visualizations in stakeholder communications

As the saying goes, a picture is worth 1,000 words. When a major incident is occurring, there is often much context that must be conveyed and complexity that must be separated, so stakeholders are able to focus their attention on the pieces of the situation that actually matter.

Visualizations can help. IT systems operate within the context of business processes, physical locations and dependency chains that are often difficult to depict in words, but with the right picture, stakeholders can easily understand where the problem is and how it impacts them.

Visualization and mapping capabilities like those found in Virima can depict the impacts of a major incident visually and be explained with simple business terms. This is what is broken. These connect to it. These are the business processes, operations or locations which use those components, systems, processes, etc. to complete the job.

Incident mitigation with visualizations

Mitigation steps can similarly be explained using visualizations. We are redirecting the connections to provide partial service to users while we fix what is broken or we will deploy these network security guard capabilities around the edge of the environment to stop the attackers from entering from the outside. The words may be overly simple , but they can be simple because the picture is telling the rest of the story.

Stakeholder communications are your primary control points when a major incident occurs. They create the common narrative and guide stakeholder perceptions about how well the incident is being managed and whether stakeholders must be alarmed.

With visualization capabilities from Virima, you can transform your operational data into pictures of the incident with the right shapes and colors, so your explanations are direct, concise and impactful.

Virima is here to help. To get started, contact us today to schedule a demo and explore the possibilities!

Share on linkedin
Share on facebook
Share on twitter

Subscribe to Our Newsletter

More to Explore

IT Operations Management (ITOM) refers to the administration of technology and application requirements within an IT organization. Under the ITIL framework, ITOM’s objective is to monitor, control, and execute the routine tasks necessary to support an organization’s IT infrastructure.(Also, see…

CMDB service maps are visual depictions of hierarchical relationships among business services (sometimes also major applications) and their supporting Configuration Items (CIs). Because service maps can provide an instant bird’s eye view of critical dependencies and relationships, their utility lies…

Understanding the Configuration Management Database (CMDB) and its core functions is a critical aspect of service management. The CMDB forms the hub of numerous service management practices and provides a means of correlation needed to deliver business services successfully.   The…

Introduction  IT asset management (ITAM) and inventory management are both useful practices that can benefit any organization using IT. Both of these practices are concerned with the management of IT assets but focus on different things. Inventory management can exist…

IT asset management (ITAM) and configuration management are both useful practices that can benefit any organization using IT. Both of these practices are concerned with the management of IT assets, but focus on different things.Configuration management can exist without IT…

Some people think that an IT service desk is the same thing as an IT help desk. It isn't, as I'm going to explain. Sure, there are some similarities, but there are also many differences. Let's start by exploring what…

To understand the business value of service mapping, it’s important to shift to a service delivery mindset, rather than thinking about delivering infrastructure, equipment, software, and applications. Defining services is relatively simple if thought of as the commoditization of what’s…

Business service mapping – the area of configuration management that perplexes so many IT professionals, yet that which provides the highest value in configuration management database (CMDB) projects. There are several major reasons IT gets stopped when it comes to…

The world of ITSM has changed as technology has shifted from providing tools for administrative support to being fully embedded in the delivery of the business’ core function.  There’s a world of difference between using an accounts payable system to…

The Configuration Management Database (CMDB) provides a single database that contains information about the enterprise’s assets, both logical and physical. In modern service management platforms, it provides core functionality that is referenced by all of the service management practices, including…