Skip to main content

AI Without Readiness Is Risk - What Enterprises Must Fix First

Robin Macfarlane
RRMac Associates

AI has quickly become the tech world's version of peer pressure. As competitors adopt it, developers push for it, and vendors weave it into nearly every platform, the message feels unavoidable: you need AI to keep up.

The discussion has rapidly shifted from whether organizations should adopt AI to how quickly they can deploy it. But moving too fast introduces its own risks, especially when companies haven't paused to answer a more critical question: What problem are we actually trying to solve?

The Pressure to Adopt AI Is Real. So Is the Risk of Getting It Wrong

For some companies, AI may genuinely create efficiencies. It can accelerate development, reduce repetitive work, improve workflows, and surface insights hidden in years of operational data. For others, it risks becoming the next generation of enterprise shelfware: adopted quickly, talked about often, and rarely integrated in ways that meaningfully change how the organization operates.

Technology alone doesn't create transformation. It amplifies what already exists. If systems are fragmented, workflows disconnected, or data difficult to access, AI won't necessarily fix those issues. It may expose them faster.

That matters because many organizations pursuing AI still rely on mainframes to run some of their most critical operations. And despite assumptions that legacy environments slow innovation, those systems may hold one of the most valuable assets for AI success: decades of business logic, institutional knowledge, and operational data.

Preparing for AI often starts well before implementation. It requires modernization, enterprise readiness, and a clear understanding of how information moves across the business. The value already exists in many organizations. The question is whether they're positioned to use it effectively.

The Conversation Around AI Is Really a Conversation About Data

Mainframes hold decades of context that AI depends on to generate meaningful value. Years, sometimes decades, of business logic, transaction history, operational records, customer interactions, and institutional knowledge live there. In many enterprises, the mainframe contains the most complete picture of how the business actually runs.

Enterprise data creates opportunities many organizations overlook. Connected thoughtfully, it can improve AI outputs, support code modernization efforts, preserve institutional knowledge as experienced employees retire, and help teams navigate increasingly complex environments. AI may help accelerate code conversion, reduce manual work, or surface insights more quickly.

But access to information alone doesn't create value. Organizations still need people who understand business context, know which outputs to trust, and can recognize when AI gets something wrong. Historical knowledge, human judgment, and oversight remain essential, particularly in environments where errors carry operational or regulatory risk.

The greatest opportunity may not be giving AI access to decades of enterprise knowledge. It may be creating environments where data, technology, and human expertise work together in ways that improve decisions without sacrificing security, governance, or control.

Realizing that opportunity requires more than access to information. It depends on whether systems, workflows, and teams are prepared to support AI effectively. That's where the conversation shifts from data to modernization.

Modernization Is Bigger than the Mainframe, and AI Readiness Is Bigger than Modernization

Organizations can invest in newer hardware, modern tooling, and AI-enabled environments while continuing to operate with fragmented workflows, disconnected teams, and assumptions built decades earlier. The technology changes, but the enterprise often does not.

That gap matters because AI doesn't operate in isolation. Its effectiveness depends on how information moves, how decisions are made, where ownership sits, and whether teams can actually use new capabilities together.

Modernization creates an opportunity to improve how information moves, how teams collaborate, and how new technologies are adopted across the enterprise. More connected systems, accessible data, and shared workflows make it easier for organizations to experiment responsibly, integrate AI into everyday work, and scale adoption beyond isolated use cases.

Real AI readiness often depends less on infrastructure and more on whether teams, processes, and information can move through the organization effectively.

Where are decisions delayed?

Where does information get stuck?

Which teams operate in isolation?

AI tends to expose those gaps, but modernization creates an opportunity to address them before inefficiencies are amplified.

AI Raises New Questions About Ownership, Access and Control

There's enormous pressure right now to move quickly. Speed has become a competitive advantage, but without due diligence it has rarely ended well when it comes to technology.

The bigger concern may not be AI itself, but how casually organizations are willing to hand over information to it. Public AI tools have made experimentation easier than ever, but organizations handling proprietary code, regulated information, or customer data should think carefully about where that information goes and who ultimately retains control over it.

Questions around AI adoption increasingly extend beyond usefulness. Organizations need clarity around who owns the information being shared, where data is processed, and what happens to it over time. The convenience of public AI tools can make those questions easy to overlook, particularly when speed and experimentation become priorities.

For enterprises managing proprietary code, customer records, financial information, or regulated data, the stakes are higher. Protecting intellectual property and customer information must come before convenience. For companies like these, purpose-built or private AI environments operating within existing security boundaries may be a more appropriate fit than broadly accessible public tools.

That caution can sound conservative in a market obsessed with adoption, but it isn't. It's governance. And as AI becomes more embedded in enterprise environments, governance may become just as important as innovation. Because once AI is integrated into critical workflows, questions around ownership, access, and accountability become business decisions, not just technical ones.

The Future of AI Belongs to Organizations Prepared to Use It Well

AI will continue advancing whether organizations are ready or not. Expectations will rise. New capabilities will emerge.

Organizations that approach AI with intention rather than urgency may discover something important: modernization, enterprise readiness, data strategy, and AI adoption are not separate conversations. Together, they create the foundation for a more connected, resilient, and adaptive organization.

Over the next decade, the companies that see the greatest value from AI may not be the ones that adopted it first. They will be the ones that invested in understanding their environments, modernizing with purpose, and creating systems where technology, data, and people work together effectively.

Robin Macfarlane is President and CEO of RRMac Associates, LLC

Hot Topics

The Latest

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

Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...

Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...

This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...

There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...

AI Without Readiness Is Risk - What Enterprises Must Fix First

Robin Macfarlane
RRMac Associates

AI has quickly become the tech world's version of peer pressure. As competitors adopt it, developers push for it, and vendors weave it into nearly every platform, the message feels unavoidable: you need AI to keep up.

The discussion has rapidly shifted from whether organizations should adopt AI to how quickly they can deploy it. But moving too fast introduces its own risks, especially when companies haven't paused to answer a more critical question: What problem are we actually trying to solve?

The Pressure to Adopt AI Is Real. So Is the Risk of Getting It Wrong

For some companies, AI may genuinely create efficiencies. It can accelerate development, reduce repetitive work, improve workflows, and surface insights hidden in years of operational data. For others, it risks becoming the next generation of enterprise shelfware: adopted quickly, talked about often, and rarely integrated in ways that meaningfully change how the organization operates.

Technology alone doesn't create transformation. It amplifies what already exists. If systems are fragmented, workflows disconnected, or data difficult to access, AI won't necessarily fix those issues. It may expose them faster.

That matters because many organizations pursuing AI still rely on mainframes to run some of their most critical operations. And despite assumptions that legacy environments slow innovation, those systems may hold one of the most valuable assets for AI success: decades of business logic, institutional knowledge, and operational data.

Preparing for AI often starts well before implementation. It requires modernization, enterprise readiness, and a clear understanding of how information moves across the business. The value already exists in many organizations. The question is whether they're positioned to use it effectively.

The Conversation Around AI Is Really a Conversation About Data

Mainframes hold decades of context that AI depends on to generate meaningful value. Years, sometimes decades, of business logic, transaction history, operational records, customer interactions, and institutional knowledge live there. In many enterprises, the mainframe contains the most complete picture of how the business actually runs.

Enterprise data creates opportunities many organizations overlook. Connected thoughtfully, it can improve AI outputs, support code modernization efforts, preserve institutional knowledge as experienced employees retire, and help teams navigate increasingly complex environments. AI may help accelerate code conversion, reduce manual work, or surface insights more quickly.

But access to information alone doesn't create value. Organizations still need people who understand business context, know which outputs to trust, and can recognize when AI gets something wrong. Historical knowledge, human judgment, and oversight remain essential, particularly in environments where errors carry operational or regulatory risk.

The greatest opportunity may not be giving AI access to decades of enterprise knowledge. It may be creating environments where data, technology, and human expertise work together in ways that improve decisions without sacrificing security, governance, or control.

Realizing that opportunity requires more than access to information. It depends on whether systems, workflows, and teams are prepared to support AI effectively. That's where the conversation shifts from data to modernization.

Modernization Is Bigger than the Mainframe, and AI Readiness Is Bigger than Modernization

Organizations can invest in newer hardware, modern tooling, and AI-enabled environments while continuing to operate with fragmented workflows, disconnected teams, and assumptions built decades earlier. The technology changes, but the enterprise often does not.

That gap matters because AI doesn't operate in isolation. Its effectiveness depends on how information moves, how decisions are made, where ownership sits, and whether teams can actually use new capabilities together.

Modernization creates an opportunity to improve how information moves, how teams collaborate, and how new technologies are adopted across the enterprise. More connected systems, accessible data, and shared workflows make it easier for organizations to experiment responsibly, integrate AI into everyday work, and scale adoption beyond isolated use cases.

Real AI readiness often depends less on infrastructure and more on whether teams, processes, and information can move through the organization effectively.

Where are decisions delayed?

Where does information get stuck?

Which teams operate in isolation?

AI tends to expose those gaps, but modernization creates an opportunity to address them before inefficiencies are amplified.

AI Raises New Questions About Ownership, Access and Control

There's enormous pressure right now to move quickly. Speed has become a competitive advantage, but without due diligence it has rarely ended well when it comes to technology.

The bigger concern may not be AI itself, but how casually organizations are willing to hand over information to it. Public AI tools have made experimentation easier than ever, but organizations handling proprietary code, regulated information, or customer data should think carefully about where that information goes and who ultimately retains control over it.

Questions around AI adoption increasingly extend beyond usefulness. Organizations need clarity around who owns the information being shared, where data is processed, and what happens to it over time. The convenience of public AI tools can make those questions easy to overlook, particularly when speed and experimentation become priorities.

For enterprises managing proprietary code, customer records, financial information, or regulated data, the stakes are higher. Protecting intellectual property and customer information must come before convenience. For companies like these, purpose-built or private AI environments operating within existing security boundaries may be a more appropriate fit than broadly accessible public tools.

That caution can sound conservative in a market obsessed with adoption, but it isn't. It's governance. And as AI becomes more embedded in enterprise environments, governance may become just as important as innovation. Because once AI is integrated into critical workflows, questions around ownership, access, and accountability become business decisions, not just technical ones.

The Future of AI Belongs to Organizations Prepared to Use It Well

AI will continue advancing whether organizations are ready or not. Expectations will rise. New capabilities will emerge.

Organizations that approach AI with intention rather than urgency may discover something important: modernization, enterprise readiness, data strategy, and AI adoption are not separate conversations. Together, they create the foundation for a more connected, resilient, and adaptive organization.

Over the next decade, the companies that see the greatest value from AI may not be the ones that adopted it first. They will be the ones that invested in understanding their environments, modernizing with purpose, and creating systems where technology, data, and people work together effectively.

Robin Macfarlane is President and CEO of RRMac Associates, LLC

Hot Topics

The Latest

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

Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...

Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...

This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...

There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...