Skip to main content

Breaking Down Agentic AI Fragmentation and Complexity with Governance

Ritu Dubey
Digitate

ITOps are going through a significant and fundamental transformation as self-directed AI agents that can independently and autonomously operate and make decisions over entire workflows are evolving past proof of concept and into production deployments. By deploying AI agents at scale, businesses can realize tangible operational benefits, including increased efficiencies, the automation of business processes at scale, and reducing human intervention to just where it's needed.

This penetration of agentic AI is borne out by data published in Deloitte's 2026 report, The State of AI in the Enterprise, which tracks AI adoption and impact. Deloitte found that 74% of enterprises expect to deploy agentic AI solutions in the next 24 months. However, the rush to deployment is outpacing foundational work, though. Only 21% of enterprises have fully formed agent governance models in place.

The result?

AI agents deployed without guidance or governance begin to function as fragmented islands of complexity. To realize agentic AI's full value, businesses must focus less on rapidly pushing individual agents into production and prioritize building sustainable governance, integration, and deployment frameworks.

Moving from Agentic Fragmentation to Integration

Historically, IT workflows have been centered around human-controlled systems performing predefined processes. That's simply not enough anymore. Organizations nowadays expect systems to react and adapt to information coming from many different channels, often needing to make automated decisions in real time.

Agentic AI solves that challenge by freeing organizations from manual workflows. Software agents can handle complex, automated tasks without burdening human employees, then make decentralized decisions faster than any human could. The promise of agencies is too great to pass up — but there's a caveat. Many organizations rush deployment without putting the proper planning in place, creating systems that lack the cohesion needed to deliver meaningful business value.

To avoid fragmentation, organizations should take a lesson from the Agile playbook and think about how individual agents will fit into the larger ecosystem. One of the primary benefits of agents is their ability to operate independently. But autonomy doesn't mean organizations should withhold planning for how AI agents collaborate. Establish orchestration frameworks to keep AI decision-making aligned with broader business objectives. Once those frameworks are established, every new agent deployed should reduce fragmentation rather than contribute to it.

Demystifying Governance: Enabling Agencies to Scale Thoughtfully

There's a lot of fear around governance. Some organizations worry that imposing structure on AI agents limits their autonomy, resulting in stunted growth and AI that's able to do little more than its initial programming. That fear is unnecessary.

Governance isn't a bottleneck — it's the key that unlocks value from agents. Organizations that establish governance models early not only mitigate risk, but they also create guardrails agents can use to improve decisions over time. The best governance models strike a balance between control and autonomy, giving agents enough flexibility to adjust their decision-making based on incoming data.

Remember: agents that never break your rules are still free to make bad decisions. Effective governance should allow agents to learn and adapt their behavior while giving teams visibility into how decisions are made.

Connecting the Dots: Agents Alone Don't Equal Value

Siloed agents aren't just complicated; they don't create value either. When asked about their current agentic AI deployments, too many organizations will likely point to a project deployed into a single workflow. Nice start, but those agents aren't connected to anything else.

AI agents are only as valuable as the data they have access to. If you deploy an agent into a workflow without linking it to other systems, processes, or data stores it needs to operate effectively, it'll make decisions based on an incomplete understanding of your organization. At best, that agent will be a bottleneck. At worst, it could cause extensive damage.

Here's the best way to think about agent integration: An agent shouldn't just be connected to the IT workflow it supports. By chaining agents together and linking them to shared data sources, you'll drive accuracy in decisions your agents make while improving business outcomes across the organization.

Connected agents = AI value.

Give Yourself Permission to Stop Experimenting

To be clear, experimentation is good. There's absolutely a time and place for pilots. But too many organizations get comfortable in the pilot stage. An agent deployed into production is not experimenting toward value, but rather a cost that either begins to provide value or doesn't.

Running endless pilot projects doesn't help you scale in an agile way. Instead, organizations should establish deployment plans with success metrics defined in milestones. How will you know if your AI agent is ready to graduate from experimentation? Your deployment plan should outline clearly defined objectives but also allow for some flexibility. It's fine for your plan to evolve as you learn more about your agent, but you shouldn't neglect to set a plan in the first place.

Agentic AI Requires Work

Unlocking the full potential of agentic AI isn't easy. But then scaling AI to create business value is challenging, and continuing to rush agents into production without making foundational investments now will only make that work that bit more difficult.

Think about agents as you would a new employee. They don't automatically know how your organization works, but if they're deployed effectively, they will learn your workflows and add value wherever they're most needed. Agentic AI that fits into your organizational ecosystem won't work alongside your existing systems, processes, and data — it will join them.

Ritu Dubey is Global Head of New Business Sales and Market Development at Digitate

Hot Topics

The Latest

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

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

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

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

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

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

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

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

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

Breaking Down Agentic AI Fragmentation and Complexity with Governance

Ritu Dubey
Digitate

ITOps are going through a significant and fundamental transformation as self-directed AI agents that can independently and autonomously operate and make decisions over entire workflows are evolving past proof of concept and into production deployments. By deploying AI agents at scale, businesses can realize tangible operational benefits, including increased efficiencies, the automation of business processes at scale, and reducing human intervention to just where it's needed.

This penetration of agentic AI is borne out by data published in Deloitte's 2026 report, The State of AI in the Enterprise, which tracks AI adoption and impact. Deloitte found that 74% of enterprises expect to deploy agentic AI solutions in the next 24 months. However, the rush to deployment is outpacing foundational work, though. Only 21% of enterprises have fully formed agent governance models in place.

The result?

AI agents deployed without guidance or governance begin to function as fragmented islands of complexity. To realize agentic AI's full value, businesses must focus less on rapidly pushing individual agents into production and prioritize building sustainable governance, integration, and deployment frameworks.

Moving from Agentic Fragmentation to Integration

Historically, IT workflows have been centered around human-controlled systems performing predefined processes. That's simply not enough anymore. Organizations nowadays expect systems to react and adapt to information coming from many different channels, often needing to make automated decisions in real time.

Agentic AI solves that challenge by freeing organizations from manual workflows. Software agents can handle complex, automated tasks without burdening human employees, then make decentralized decisions faster than any human could. The promise of agencies is too great to pass up — but there's a caveat. Many organizations rush deployment without putting the proper planning in place, creating systems that lack the cohesion needed to deliver meaningful business value.

To avoid fragmentation, organizations should take a lesson from the Agile playbook and think about how individual agents will fit into the larger ecosystem. One of the primary benefits of agents is their ability to operate independently. But autonomy doesn't mean organizations should withhold planning for how AI agents collaborate. Establish orchestration frameworks to keep AI decision-making aligned with broader business objectives. Once those frameworks are established, every new agent deployed should reduce fragmentation rather than contribute to it.

Demystifying Governance: Enabling Agencies to Scale Thoughtfully

There's a lot of fear around governance. Some organizations worry that imposing structure on AI agents limits their autonomy, resulting in stunted growth and AI that's able to do little more than its initial programming. That fear is unnecessary.

Governance isn't a bottleneck — it's the key that unlocks value from agents. Organizations that establish governance models early not only mitigate risk, but they also create guardrails agents can use to improve decisions over time. The best governance models strike a balance between control and autonomy, giving agents enough flexibility to adjust their decision-making based on incoming data.

Remember: agents that never break your rules are still free to make bad decisions. Effective governance should allow agents to learn and adapt their behavior while giving teams visibility into how decisions are made.

Connecting the Dots: Agents Alone Don't Equal Value

Siloed agents aren't just complicated; they don't create value either. When asked about their current agentic AI deployments, too many organizations will likely point to a project deployed into a single workflow. Nice start, but those agents aren't connected to anything else.

AI agents are only as valuable as the data they have access to. If you deploy an agent into a workflow without linking it to other systems, processes, or data stores it needs to operate effectively, it'll make decisions based on an incomplete understanding of your organization. At best, that agent will be a bottleneck. At worst, it could cause extensive damage.

Here's the best way to think about agent integration: An agent shouldn't just be connected to the IT workflow it supports. By chaining agents together and linking them to shared data sources, you'll drive accuracy in decisions your agents make while improving business outcomes across the organization.

Connected agents = AI value.

Give Yourself Permission to Stop Experimenting

To be clear, experimentation is good. There's absolutely a time and place for pilots. But too many organizations get comfortable in the pilot stage. An agent deployed into production is not experimenting toward value, but rather a cost that either begins to provide value or doesn't.

Running endless pilot projects doesn't help you scale in an agile way. Instead, organizations should establish deployment plans with success metrics defined in milestones. How will you know if your AI agent is ready to graduate from experimentation? Your deployment plan should outline clearly defined objectives but also allow for some flexibility. It's fine for your plan to evolve as you learn more about your agent, but you shouldn't neglect to set a plan in the first place.

Agentic AI Requires Work

Unlocking the full potential of agentic AI isn't easy. But then scaling AI to create business value is challenging, and continuing to rush agents into production without making foundational investments now will only make that work that bit more difficult.

Think about agents as you would a new employee. They don't automatically know how your organization works, but if they're deployed effectively, they will learn your workflows and add value wherever they're most needed. Agentic AI that fits into your organizational ecosystem won't work alongside your existing systems, processes, and data — it will join them.

Ritu Dubey is Global Head of New Business Sales and Market Development at Digitate

Hot Topics

The Latest

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

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

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

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

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

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

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

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

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