Let me paint you a picture of corporate delusion in its purest form.
Your CIO just walked out of another “AI Strategy” meeting where the team discussed implementing machine learning to optimise application performance.
Sounds progressive, right?
Meanwhile, three floors down, your infrastructure team is manually patching API integrations that broke overnight when a vendor pushed an “upgrade.” They’ve been at it for six hours.
The automation that was supposed to reduce manual work just became the source of emergency manual work.
Here’s the rebel truth that’ll make your transformation consultants squirm: You can’t use AI to solve your IT problems because your IT problems are preventing you from using AI.
Welcome to the complexity death spiral that’s consuming enterprise IT (and the uncomfortable steps to take for breaking free that your vendors definitely don’t want you to read).
The Great Digital Performance
The statistics paint a picture of AI adoption success that would make any board smile.
96% of organisations are deploying AI models, and 73% want AI to optimise their application performance. Gartner predicts worldwide IT spending will increase 7.9% this year, with software spending alone up 10.5%.
But here’s what the glossy transformation reports won’t tell you: 60% of IT professionals are mired in manual operational tasks.
Let that sink in. We’re supposedly in the age of automation, yet more than half of IT professionals are stuck doing the digital equivalent of manual labor. How on Earth did we get here?
The answer lies in the fundamental lie that’s been sold to enterprise IT for the past decade: that adding more technology solves technology problems.
Craig Kane from Kearney gets it partially right when he observes that “technology cycles are spinning faster and faster, and some solutions are evolving so fast, that they’re now a year-long bet, not a three- or five-year bet for CIOs.”
But he’s missing the deeper pathology.
It’s not that technology is moving faster. It’s that we’re addicted to complexity theater.
Myth #1: “Hybrid Cloud Gives Us Flexibility”
The first lie eating away at enterprise sanity is that hybrid cloud deployments create operational flexibility.
The reality? F5’s research shows that 94% of organisations deploy apps across multiple environments, with a median of four different public cloud vendors. Meanwhile, 79% have moved applications back from public clouds to on-premises.
That’s not flexibility. That’s organisational schizophrenia.
Raghav Potluri, who’s seen this disaster from both sides as a technical leader at VMware and now F5, drops the uncomfortable truth: “The hybrid cloud flexibility we promised became hybrid cloud complexity that they couldn’t manage.”
Each additional cloud provider doesn’t just add one more platform to manage, it creates exponential integration points, API relationships, and potential failure modes. What we sold as “unified management” still requires teams to understand the nuances of multiple platforms.
Case in point: AWS’s load balancer API uses completely different authentication, data structures, and error handling than Azure’s, which differs entirely from on-premises solutions.
A team might spend months building AI-powered traffic optimisation that works perfectly with one vendor’s API, only to discover they need to rebuild everything when they expand to another platform.
This is the dirty secret of hybrid cloud: we didn’t eliminate operational complexity, we just centralized it and made it someone else’s problem to figure out.
Myth #2: “Innovation Requires Constant Technology Refresh”
The second delusion destroying enterprise IT is the belief that staying competitive means constantly chasing the latest technology.
Greg Taffet, a fractional CIO, has bought into this madness completely: “I am replacing solutions after a couple of years in some cases right now, because in some cases it’s better to start with new tools to get the better result than get patches and upgrades to the solution we have.”
Some software won’t even last months, he says. Throw-away apps built for specific moment needs and then completely discarded.
This isn’t strategic technology management. This is corporate FOMO in its most expensive form.
Capterra’s 2025 Tech Trends Survey delivers the brutal reality check: 59% of 3,500 businesses surveyed regretted their software purchases.
More than half of those regretful buyers reported significant to monumental financial losses.
Olivia Montgomery from Capterra nails the core problem: “CIOs and business colleagues sometimes think the solutions they have in place are falling behind market innovations and, as a result, their business will fall behind, too. That may be the case, but they may just be falling for marketing hype.”
The businesses least likely to regret software purchases? Those with CIOs who “focus on the business problem first” rather than chasing shiny technology objects.
Yet here we are, with fractional CIOs proudly declaring they’re replacing solutions every couple of years like it’s a badge of honor instead of a symptom of strategic failure.
Myth #3: “More Vendors Mean More Options”
The third lie is that vendor diversification reduces risk and increases capability.
A10’s research reveals the pathological endpoint of this thinking: 58% of organisations consider API sprawl a ‘significant pain point.’ Working with vendor APIs is now the most time-consuming automation-related task for IT teams.
Think about that for a moment.
The tools designed to automate work are consuming more manual effort than the work they were supposed to automate.
47% of EMEA IT professionals and 55% of U.S. executives would change their ADC providers due to limited or poor vendor support. When businesses do consider changing vendors, the cycle repeats: more complexity, more APIs, more integration points.
Potluri sees this vendor proliferation disaster up close: “I’ve seen teams managing dozens of different APIs just for application delivery and security. Every API represents operational overhead.”
But instead of rationalising their vendor stack, organisations keep adding more.
44% of organisations have faced issues with recent vendor licensing changes, and 29% of executives cite rising licensing costs as their top complaint, ahead of even security concerns.
The response? Add another vendor to the mix. Brilliant.
The Systemic Dysfunction: Why This Keeps Getting Worse
The deeper pathology isn’t just bad decision-making, it’s structural dysfunction that compounds over time.
Executive turnover is driving technology churn.
Montgomery identifies new CIOs and business executives seeking to replace existing solutions they inherit with ones they prefer from prior jobs. Each leadership change triggers another round of vendor evaluation, implementation projects, and integration nightmares.
Meanwhile, the shift in AI adoption barriers tells the real story of organisational capacity. In 2024, data quality was the primary obstacle to AI implementation.
By 2025, it’s shifted to human skillsets: 54% of organisations lack sufficient AI expertise.
But Potluri cuts through this excuse: “I suspect the real issue isn’t lack of skills, it’s lack of time to develop and apply those skills.”
Teams are so overwhelmed with managing complexity that they can’t step back to implement the solutions that could manage that complexity for them.
This is the innovation death spiral in pure form.
Businesses want AI-powered infrastructure automation, but they’re trapped in a cycle of vendor API management that consumes their bandwidth. They can’t automate because they’re too busy managing the complexity that automation was supposed to eliminate.
The F5 data showing that 95% of organisations are standardising with observability tools like OpenTelemetry offers a glimmer of sanity, but it’s overwhelmed by the chaos of everything else.
The Rebel Truth: What Actually Works
While your peers are drowning in complexity theater, rebels are building something different.
They’re not chasing every new technology or adding vendors to solve vendor problems.
They’re practicing radical simplification.
Truth #1: Simplify Before You Automate
The enterprises successfully implementing AI aren’t the ones with the biggest budgets or the most advanced infrastructure. They’re the ones that simplified their operational foundation first.
Potluri learned this the hard way: “You can’t effectively automate chaos – you have to organise it first.”
When 93% of organisations now generate revenue through digital applications, up from just 79% two years ago, complexity becomes a direct threat to business continuity.
You can’t afford operational chaos when your revenue depends on digital infrastructure.
The rebel approach? Audit your API landscape ruthlessly.
Question whether each API represents truly necessary functionality or just accumulated technical debt. In Potluri’s experience with enterprise customers, teams manage dozens of different APIs just for application delivery and security.
Every API represents operational overhead. Most represent waste.
Truth #2: Vendor Consolidation Over Vendor Proliferation
Resist the urge to add more vendors when existing ones aren’t meeting your needs.
The A10 data shows organisations managing relationships with multiple ADC providers, often out of frustration with their primary vendor.
But vendor proliferation is complexity proliferation.
Instead of adding another vendor to your stack, invest time in fixing the relationships you have or making deliberate vendor consolidation decisions. When evaluating new tools or vendors, ask one question: “Will this reduce or increase our operational complexity?”
If the answer isn’t clearly “reduce,” don’t implement it.
Truth #3: Focus on Business Problems, Not Technology Trends
Fractional CIO Taffet gets it right when the pressure mounts: “The fact that technology is changing so fast is not really anything that I focus on. I still have to focus on the business problem first and then apply the right technology to the problem. So if I have something that is working and is meeting the business requirements, it’s not automatically replaced because the technology changes.”
This is rebel thinking in its purest form.
While everyone else is chasing innovation theater, rebels are asking: “What business problem are we actually solving?”
Eric Bloom from the IT Management and Leadership Institute drops the uncomfortable truth: rapid solution turnover is driven more by FOMO than need, and “generally does not deliver any benefits or ROI.”
The organisations with the lowest buyer’s remorse rates? Those with CIOs who understand business objectives and have solid processes to evaluate whether existing solutions meet business needs before chasing new ones.
Truth #4: Standardisation Enables Innovation
The F5 research shows the path forward: automation has become the top use case for operational telemetry. Businesses are moving beyond using data just for alerts – they want it to drive automated responses.
But you can’t automate effectively across a chaotic vendor landscape with dozens of different APIs and integration points.
Standardisation creates the foundation for automation. When 95% of organizations standardise with observability tools like OpenTelemetry, they create the consistent data foundation that makes AI-powered automation possible.
Rebels standardise ruthlessly, then automate systematically.
Truth #5: Treat Infrastructure as Architecture, Not Collection
Every technology decision should be evaluated as an architectural choice that either reduces or increases operational complexity.
Potluri’s approach in leading F5’s BIG-IP management plane architecture: “Rather than adding more features that require more configuration, we’re working on intelligent defaults and automated policy management that reduce the number of decisions operators need to make manually.”
This is architectural thinking applied to vendor relationships.
Instead of accumulating tools and vendors, rebels are deliberately architecting for operational simplicity.
The shift from reactive to proactive operations requires discipline, not just technology.
Truth #6: Time Horizons Matter More Than Technology Horizons
While Taffet proudly replaces solutions every couple of years, Enterprise Resource Planning (ERP) software in Fortune 100 companies has 15- to 20-year lifespans for a reason.
Core solutions that actually matter to business operations don’t turn over any more quickly today than they did five or 10 years ago.
The high cost, effort, and complexity associated with implementing new core systems means the decision to replace isn’t made lightly or quickly.
Rebels understand that some technology should have long lifecycles. The art is knowing which technology deserves long-term commitment and which should be treated as disposable.
The Choice: Rebel or Whither
We’re at an inflection point that will separate the organisations that successfully harness AI from those that remain trapped in complexity cycles.
The businesses that succeed with AI implementation will be those that solve their operational complexity first.
The data clearly shows us that businesses want AI to optimise application performance and handle security responses automatically.
But you can’t effectively automate systems you don’t fully control or understand.
From the trenches of enterprise infrastructure, the future is dividing into two camps:
- Businesses that simplify their infrastructure to enable AI capabilities, and
- Businesses that remain trapped in complexity cycles that prevent them from using the very technologies they’re implementing.
The gap between these two groups will only widen as AI becomes more central to business operations.
The uncomfortable reality is that most enterprises are choosing the complexity trap.
They’re adding more vendors to solve vendor problems. They’re implementing more tools to manage the tools they already can’t manage. And they’re chasing innovation theater while their revenue-generating applications run on infrastructure held together with manual processes and emergency fixes.
Meanwhile, rebels are making the hard choices. They’re saying no to vendor proliferation. They’re focusing on business problems instead of technology trends. And they’re standardising before automating. They’re treating infrastructure decisions as architectural choices.
The irony of our current moment is that we have the tools to solve our operational problems, but our operational problems prevent us from using those tools.
Breaking this cycle requires discipline, not just technology.
Your consultants won’t tell you this because their revenue depends on complexity. Your vendors won’t tell you this because their growth depends on proliferation. Unfortunately, your peers won’t tell you this, because admitting the problem means admitting their transformation initiatives are contributing to the chaos.
But rebels know the truth: The path out of the complexity trap isn’t more technology: it’s more discipline.
The question isn’t whether you can afford to simplify.
The question is whether you can afford not to.
Choose simplification and to solve business problems instead of chasing technology trends.
Or watch AI pass you by while you’re stuck managing the complexity that was supposed to enable your AI strategy.
The choice is yours. But choose quickly.
The rebels are already building what comes next.
