Skip to main content

What it Takes for Today's Organizations to Achieve Operational Resilience

Sean Sebring
SolarWinds

Over the past year, I spent a good amount of time thinking about operational resilience. I asked myself what does it mean? Why is it so important, especially now?

My colleagues and I define operational resilience as the ability to identify, anticipate, and mitigate risks to help prevent future issues while accelerating responsiveness to ongoing disruptions when they do occur. It is achieved by understanding the different parts of the business and how they interact across teams, workflows, and tools, while driving a culture of intentional learning and adaptation.

Adequately preventing and responding to disruptions has never been more important — or more possible. The growing ubiquity of AI has introduced more automated workstreams and increased productivity, while simultaneously creating a greater need for better data management. As customer expectations increasingly align with always-on services, the ability to prevent and recover from disruptions has direct ties to a business's bottom line.

Recent data from the SolarWinds IT Trends Report 2025, which surveyed more than 600 IT leaders and professionals, suggests nine in 10 IT teams believe they're resilient. However, a closer inspection of the data indicates a more complex reality. Many organizations still have room to improve their operational reliance and prepare for an AI-driven, data-intensive future.

The Complex Reality of Today's IT Teams

While these organizations consider themselves resilient, survey respondents pointed to a lack of confidence in their ability to handle certain core IT functions. For example, only 26% of IT leaders were confident they could sufficiently handle bring-your-own-device practices. Less than half of IT leaders felt confident they could manage increasing user expectations (36%), support artificial intelligence (38%), and manage remote and distributed workforces (45%). A little more than half, 52%, felt they could sufficiently deal with cyberthreats.

An operationally resilient organization must be able to handle these functions. For example, if employees or third-party contractors are bringing their own devices onto your network, your IT systems will require proper security policies to help ensure those parties aren't introducing malicious content or data into your network. If today's organizations aren't able to adequately implement and support the use of AI, they run the risks of shadow AI use or experiencing competitive disadvantages in their respective markets.  

Speaking of competitive disadvantages, the report also highlighted how sub-par operational resilience can lead to reputational harm. More than one quarter (28%) of IT leaders said service outages can cause brand damage. A hit to public image can have cascading effects, causing consumers to take their business elsewhere and leading to both short-term and long-term revenue loss.

Why Organizations Are Facing Gaps in Their IT Operations

When facing issues with an IT environment, the most natural — and even logical — step is to expand IT capabilities. However, IT leaders in the report said their issues weren't solely technology-based. In fact, for some teams, tools are the least important issue. More IT leaders cited workflows (51%) and the size of their teams (36%) as the biggest hindrances to exercising operational resilience during disruption. This is a great reminder that, although a system disruption may begin as a technology issue, the resilience necessary to respond is neither technology-only nor technology-first.

Organizations face an inability to measure operational resilience as well as the additional challenge of practicing operational resilience. According to the survey, 3 in 10 IT teams spend half their time resolving critical issues. The only way to reduce these numbers is to know how long it takes to reach resolution and recover after an incident occurs.

Many teams view incident management and response times as a great way to measure IT performance. This often translates to use of the MTTx metric, also known as mean time to detect, mean time to acknowledge and or mean time to resolve.

Almost half of the respondents (45%) said they didn't use MTTx for multiple reasons, such as a lack of awareness, difficulty measuring accurately, or a preference for alternative metrics. Regardless, sufficient and prompt MTTx is a strong measure for operational resilience.

Improving Operational Resilience

To take operational resilience from insufficient to excellent, organizations must build their IT frameworks on solid relationships, streamlined processes, and comprehensive tooling.

A focus on relationships should extend to both technology and teams. IT leaders can look to comprehensive observability software to view how each IT asset, piece of data, and login credentials relate to each other. This help leaders create a map to describe the causes and effects within a system if a disruption occurs. Similar to tooling, it's also important to map relationships between team members. When you understand the relationships between team and technology, you can discern which assets and workflows are most important and which require the highest priority.

Once you outline relationships, you can begin delving into processes. A good way to figure out what's working and what isn't, is by surveying IT team members. They can best describe areas with communication problems, antithetical working styles, or a lack of necessary expertise. You may find you need to move team members around or decide that teamwork is great but could benefit from better tooling.

If tooling is part of the solution, it's important to meet with leadership to implement technology that is helpful, addresses team needs, and aligns with business goals. For example, if you have an IT team that has historically suffered from alert fatigue and disjointed incident management, the team may benefit from tooling that centralizes incident response and helps isolate and identify the most critical issues. This creates focus and streamlined processes that can enhance teamwide operational resilience.

When organizations can improve their tools, teams and processes, they can create a culture of operational resilience that breaks down silos and efficiently responds in the face of disruption. 

Sean Sebring is Solutions Engineering Manager at SolarWinds

Hot Topics

The Latest

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

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 ...

What it Takes for Today's Organizations to Achieve Operational Resilience

Sean Sebring
SolarWinds

Over the past year, I spent a good amount of time thinking about operational resilience. I asked myself what does it mean? Why is it so important, especially now?

My colleagues and I define operational resilience as the ability to identify, anticipate, and mitigate risks to help prevent future issues while accelerating responsiveness to ongoing disruptions when they do occur. It is achieved by understanding the different parts of the business and how they interact across teams, workflows, and tools, while driving a culture of intentional learning and adaptation.

Adequately preventing and responding to disruptions has never been more important — or more possible. The growing ubiquity of AI has introduced more automated workstreams and increased productivity, while simultaneously creating a greater need for better data management. As customer expectations increasingly align with always-on services, the ability to prevent and recover from disruptions has direct ties to a business's bottom line.

Recent data from the SolarWinds IT Trends Report 2025, which surveyed more than 600 IT leaders and professionals, suggests nine in 10 IT teams believe they're resilient. However, a closer inspection of the data indicates a more complex reality. Many organizations still have room to improve their operational reliance and prepare for an AI-driven, data-intensive future.

The Complex Reality of Today's IT Teams

While these organizations consider themselves resilient, survey respondents pointed to a lack of confidence in their ability to handle certain core IT functions. For example, only 26% of IT leaders were confident they could sufficiently handle bring-your-own-device practices. Less than half of IT leaders felt confident they could manage increasing user expectations (36%), support artificial intelligence (38%), and manage remote and distributed workforces (45%). A little more than half, 52%, felt they could sufficiently deal with cyberthreats.

An operationally resilient organization must be able to handle these functions. For example, if employees or third-party contractors are bringing their own devices onto your network, your IT systems will require proper security policies to help ensure those parties aren't introducing malicious content or data into your network. If today's organizations aren't able to adequately implement and support the use of AI, they run the risks of shadow AI use or experiencing competitive disadvantages in their respective markets.  

Speaking of competitive disadvantages, the report also highlighted how sub-par operational resilience can lead to reputational harm. More than one quarter (28%) of IT leaders said service outages can cause brand damage. A hit to public image can have cascading effects, causing consumers to take their business elsewhere and leading to both short-term and long-term revenue loss.

Why Organizations Are Facing Gaps in Their IT Operations

When facing issues with an IT environment, the most natural — and even logical — step is to expand IT capabilities. However, IT leaders in the report said their issues weren't solely technology-based. In fact, for some teams, tools are the least important issue. More IT leaders cited workflows (51%) and the size of their teams (36%) as the biggest hindrances to exercising operational resilience during disruption. This is a great reminder that, although a system disruption may begin as a technology issue, the resilience necessary to respond is neither technology-only nor technology-first.

Organizations face an inability to measure operational resilience as well as the additional challenge of practicing operational resilience. According to the survey, 3 in 10 IT teams spend half their time resolving critical issues. The only way to reduce these numbers is to know how long it takes to reach resolution and recover after an incident occurs.

Many teams view incident management and response times as a great way to measure IT performance. This often translates to use of the MTTx metric, also known as mean time to detect, mean time to acknowledge and or mean time to resolve.

Almost half of the respondents (45%) said they didn't use MTTx for multiple reasons, such as a lack of awareness, difficulty measuring accurately, or a preference for alternative metrics. Regardless, sufficient and prompt MTTx is a strong measure for operational resilience.

Improving Operational Resilience

To take operational resilience from insufficient to excellent, organizations must build their IT frameworks on solid relationships, streamlined processes, and comprehensive tooling.

A focus on relationships should extend to both technology and teams. IT leaders can look to comprehensive observability software to view how each IT asset, piece of data, and login credentials relate to each other. This help leaders create a map to describe the causes and effects within a system if a disruption occurs. Similar to tooling, it's also important to map relationships between team members. When you understand the relationships between team and technology, you can discern which assets and workflows are most important and which require the highest priority.

Once you outline relationships, you can begin delving into processes. A good way to figure out what's working and what isn't, is by surveying IT team members. They can best describe areas with communication problems, antithetical working styles, or a lack of necessary expertise. You may find you need to move team members around or decide that teamwork is great but could benefit from better tooling.

If tooling is part of the solution, it's important to meet with leadership to implement technology that is helpful, addresses team needs, and aligns with business goals. For example, if you have an IT team that has historically suffered from alert fatigue and disjointed incident management, the team may benefit from tooling that centralizes incident response and helps isolate and identify the most critical issues. This creates focus and streamlined processes that can enhance teamwide operational resilience.

When organizations can improve their tools, teams and processes, they can create a culture of operational resilience that breaks down silos and efficiently responds in the face of disruption. 

Sean Sebring is Solutions Engineering Manager at SolarWinds

Hot Topics

The Latest

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

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 ...