Modern AIOps Leaders Demand Flexible Control Systems Wrapped In Opinionated Infrastructure

Enterprise IT maturity is shifting away from groundbreaking tech toward disciplined operational coherence. As organizations scale increasingly complex hyperscale and hybrid environments, technology has continued to support that scalability. What appears to be a systems problem is more often a coordination problem, where fragmented ownership and misaligned processes quietly erode performance. Accordingly, the industry conversation around AIOps has largely framed the technology as an operational efficiency tool: smarter alerting, faster incident correlation, reduced mean time to resolution. Unfortunately, the move to AIOps isn't a default fix to this problem.

CIO News spoke with Johnny Franco-Arboine, a Senior Agile Project Manager at Amtrak who has built his career at the intersection of infrastructure, cloud, and large-scale Agile delivery. Franco-Arboine sees it differently, and the distinction matters for how organizations should be sizing the investment.

"Systemic inefficiency rarely lives in the technology itself. It lives in organizational boundaries and fragmented accountability," said Franco-Arboine. This inefficiency is hard to spot because the very tools used to measure success create a deceptive sense of progress, particularly in AIOps. The resulting delivery bottlenecks are often the most visible symptoms of what, at its core, is a breakdown in governance.

• Hiding in plain sight: For Franco-Arboine, relying on the tools used to measure success doesn't quite capture the organization-wide operations that impact performance. "At scale, AIOps becomes a governance enforcement layer. When telemetry and correlation engines begin automatically enforcing operational baselines, they essentially enforce executive policy through automation."

If AIOps should be a governance mechanism, then its effectiveness is entirely bound up in the quality of the policies it enforces. AIOps, then, needs to move beyond serving as a dashboard and exist as a true policy automation tool. Franco-Arboine identified three preconditions that must be in place before AIOps can operate as a true control system: unified observability across infrastructure, applications, and identity systems; documented operational standards and runbooks that automation can reliably execute; and governance alignment across security, platform engineering, and DevOps. Following these three pillars leads to tools like MCP servers that operationalize them into trusted workflows that connect platforms and AI agent infrastructures.

Franco-Arboine identified a consistent pattern in what surfaces during compliance reviews where tech blends best practices with AIOps that can make them a reality: identity sprawl, undocumented system dependencies, outdated account management procedures, inconsistent documentation practices, and irregular patch governance. None of these are novel technology problem. They are discipline problems where the accumulated residue of years of local optimization without unified operational accountability.

• An inconvenient truth: It was in the course of his own compliance work that Franco-Arboine noticed widespread gaps that would affect efficiency and security. "In my work with PCI DSS compliance, the biggest gaps that surface are identity sprawl, undocumented system dependencies, inconsistent patch governance, and outdated account management procedures."

• Discipline over dazzle: More importantly, these compliance requirements force leaders to acknowledge that the technology won't solve efficiency problems—it becomes the efficiency problem when organizational bottlenecks are disregarded. He clarified that "modernization initiatives often focus on new platforms or migrations, but compliance forces the organization to confront operational discipline."

What he discovered here is that the framing of autonomous systems often reflects a form of reverse causality. Automation doesn't create organizational discipline, but it does amplify whatever discipline (or lack thereof) is already there. And there are often similar, long-standing challenges in many organizations that AIOps unearths, such as fragmented ownership of systems and tasks. This fragmented authority creates "decision latency," triggering a ripple effect that cascades down to the teams tasked with delivery. Franco-Arboine noted that "when governance breaks down, the first symptom is decision latency. That kind of 'downtime' disrupts or destroys business value."

• Misplaced accountability: According to Franco-Arboine, a lack of accountability leads to a lack of ownership over tasks and decisions, resulting in a slow, reactive approach to project and IT management. "The consequences land on the delivery teams, specifically the project managers, engineering leads, and operations teams. They are the ones accountable for timelines, outages, and compliance deadlines, even when the root cause is organizational misalignment."

A compliance audit is often one of the few processes that reveals these hidden gaps. The audit process forces an organization to examine its infrastructure through the lens of accountability. A focus on verifiable governance often surfaces deep-seated issues that typical modernization projects, centered on new platforms, might miss. It’s here, under the harsh light of an audit, that the consequences of fragmented ownership become starkly clear.

Ultimately, the answer, Franco-Arboine said, lies in what he called "IT Operational Coherence." After years of piecemeal adoption of cloud, Agile, and AI, the next wave of competitive advantage will likely come from integrating governance, security, and telemetry into a single, coherent operational system, such as an MCP. Under this model, agents, processes, and platforms are all under a single umbrella where workflows are observable and governable in one place. Successful enterprises are those that cultivate a continuously observable, governable ecosystem, treating AIOps as a tool that amplifies coherence in that ecosystem rather than destabilizing it. Embracing this system-centric mindset could be the defining differentiator for enterprise IT success in 2026 and beyond.