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
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.
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
Achieving audit compliance within your IT ecosystem can be an iterative process, and it doesn't have to be compressed into the five days before the audit is due. Following is a four-step process I use to guide clients through the process of preparing for and successfully completing IT audits ...
Network performance issues come in all shapes and sizes, and can require vast amounts of time and resources to solve. Here are three examples of painful network performance issues you're likely to encounter this year, and how NPMD solutions can help you overcome them ...
"Scale up" versus "scale out" doesn't just apply to hardware investments, it also has an impact on product features. "Scale up" promotes buying the feature set you think you need now, then adding "feature modules" and licenses as you discover additional feature requirements are needed. Often as networks grow in size they also grow in complexity ...
Network Packet Brokers play a critical role in gaining visibility into new complex networks. They deliver the packet data and information IT and security teams need to identify problems, recognize security issues, and ensure overall network performance. However, not all Packet Brokers are created equal when it comes to scalability. Simply "scaling up" your network infrastructure at every growth point is a more complex and more expensive endeavor over time. Let's explore three ways the "scale up" approach to infrastructure growth impedes NetOps and security professionals (and the business as a whole) ...
Loyal users are the key to your service desk's success. Happy users want to use your services and they recommend your services in the organization. It takes time and effort to exceed user expectations, but doing so means keeping the promises we make to our users and being careful not to do too much without careful consideration for what's best for the organization and users ...
What's the difference between user satisfaction and user loyalty? How can you measure whether your users are satisfied and will keep buying from you? How much effort should you make to offer your users the ultimate experience? If you're a service provider, what matters in the end is whether users will keep coming back to you and will stay loyal ...
What if I said that a 95% reduction in the amount of IT noise, 99% reduction in ticket volume and 99% L1 resolution rate are not only possible, but that some of the largest, most complex enterprises in the world see these metrics in their environments every day, thanks to Artificial Intelligence (AI) and Machine Learning (ML)? Would you dismiss that as belonging to the realm of science fiction? ...
Of those surveyed, 96% of organizations have a digital transformation strategy, with 57% approaching it as an enterprise-wide priority, with a clear emphasis on speed of business, costs, risk, and customer satisfaction, according to IDC’s Aligning IT Strategies and Business Expectations for Digital Transformation Success, sponsored by EasyVista ...
One of my ongoing areas of focus is analytics, AIOps, and the intersection with AI and machine learning more broadly. Within this space, sad to say, semantic confusion surrounding just what these terms mean echoes the confusions surrounding ITSM ...