Skip to main content

How ITOps Can Adapt to the New Normal - Part 2

APMdigest posed the following question to the IT Operations community: How should ITOps adapt to the new normal? In response, industry experts offered their best recommendations for how ITOps can adapt to this new remote work environment. Part 2 covers communication and collaboration.

Start with: How ITOps Can Adapt to the New Normal - Part 1

VIRTUAL TEAM CULTURE

In order to adapt to the new normal, ITOps leaders should focus on fortifying a virtual team culture that fosters an environment for open communication. In a remote and digital world, it's imperative that teams communicate effectively.
Kalyan Ramanathan
VP of Product Marketing, Sumo Logic

ONLINE-FIRST CULTURE

Our office culture placed a high value on in-person interactions, so office budgets were targeting an inviting atmosphere. During the overnight change to work-from-home, we worried that we'd lose our office culture, so tried to adapt our in-person office culture to online forums. We held video conferences with an effort to create a facsimile experience — but it turns out it was not possible. The online experience works best where there is one voice at a time. We made a mistake in attempting to adapt our in-person office culture, and it's just not fully reproducible. This mistake led to trial and error, and we realized that we couldn't recapture what we had in-person, so instead had to create a new online-first culture. We are still working on this. So far we found ways to balance communication, using tools like company messaging apps and video conferencing. In ways, we now have better company-wide communication. The communication limit of one voice at a time allowed us to condense information into numerical goals, for instance we have breakout general gathering video conversations for general chats.
Stephen Blum
CTO and Co-Founder, PubNub

TEAM ALIGNMENT

In order to adapt to the new normal, ITOps and DevOps leaders should onboard a streamlined process that ensures team alignment.
Kalyan Ramanathan
VP of Product Marketing, Sumo Logic

SET NUMERIC GOALS

We found that focusing on communication using numeric goals and progress towards them helped. Numeric goals are easy to communicate visually (bar graphs) and explain in a short sentence.
Stephen Blum
CTO and Co-Founder, PubNub

PRIORITIZE AND DELEGATE

In order to adapt to the new normal, ITOps and DevOps leaders should learn how to prioritize and delegate correctly.
Kalyan Ramanathan
VP of Product Marketing, Sumo Logic

CROSS-ORGANIZATIONAL VISIBILITY

The need for cross-organizational visibility is more critical now than ever before. IT teams can often be siloed — and working from home can make that worse. To find gaps in IT operation hand-offs, track productivity (response to tickets, support workloads by operator, development release cycles, etc.) over time to see if there has been a major change (up or down) in workloads and engagement. Examine your teams' workflows and identify places where tools sprawl might be creating delays due to mental switching costs; streamline through integration and/or aggregating monitoring, change and topology data into a single pane of glass. IT Ops teams will have less competing noise, better understanding of the health of their IT Operations and the right tools to help them.
Assaf Resnick
CEO, BigPanda

ASYNCHRONOUS COMMUNICATION

Ever since the work-from-home mandates started, ad hoc conversations and resources that were already scattered are often going into a black hole. For many engineers, it's become overwhelming to keep up with all of the communications when working out of the office. To succeed from home, teams need to maintain real-time, aggregated communication streams.
Tina Huang
Founder and CTO, Transposit

High stakes and urgent (synchronous) communication are especially challenging during Covid. I vote that teams invest in automation and monitoring that enables employees to move fast — coordinating asynchronously and with guardrails built in — yet recover quickly when things go wrong.
Mohit Tiwari
CEO and Co-Founder, Symmetry Systems

MAINTAIN FEEDBACK LOOP

Knowing that feedback is a key element to the culture of your ITOps teams, it is critical to address the lack of in-person feedback in a remote culture. Creating several, smaller touch points is critical to keeping this feedback loop going without creating more arduous meetings.
Collin Mariner
Analyst, Gigaom

OFFICE HOURS

We have seen success by scheduling 30 minutes near the end of each day for what we call office hours. We publish our office hours to the entire organization and encourage anyone to join. This allows us to be available to the organization for asks that typically come in person, as well as receive more real-time feedback.
Collin Mariner
Analyst, Gigaom

MAKE A CONNECTION

The most prepared IT leaders will develop new programs for engaging staff that may feel disconnected.
Sean McDermott
CEO, Windward Consulting Group

Listen to the AI+ITOPS Podcast with special guest Sean McDermott

Read Windward Consulting's New Report: 2020 COVID-19 IT Economic Impact Study

COLLABORATION TOOLS

As remote work has become a mainstay of doing business, ITOps should work with their company's CTO and CSO to offer the right mix of collaboration tools for employees. Remote work will continue to add stress for employees, and it's the company's job to provide a framework of respect for the home situations of their employees and the tools/resources they need to be successful, such as video conferencing platforms, Google Drive, and notification systems. ITOps teams should regularly evaluate the performance of their organization's communication and collaboration tools to ensure employees can maintain their productivity levels while working remotely.
Marc Linster
CTO, EDB

Prior to the COVID-19 crisis, few enterprises had made the leap forward to remote working. When the pandemic hit, many companies transitioned to a fully remote work environment, accelerating the trend many years ahead in a matter of months. ITOps suddenly needed to fight an uphill battle, supporting a remote workforce of tens, hundreds, or even thousands of people. Setting up the proper infrastructure, in terms of tools and processes, is the number one priority, ensuring that in the short term the company survives and long term that it thrives. New tools must be procured, which inherently are built to support remote collaboration, particularly for mission critical roles such as SREs.
Odysseas Lamtzidis
Developer Relations, Netdata

Go to: How ITOps Can Adapt to the New Normal - Part 3

Hot Topics

The Latest

Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...

 

Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...

When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...

If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

How ITOps Can Adapt to the New Normal - Part 2

APMdigest posed the following question to the IT Operations community: How should ITOps adapt to the new normal? In response, industry experts offered their best recommendations for how ITOps can adapt to this new remote work environment. Part 2 covers communication and collaboration.

Start with: How ITOps Can Adapt to the New Normal - Part 1

VIRTUAL TEAM CULTURE

In order to adapt to the new normal, ITOps leaders should focus on fortifying a virtual team culture that fosters an environment for open communication. In a remote and digital world, it's imperative that teams communicate effectively.
Kalyan Ramanathan
VP of Product Marketing, Sumo Logic

ONLINE-FIRST CULTURE

Our office culture placed a high value on in-person interactions, so office budgets were targeting an inviting atmosphere. During the overnight change to work-from-home, we worried that we'd lose our office culture, so tried to adapt our in-person office culture to online forums. We held video conferences with an effort to create a facsimile experience — but it turns out it was not possible. The online experience works best where there is one voice at a time. We made a mistake in attempting to adapt our in-person office culture, and it's just not fully reproducible. This mistake led to trial and error, and we realized that we couldn't recapture what we had in-person, so instead had to create a new online-first culture. We are still working on this. So far we found ways to balance communication, using tools like company messaging apps and video conferencing. In ways, we now have better company-wide communication. The communication limit of one voice at a time allowed us to condense information into numerical goals, for instance we have breakout general gathering video conversations for general chats.
Stephen Blum
CTO and Co-Founder, PubNub

TEAM ALIGNMENT

In order to adapt to the new normal, ITOps and DevOps leaders should onboard a streamlined process that ensures team alignment.
Kalyan Ramanathan
VP of Product Marketing, Sumo Logic

SET NUMERIC GOALS

We found that focusing on communication using numeric goals and progress towards them helped. Numeric goals are easy to communicate visually (bar graphs) and explain in a short sentence.
Stephen Blum
CTO and Co-Founder, PubNub

PRIORITIZE AND DELEGATE

In order to adapt to the new normal, ITOps and DevOps leaders should learn how to prioritize and delegate correctly.
Kalyan Ramanathan
VP of Product Marketing, Sumo Logic

CROSS-ORGANIZATIONAL VISIBILITY

The need for cross-organizational visibility is more critical now than ever before. IT teams can often be siloed — and working from home can make that worse. To find gaps in IT operation hand-offs, track productivity (response to tickets, support workloads by operator, development release cycles, etc.) over time to see if there has been a major change (up or down) in workloads and engagement. Examine your teams' workflows and identify places where tools sprawl might be creating delays due to mental switching costs; streamline through integration and/or aggregating monitoring, change and topology data into a single pane of glass. IT Ops teams will have less competing noise, better understanding of the health of their IT Operations and the right tools to help them.
Assaf Resnick
CEO, BigPanda

ASYNCHRONOUS COMMUNICATION

Ever since the work-from-home mandates started, ad hoc conversations and resources that were already scattered are often going into a black hole. For many engineers, it's become overwhelming to keep up with all of the communications when working out of the office. To succeed from home, teams need to maintain real-time, aggregated communication streams.
Tina Huang
Founder and CTO, Transposit

High stakes and urgent (synchronous) communication are especially challenging during Covid. I vote that teams invest in automation and monitoring that enables employees to move fast — coordinating asynchronously and with guardrails built in — yet recover quickly when things go wrong.
Mohit Tiwari
CEO and Co-Founder, Symmetry Systems

MAINTAIN FEEDBACK LOOP

Knowing that feedback is a key element to the culture of your ITOps teams, it is critical to address the lack of in-person feedback in a remote culture. Creating several, smaller touch points is critical to keeping this feedback loop going without creating more arduous meetings.
Collin Mariner
Analyst, Gigaom

OFFICE HOURS

We have seen success by scheduling 30 minutes near the end of each day for what we call office hours. We publish our office hours to the entire organization and encourage anyone to join. This allows us to be available to the organization for asks that typically come in person, as well as receive more real-time feedback.
Collin Mariner
Analyst, Gigaom

MAKE A CONNECTION

The most prepared IT leaders will develop new programs for engaging staff that may feel disconnected.
Sean McDermott
CEO, Windward Consulting Group

Listen to the AI+ITOPS Podcast with special guest Sean McDermott

Read Windward Consulting's New Report: 2020 COVID-19 IT Economic Impact Study

COLLABORATION TOOLS

As remote work has become a mainstay of doing business, ITOps should work with their company's CTO and CSO to offer the right mix of collaboration tools for employees. Remote work will continue to add stress for employees, and it's the company's job to provide a framework of respect for the home situations of their employees and the tools/resources they need to be successful, such as video conferencing platforms, Google Drive, and notification systems. ITOps teams should regularly evaluate the performance of their organization's communication and collaboration tools to ensure employees can maintain their productivity levels while working remotely.
Marc Linster
CTO, EDB

Prior to the COVID-19 crisis, few enterprises had made the leap forward to remote working. When the pandemic hit, many companies transitioned to a fully remote work environment, accelerating the trend many years ahead in a matter of months. ITOps suddenly needed to fight an uphill battle, supporting a remote workforce of tens, hundreds, or even thousands of people. Setting up the proper infrastructure, in terms of tools and processes, is the number one priority, ensuring that in the short term the company survives and long term that it thrives. New tools must be procured, which inherently are built to support remote collaboration, particularly for mission critical roles such as SREs.
Odysseas Lamtzidis
Developer Relations, Netdata

Go to: How ITOps Can Adapt to the New Normal - Part 3

Hot Topics

The Latest

Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...

 

Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...

When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...

If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ...