Skip to main content

How to Prepare for Your Next Network War Room Debate - Part 2

Jay Botelho

Whether proactive or reactive in nature, war room sessions fundamentally come down to problem solving. But the ultimate goal is to eliminate these sessions altogether.

Start with How to Prepare for Your Next Network War Room Debate - Part 1

However, sometimes problems still happen no matter how proactive you are. If you have to go to the war room, and you want to win, here are some key tips:

Populate the room wisely and sparingly

The old adage about the bigger the group, the less work gets done certainly holds true for the war room. You want all critical functions represented, but with a single representative. If someone needs access to their teams for more details, they should report back, not drag more participants into the meetings.

Define roles and responsibilities

Clearly define roles and responsibilities for the war room. In most cases, the primary responsibility is to develop a comprehensive proposal to present to executive management. When done well, the execs shouldn't even need to participate. The right team should be able to deliver a rock-solid proposal, regardless of whether the driving force is project-focused or response-focused.

Bring data

Bring all the data you have and be prepared to share it. There are no secrets in the war room. All corporate politics must be put aside for a successful resolution. Remove blinders regarding available data. For example, when dealing with a security issue, don't forget to involve the network team. They often have critical data that's overlooked, at least in the beginning of the situational analysis.

Know the end game

Have an idea of the ultimate win-win outcome before you enter the war room. This is probably easier when the situation is project-focused vs. response-focused, but it's critical either way.

Involve PR experts

Involve PR experts for events that will impact the external perception of the brand. This is extremely important when dealing with response-focused issues, especially security breaches. External communication is a legal requirement for security breaches, and you need to get it right. It's the responsibility of the entire team to craft an accurate and complete response, but it's best for all communication to funnel through a single PR representative.

Plan to communicate only once

Analyze ALL the data and get the full extent of the problem isolated as early as possible. Communicate as clearly as you can. A great example of what not to do would be the Equifax breach, where the initial breach announcement was made approximately 6 weeks after discovery, with news of ever-greater exposure continuing to be reported by Equifax for more than 6 months.

War rooms can be intimidating places with lots of finger pointing, blame and chaos. For the network team, having the proper visibility tools in place is a win-win. First, it helps reduce these sessions, and second, if called in to answer the bell, it gives you the data needed to properly contribute and help solve the problem quickly. When the fingers start pointing, will you be ready?

Hot Topics

The Latest

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

How to Prepare for Your Next Network War Room Debate - Part 2

Jay Botelho

Whether proactive or reactive in nature, war room sessions fundamentally come down to problem solving. But the ultimate goal is to eliminate these sessions altogether.

Start with How to Prepare for Your Next Network War Room Debate - Part 1

However, sometimes problems still happen no matter how proactive you are. If you have to go to the war room, and you want to win, here are some key tips:

Populate the room wisely and sparingly

The old adage about the bigger the group, the less work gets done certainly holds true for the war room. You want all critical functions represented, but with a single representative. If someone needs access to their teams for more details, they should report back, not drag more participants into the meetings.

Define roles and responsibilities

Clearly define roles and responsibilities for the war room. In most cases, the primary responsibility is to develop a comprehensive proposal to present to executive management. When done well, the execs shouldn't even need to participate. The right team should be able to deliver a rock-solid proposal, regardless of whether the driving force is project-focused or response-focused.

Bring data

Bring all the data you have and be prepared to share it. There are no secrets in the war room. All corporate politics must be put aside for a successful resolution. Remove blinders regarding available data. For example, when dealing with a security issue, don't forget to involve the network team. They often have critical data that's overlooked, at least in the beginning of the situational analysis.

Know the end game

Have an idea of the ultimate win-win outcome before you enter the war room. This is probably easier when the situation is project-focused vs. response-focused, but it's critical either way.

Involve PR experts

Involve PR experts for events that will impact the external perception of the brand. This is extremely important when dealing with response-focused issues, especially security breaches. External communication is a legal requirement for security breaches, and you need to get it right. It's the responsibility of the entire team to craft an accurate and complete response, but it's best for all communication to funnel through a single PR representative.

Plan to communicate only once

Analyze ALL the data and get the full extent of the problem isolated as early as possible. Communicate as clearly as you can. A great example of what not to do would be the Equifax breach, where the initial breach announcement was made approximately 6 weeks after discovery, with news of ever-greater exposure continuing to be reported by Equifax for more than 6 months.

War rooms can be intimidating places with lots of finger pointing, blame and chaos. For the network team, having the proper visibility tools in place is a win-win. First, it helps reduce these sessions, and second, if called in to answer the bell, it gives you the data needed to properly contribute and help solve the problem quickly. When the fingers start pointing, will you be ready?

Hot Topics

The Latest

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.