A Research Agent Can Leak Private Files Through Its Search Queries
A research agent can leak a private document without uploading it. It can read a detail, turn it into a web search,…
According to PagerDuty's 2025 State of Digital Operations Report reveals an interesting divide in how different levels of IT organizations view AI agents. While 53% of CIOs and CTOs see agentic AI as core to future operations, only 29% of practitioners share this enthusiasm. This gap isn't surprising when you understand the different perspectives these groups bring to AI adoption.
From the executive suite, agentic AI looks like a clear win. The numbers are compelling: 37% operational efficiency gains, 36% improved customer experiences, and 38% better insights from data. When you're focused on strategic objectives and bottom-line results, these improvements make AI adoption seem like an obvious choice.
CIOs and CTOs are paid to think big picture and long-term. They see competitors adopting AI, read about breakthrough capabilities, and recognize that staying competitive means embracing these technologies. Their perspective naturally gravitates toward potential rather than problems.
IT practitioners see a different reality. They're the ones wrestling with the actual implementation challenges that determine whether AI projects succeed or fail. Their caution comes from hands-on experience with current limitations.
Take something seemingly simple like using AI agents for incident response. The idea sounds great in a board room: AI analyzing alerts, identifying root causes, and initiating responses automatically. But practitioners know the complexity hiding beneath this simple description.
They've seen how AI can struggle with nuanced decisions in complex environments. They've dealt with the challenges of integrating these systems with legacy infrastructure. They understand the security implications of giving AI agents operational control. Most importantly, they've learned to be wary of solutions that sound too good to be true.
This disconnect between executive enthusiasm and practitioner caution isn't unique to AI. We've seen similar patterns with cloud adoption, DevOps transformation, and other major technological shifts. The pattern usually goes something like this:
Executives get excited about potential benefits and push for rapid adoption. Practitioners raise concerns based on real-world complexity. Initial implementations hit unexpected challenges. Eventually, a more balanced approach emerges that acknowledges both the potential and the practical limitations.
What's different with AI agents is the speed of evolution. The technology is advancing so rapidly that the usual pattern of gradual adoption and adjustment is compressed. This makes the gap between executive vision and practical reality more stark.
The solution isn't for CIOs to temper their enthusiasm or for practitioners to ignore their valid concerns. Instead, organizations need to create space for both perspectives to inform their AI strategy.
This means starting with smaller, well-defined projects where success criteria are clear and risks are manageable. It means investing in proper training and tooling before deployment. It means creating clear escalation paths for when AI agents need human oversight. Most importantly, it means giving practitioners time to experiment and validate AI solutions before full deployment.
The future likely lies somewhere between the CIO's optimistic vision and the practitioner's cautious reality. AI agents will transform IT operations, but probably not as quickly or smoothly as executives hope. The transformation will require careful attention to practitioners' concerns about reliability, security, and integration.
Success will come to organizations that can maintain momentum toward AI adoption while honestly addressing the practical challenges practitioners encounter. This isn't about selling a vision - it's about supporting a journey through the messy details of implementation.
The fact that practitioners are more cautious about AI agents isn't a problem to be solved. It's valuable feedback that should inform how organizations approach AI adoption. Their perspective isn't holding back progress; it's helping ensure that progress is sustainable and genuine rather than just hype-driven change.
The goal shouldn't be to close the enthusiasm gap, but to use it productively. Let executive vision push the boundaries of what's possible while letting practitioner experience guide the path to getting there. This balance of ambition and pragmatism is how real technological transformation happens.
Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.
Take a look at vroni.com