How Legacy Friction Strangles AI-Driven DevOps

David Torgerson
Lucid Software

Organizations are discovering that AI performance reflects the health of their core systems as pilots move into production. Whether organizations realize it or not, they are already somewhere on the AI maturity curve — progressing from fragmented AI use to aggregated consumption, contextual processing, logic execution, and ultimately strategic transformation. Most stall in the early stages, not because of model limitations, but because their operational foundation isn't ready to support the next level. Lucid's AI Readiness Report found that only 26% of organizations that have implemented AI agents say those efforts have been "completely successful," a clear sign that something beneath the surface is holding teams back.

In many cases, the constraint is what I call the "Legacy Layer": the accumulation of old systems, and undocumented and fragmented workflows that quietly power day-to-day operations. Over time, this layer becomes the operational backbone and the primary source of friction.

This infrastructure of undocumented workarounds and isolated data silos drains momentum long before a project reaches production. When you pull back the covers on AI success stories, it almost always boils down to the maturity of their documentation and processes. If your AI efforts have hit a wall, the problem is likely the hidden blockers in your workflow. When organizations try to layer AI on top of this legacy foundation, they often assume automation will make up for these complex issues, but in reality, it only exposes them.

Spotting Associated Pain Points and Frictions in Legacy Systems

AI thrives on clean data and clearly defined processes, yet legacy systems offer the opposite — siloed tools, point-to-point integrations, and human workarounds. This structural disconnect creates associated pain — subtle frictions that rarely trigger alarms but steadily drain momentum. When 61% of workers say their AI strategy is misaligned with operational capabilities, they are feeling the weight of this friction.

Because modern AI depends on an open architecture where data moves freely, these isolated silos make it nearly impossible for an agent to create a single source of truth or act across a broader ecosystem. Without that shared context, AI is able to analyze data in one corner of the organization but is unable to execute meaningful action across the entire workflow.

This lack of connectivity is compounded by the tacit knowledge gap. Many DevOps environments function because only a handful of people know how things really work. They understand the edge cases, and the undocumented steps that keep systems running. AI can't learn from tacit knowledge. It needs that expertise extracted and structured, which is why 49% of organizations say undocumented or ad-hoc processes impact efficiency. In practice, much of this knowledge already surfaces in diagrams, scratch pads, and collaborative workspaces created as part of day-to-day activities.

Recognizing AI Readiness Gaps

Until hidden expertise is codified, AI remains blocked by a map it cannot read. If a workflow is inherently inefficient or relies on human intuition to bridge technical gaps, deploying AI will only serve to make those inefficiencies move at machine speed.

Time compounds the risk. As experienced employees leave, organizations lose the institutional memory of how their legacy systems actually behave. Once that tacit knowledge is gone, it becomes nearly impossible to train an AI to replicate those nuances accurately. This explains why 46% of organizations have integrated AI into only "some" or "almost no" workflows. They lack the basic visibility needed to support day-to-day operations, let alone a sophisticated automation layer.

Before scaling AI, you must assess your associated pain metric. If a system requires constant manual intervention or custom workarounds, it is a high-drag environment. Highly associated pain acts as a firewall that prevents AI from delivering measurable ROI.

Practical Interventions to Reduce Pain Points/Friction

The good news is that stalled AI initiatives don't require a full IT overhaul to get moving again. Small, targeted interventions can unlock immediate progress. For DevOps teams looking to reduce friction, I recommend these four steps:

  • Make the current state visible. Intelligent diagramming tools can help teams map workflows as they actually exist, not only as they were designed on paper. This extracts low-level documentation without making it an extra step, because you are tying into the place where people actually work day-to-day.
  • Streamline and standardize where possible. You don't need perfection, but consistency matters. Standard inputs and outputs give AI something reliable to work with.
  • Focus on quick wins. Automating a single high-friction handoff or reducing manual reporting can show immediate productivity gains and build internal confidence in AI-driven improvements.
  • Align systems with business objectives. AI should support real operational goals, not abstract innovation metrics. When workflows are clearer and less fragmented, AI becomes more actionable by default.

Moving Past Stalled AI Projects

AI can't deliver results in disconnected systems or broken workflows. The organizations seeing real productivity gains aren't deploying more tools, they're identifying pain points, clarifying processes and aligning stakeholders around how work actually gets done.

The organizations seeing real productivity gains today aren't necessarily the ones with the most advanced models or the largest budgets, it's the ones identifying hidden pain points, clarifying their Legacy Layer, and aligning stakeholders around how work actually gets done.

For DevOps leaders, the takeaway is simple: before deploying more AI, look for the hidden blockers underneath. If humans don't understand the workflow, AI never will. 

David Torgerson is VP of Infrastructure and IT at Lucid Software

Related Links

Hot Topics

The Latest

The Corporate Network Is Fading - Here's What Replaces It

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

IT Leaders Must Establish a Network Data Architecture Practice

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

Data Center Outages Are Decreasing but More Costly

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

Observability Has a Physical Layer Now: What AI Infrastructure Teaches IT Operations

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

TLS Certificate Expiration Is Becoming an Observability Problem

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprise Cloud Observability: Choosing the Right Starting Point

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

AI Is Making Incident Management More Complex - Bad Data Makes It Harder

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

MEAN TIME TO INSIGHT Podcast - Episode 26: Network Compliance

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Why VM and Container Monitoring Is Not Enough for Cloud-Hosted Autonomous Agents

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

Beyond Monitoring: Why IT Operations Must Evolve into Decision Operations

Enterprise IT environments have never been more observable ... Yet many organizations still grapple with outages, lengthy incident resolution cycles, and increasing complexity. Most teams do not suffer from a shortage of data. They struggle to determine what deserves attention and what action to take next ... Enterprise IT operations must move beyond monitoring and visibility. The next stage of maturity is decision operations, an approach that helps teams make faster, better-informed decisions ...

How Legacy Friction Strangles AI-Driven DevOps

David Torgerson
Lucid Software

Organizations are discovering that AI performance reflects the health of their core systems as pilots move into production. Whether organizations realize it or not, they are already somewhere on the AI maturity curve — progressing from fragmented AI use to aggregated consumption, contextual processing, logic execution, and ultimately strategic transformation. Most stall in the early stages, not because of model limitations, but because their operational foundation isn't ready to support the next level. Lucid's AI Readiness Report found that only 26% of organizations that have implemented AI agents say those efforts have been "completely successful," a clear sign that something beneath the surface is holding teams back.

In many cases, the constraint is what I call the "Legacy Layer": the accumulation of old systems, and undocumented and fragmented workflows that quietly power day-to-day operations. Over time, this layer becomes the operational backbone and the primary source of friction.

This infrastructure of undocumented workarounds and isolated data silos drains momentum long before a project reaches production. When you pull back the covers on AI success stories, it almost always boils down to the maturity of their documentation and processes. If your AI efforts have hit a wall, the problem is likely the hidden blockers in your workflow. When organizations try to layer AI on top of this legacy foundation, they often assume automation will make up for these complex issues, but in reality, it only exposes them.

Spotting Associated Pain Points and Frictions in Legacy Systems

AI thrives on clean data and clearly defined processes, yet legacy systems offer the opposite — siloed tools, point-to-point integrations, and human workarounds. This structural disconnect creates associated pain — subtle frictions that rarely trigger alarms but steadily drain momentum. When 61% of workers say their AI strategy is misaligned with operational capabilities, they are feeling the weight of this friction.

Because modern AI depends on an open architecture where data moves freely, these isolated silos make it nearly impossible for an agent to create a single source of truth or act across a broader ecosystem. Without that shared context, AI is able to analyze data in one corner of the organization but is unable to execute meaningful action across the entire workflow.

This lack of connectivity is compounded by the tacit knowledge gap. Many DevOps environments function because only a handful of people know how things really work. They understand the edge cases, and the undocumented steps that keep systems running. AI can't learn from tacit knowledge. It needs that expertise extracted and structured, which is why 49% of organizations say undocumented or ad-hoc processes impact efficiency. In practice, much of this knowledge already surfaces in diagrams, scratch pads, and collaborative workspaces created as part of day-to-day activities.

Recognizing AI Readiness Gaps

Until hidden expertise is codified, AI remains blocked by a map it cannot read. If a workflow is inherently inefficient or relies on human intuition to bridge technical gaps, deploying AI will only serve to make those inefficiencies move at machine speed.

Time compounds the risk. As experienced employees leave, organizations lose the institutional memory of how their legacy systems actually behave. Once that tacit knowledge is gone, it becomes nearly impossible to train an AI to replicate those nuances accurately. This explains why 46% of organizations have integrated AI into only "some" or "almost no" workflows. They lack the basic visibility needed to support day-to-day operations, let alone a sophisticated automation layer.

Before scaling AI, you must assess your associated pain metric. If a system requires constant manual intervention or custom workarounds, it is a high-drag environment. Highly associated pain acts as a firewall that prevents AI from delivering measurable ROI.

Practical Interventions to Reduce Pain Points/Friction

The good news is that stalled AI initiatives don't require a full IT overhaul to get moving again. Small, targeted interventions can unlock immediate progress. For DevOps teams looking to reduce friction, I recommend these four steps:

  • Make the current state visible. Intelligent diagramming tools can help teams map workflows as they actually exist, not only as they were designed on paper. This extracts low-level documentation without making it an extra step, because you are tying into the place where people actually work day-to-day.
  • Streamline and standardize where possible. You don't need perfection, but consistency matters. Standard inputs and outputs give AI something reliable to work with.
  • Focus on quick wins. Automating a single high-friction handoff or reducing manual reporting can show immediate productivity gains and build internal confidence in AI-driven improvements.
  • Align systems with business objectives. AI should support real operational goals, not abstract innovation metrics. When workflows are clearer and less fragmented, AI becomes more actionable by default.

Moving Past Stalled AI Projects

AI can't deliver results in disconnected systems or broken workflows. The organizations seeing real productivity gains aren't deploying more tools, they're identifying pain points, clarifying processes and aligning stakeholders around how work actually gets done.

The organizations seeing real productivity gains today aren't necessarily the ones with the most advanced models or the largest budgets, it's the ones identifying hidden pain points, clarifying their Legacy Layer, and aligning stakeholders around how work actually gets done.

For DevOps leaders, the takeaway is simple: before deploying more AI, look for the hidden blockers underneath. If humans don't understand the workflow, AI never will. 

David Torgerson is VP of Infrastructure and IT at Lucid Software

Related Links

Hot Topics

The Latest

The Corporate Network Is Fading - Here's What Replaces It

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

IT Leaders Must Establish a Network Data Architecture Practice

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

Data Center Outages Are Decreasing but More Costly

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

Observability Has a Physical Layer Now: What AI Infrastructure Teaches IT Operations

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

TLS Certificate Expiration Is Becoming an Observability Problem

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprise Cloud Observability: Choosing the Right Starting Point

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

AI Is Making Incident Management More Complex - Bad Data Makes It Harder

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

MEAN TIME TO INSIGHT Podcast - Episode 26: Network Compliance

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Why VM and Container Monitoring Is Not Enough for Cloud-Hosted Autonomous Agents

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

Beyond Monitoring: Why IT Operations Must Evolve into Decision Operations

Enterprise IT environments have never been more observable ... Yet many organizations still grapple with outages, lengthy incident resolution cycles, and increasing complexity. Most teams do not suffer from a shortage of data. They struggle to determine what deserves attention and what action to take next ... Enterprise IT operations must move beyond monitoring and visibility. The next stage of maturity is decision operations, an approach that helps teams make faster, better-informed decisions ...