Skip to main content

Opening the Gates to the Digital War Room - What is it Now, and What is it Likely to Become?

Dennis Drogseth

EMA has just completed research titled, Unifying IT for Digital War Room Performance. The research was partly inspired by current debates about the role of the "War Room" and how it is or is not evolving. Some seem lost in fantasy — "the war room will absolutely disappear." Whereas for others, basic incident handling is just emerging and having a more defined and effective war room team remains a hope for the distant future.

The Industry Debate

As with so much in our industry, a lot of this debate depends on meaning and definition — or in this case how you do or don't define "war room." War rooms are often defined as disastrous assemblages of finger-pointing adults caught up with siloed versions of "the truth" — all at least as interested in proving that their teams are not guilty, as they are in actually solving the problem at hand.

Our goal was to find out how teams are being formed and optimized to handle major incidents and problems that require cross-domain insights

However, for our research we took a much more open-ended approach. Our goal was to find out how teams are being formed and optimized to handle major incidents and problems that require cross-domain insights. This included, by the way, proactive cross-domain teams for managing issues before they become the IT equivalent of life-threatening. Our war rooms could be either physical or virtual. Highly automated or not. Made up of consistent, well-defined teams, or not. But what made them war rooms was the need for collaborative decision making across silos, and the need for urgency in taking effective action.

War Room Processes

Throughout the research, EMA examined the most critical processes logically relevant to war room performance. These included:

Initial awareness — alerting the relevant stakeholders that something is, or about to be, a problem

Response team engagement — making sure relevant stakeholders have an informed context for working together to resolve the problem

Triage and diagnostics — finding out what's really wrong in clear service-impact context

Remediation — actually fixing problem, ideally with inbuilt levels of automation to support the fix

Validation — ensuring that the "fix" really is a fix

Ideally, also, a history has been kept so that IT can move to prevent the problem in the future, or at least bring it to ever speedier resolution. We asked respondents about this in the context of auditing war room performance.

The War Room's Multiple Dimensions

We also looked at cloud to see if public and private cloud initiatives were making things easier or harder in the war room and why. (What we saw is a little bit of both.)

And then there's DevOps and agile. One of the industry hallucinations seems to be that DevOps and agile are making the war room disappear. What we found is just the opposite in the vast majority of cases (well over 80%). We looked, as well, at how development is working as an integrated part of the digital war room phenomenon, and the impact of in-house applications on war room processes.

And then of course there's security. Or maybe security should come first. In fact, security incident and event management (SIEM) was right at the top of digital war room technology priorities along with advanced IT analytics. The growing need to handshake between operations, security and ITSM teams in the digital war room was evident throughout our data.

Looking at all of the above, you might say that incidents and problems are increasingly non-denominational in how they occur. In other words, digital war rooms are no longer (if they ever were) just about operations in a vacuum.

Technologies, Metrics and Success

As mentioned above, analytics and security were the big winners when we looked at digital war room technology priorities. In fact, the top-ranking five were:

1. Advanced IT analytics or AIOps

2. SIEM

3. Security threat intelligence analysis

4. Endpoint instrumentation and analytics

5. IT process automation

The top two technical metrics were performance latencies and end user experience management.

And the top three obstacles to digital war room success were security-related issues, inconsistent data, and data fragmentation.

In Summary

Overall, we saw that the digital war room is becoming more not less important, growing in size, becoming more proactive and fundamentally more strategic.

To get a lot more insight, please watch my on-demand EMA webinar.

Read my next blog, Organization and Process (Or Lack Thereof) in the Digital War Room

The Latest

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Opening the Gates to the Digital War Room - What is it Now, and What is it Likely to Become?

Dennis Drogseth

EMA has just completed research titled, Unifying IT for Digital War Room Performance. The research was partly inspired by current debates about the role of the "War Room" and how it is or is not evolving. Some seem lost in fantasy — "the war room will absolutely disappear." Whereas for others, basic incident handling is just emerging and having a more defined and effective war room team remains a hope for the distant future.

The Industry Debate

As with so much in our industry, a lot of this debate depends on meaning and definition — or in this case how you do or don't define "war room." War rooms are often defined as disastrous assemblages of finger-pointing adults caught up with siloed versions of "the truth" — all at least as interested in proving that their teams are not guilty, as they are in actually solving the problem at hand.

Our goal was to find out how teams are being formed and optimized to handle major incidents and problems that require cross-domain insights

However, for our research we took a much more open-ended approach. Our goal was to find out how teams are being formed and optimized to handle major incidents and problems that require cross-domain insights. This included, by the way, proactive cross-domain teams for managing issues before they become the IT equivalent of life-threatening. Our war rooms could be either physical or virtual. Highly automated or not. Made up of consistent, well-defined teams, or not. But what made them war rooms was the need for collaborative decision making across silos, and the need for urgency in taking effective action.

War Room Processes

Throughout the research, EMA examined the most critical processes logically relevant to war room performance. These included:

Initial awareness — alerting the relevant stakeholders that something is, or about to be, a problem

Response team engagement — making sure relevant stakeholders have an informed context for working together to resolve the problem

Triage and diagnostics — finding out what's really wrong in clear service-impact context

Remediation — actually fixing problem, ideally with inbuilt levels of automation to support the fix

Validation — ensuring that the "fix" really is a fix

Ideally, also, a history has been kept so that IT can move to prevent the problem in the future, or at least bring it to ever speedier resolution. We asked respondents about this in the context of auditing war room performance.

The War Room's Multiple Dimensions

We also looked at cloud to see if public and private cloud initiatives were making things easier or harder in the war room and why. (What we saw is a little bit of both.)

And then there's DevOps and agile. One of the industry hallucinations seems to be that DevOps and agile are making the war room disappear. What we found is just the opposite in the vast majority of cases (well over 80%). We looked, as well, at how development is working as an integrated part of the digital war room phenomenon, and the impact of in-house applications on war room processes.

And then of course there's security. Or maybe security should come first. In fact, security incident and event management (SIEM) was right at the top of digital war room technology priorities along with advanced IT analytics. The growing need to handshake between operations, security and ITSM teams in the digital war room was evident throughout our data.

Looking at all of the above, you might say that incidents and problems are increasingly non-denominational in how they occur. In other words, digital war rooms are no longer (if they ever were) just about operations in a vacuum.

Technologies, Metrics and Success

As mentioned above, analytics and security were the big winners when we looked at digital war room technology priorities. In fact, the top-ranking five were:

1. Advanced IT analytics or AIOps

2. SIEM

3. Security threat intelligence analysis

4. Endpoint instrumentation and analytics

5. IT process automation

The top two technical metrics were performance latencies and end user experience management.

And the top three obstacles to digital war room success were security-related issues, inconsistent data, and data fragmentation.

In Summary

Overall, we saw that the digital war room is becoming more not less important, growing in size, becoming more proactive and fundamentally more strategic.

To get a lot more insight, please watch my on-demand EMA webinar.

Read my next blog, Organization and Process (Or Lack Thereof) in the Digital War Room

The Latest

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...