Skip to main content

Major Incident Management: Are You Prepared?

Troy McAlpin

If your critical business applications go down, or even run below peak level, your business pays a tremendous price. When a major IT incident occurs, engaging the right people quickly to restore service and manage communications is crucial. No big news flash there. However I have to admit I was pretty alarmed when a new survey by Dimensional Research revealed an almost cavalier approach toward the handling of major IT incidents. Security and business incidents occur so regularly that we aren't even surprised anymore when they happen. They come in the form of data breaches, malware attacks, power outages, intermittent service availability and performance degradation to name a few. Click here to see infographic below In fact, according to the survey, 68 percent of companies surveyed experienced a major incident at least several times a year. For larger organizations with at least 5,000 employees, that figure rises to more than 90 percent.

The Consequences of Slow Response

Rapid, effective response can limit the damage. In a separate survey performed by Dimensional Research in April, 60 percent said finding and engaging the right person takes more than 15 minutes. But before 15 minutes have elapsed, almost half (45 percent) said the business has already started to suffer. And the suffering is real, according to the most recent survey. A large majority (82 percent) says application downtime affects revenue. According to a 2014 study by industry analyst firm IDC, the average cost of a critical application failure per hour is $500,000 to $1 million. Given how quickly, seriously and frequently a major incident affects businesses, why aren't they making critical investments in major incident management?

Money and Resources

First, a best-in-class intelligent communication platform is not cheap. So organizations that still view major incidents as unlikely events could be put off just by the cost. Another factor is resources. Barely half of companies in the new survey (52 percent) have a major incident team. Only 44 percent of those companies have team members who are dedicated solely to major incident management. Finally, maybe the word hasn't gotten out to all companies just how important rapid and effective major incident management is.

Is the Status Quo Working?

The effectiveness of current practices is not entirely clear because only 68 percent of companies even specify target times for resolving major incidents. But among those that are, the results are not good. More than three-quarters of respondents, 76 percent, miss their target times sometimes or often. Most companies in the survey (58 percent) have target times between 30-90 minutes. Remember the IDC figure of up to $1 million per hour of application downtime? Do the math.

So What Have We Learned?

Regardless of why more companies haven't created processes and implemented solutions for resolving major incidents, the current state of affairs is troubling. And this article has only touched on the financial implications of major incidents. Business also suffer from reputational damage, loss of customer loyalty and trust, and sanctions from regulatory bodies. Major incidents happen frequently, and every business should assume that sooner or later it will experience one. The ability to quickly, efficiently and effectively respond could save the business, its shareholders, its customers and partners. Are you prepared?
 

The Latest

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

Major Incident Management: Are You Prepared?

Troy McAlpin

If your critical business applications go down, or even run below peak level, your business pays a tremendous price. When a major IT incident occurs, engaging the right people quickly to restore service and manage communications is crucial. No big news flash there. However I have to admit I was pretty alarmed when a new survey by Dimensional Research revealed an almost cavalier approach toward the handling of major IT incidents. Security and business incidents occur so regularly that we aren't even surprised anymore when they happen. They come in the form of data breaches, malware attacks, power outages, intermittent service availability and performance degradation to name a few. Click here to see infographic below In fact, according to the survey, 68 percent of companies surveyed experienced a major incident at least several times a year. For larger organizations with at least 5,000 employees, that figure rises to more than 90 percent.

The Consequences of Slow Response

Rapid, effective response can limit the damage. In a separate survey performed by Dimensional Research in April, 60 percent said finding and engaging the right person takes more than 15 minutes. But before 15 minutes have elapsed, almost half (45 percent) said the business has already started to suffer. And the suffering is real, according to the most recent survey. A large majority (82 percent) says application downtime affects revenue. According to a 2014 study by industry analyst firm IDC, the average cost of a critical application failure per hour is $500,000 to $1 million. Given how quickly, seriously and frequently a major incident affects businesses, why aren't they making critical investments in major incident management?

Money and Resources

First, a best-in-class intelligent communication platform is not cheap. So organizations that still view major incidents as unlikely events could be put off just by the cost. Another factor is resources. Barely half of companies in the new survey (52 percent) have a major incident team. Only 44 percent of those companies have team members who are dedicated solely to major incident management. Finally, maybe the word hasn't gotten out to all companies just how important rapid and effective major incident management is.

Is the Status Quo Working?

The effectiveness of current practices is not entirely clear because only 68 percent of companies even specify target times for resolving major incidents. But among those that are, the results are not good. More than three-quarters of respondents, 76 percent, miss their target times sometimes or often. Most companies in the survey (58 percent) have target times between 30-90 minutes. Remember the IDC figure of up to $1 million per hour of application downtime? Do the math.

So What Have We Learned?

Regardless of why more companies haven't created processes and implemented solutions for resolving major incidents, the current state of affairs is troubling. And this article has only touched on the financial implications of major incidents. Business also suffer from reputational damage, loss of customer loyalty and trust, and sanctions from regulatory bodies. Major incidents happen frequently, and every business should assume that sooner or later it will experience one. The ability to quickly, efficiently and effectively respond could save the business, its shareholders, its customers and partners. Are you prepared?
 

The Latest

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...