Why Enterprises Keep Getting AI Wrong

Why Enterprises Keep Getting AI Wrong

You can see the full video here: Why Enterprises are Bad at AI

I do not believe enterprises struggle with AI because the technology itself is fundamentally lacking. The bigger issue is that most organizations are trying to apply AI on top of operational, architectural, and cultural problems they have never fully addressed. In other words, the failure is usually not the model. The failure is the enterprise.

I keep seeing the same pattern repeat itself. A company decides it needs an AI strategy because everyone else is talking about AI, the board wants to hear about AI, and competitors are making announcements about AI. That urgency creates movement, but not necessarily clarity. Teams rush into pilots, proof-of-concepts, and vendor conversations before they have defined the specific business problem they are trying to solve. When that happens, AI becomes an answer in search of a question, and that is almost always where the trouble begins.

What I find most troubling is how often enterprises assume AI can compensate for weak fundamentals. It cannot. If your data is fragmented, inconsistent, inaccessible, or poorly governed, AI will not repair that situation for you. If your business processes are bloated and inefficient, AI will not magically create discipline where none exists. If your systems are disconnected and your architecture is brittle, adding intelligence on top of that environment simply increases complexity. AI tends to amplify what is already there. If the enterprise is confused, the outcome will be confused as well.

This is why so many organizations end up disappointed. They expect AI to deliver transformative outcomes while ignoring the unglamorous work transformation actually requires. They want rapid results, but they are unwilling to invest in data quality, integration, governance, and process redesign. They want innovation without operational maturity. That is not a technology strategy. That is wishful thinking dressed up as strategy.

I also think many enterprises are still approaching AI with a dangerous amount of abstraction. They talk about “leveraging AI” in sweeping terms, but they do not narrow the discussion down to use cases that matter. They are not asking the practical questions that should come first. What problem are we solving? How will we measure success? What data do we need? What process changes must happen for this to work? How will this move from experiment to production? If those questions are not answered early, the initiative usually turns into an expensive exercise in corporate optimism.

Another issue is cost realism. Too many leaders talk about AI as if it is a relatively simple capability layer that can be dropped into the enterprise and immediately generate efficiency. That is not how this works. Real AI implementation requires investment, not just in tools, but in architecture, data pipelines, skilled people, testing, governance, and change management. If an enterprise is not prepared to fund the surrounding ecosystem, it should not expect AI to generate sustainable value. The return does not come from buying access to a model. It comes from building the conditions that allow the model to be useful.

Culture is part of the problem too, and I do not think that gets enough attention. Large organizations are often structurally resistant to the kind of speed and focus that AI adoption requires. They move through layers of approval, risk review, political negotiation, and committee-driven decision-making. A promising idea enters the organization with momentum and leaves it months later as a diluted pilot with no clear owner and no credible path to scale. By the time it reaches implementation, the energy is gone and the business case is weaker than when it started. Enterprises are not just slow in this space. In many cases, they are organized in ways that actively prevent success.

I am also skeptical of the obsession with large language models as the center of every enterprise AI conversation. The market has become fixated on the biggest, newest, most visible systems, and that has distorted expectations. The most effective use of AI in an enterprise may not come from a massive, generalized platform. It may come from a narrowly scoped solution that improves one operational workflow, reduces one category of friction, or helps one business function make faster and better decisions. That kind of practical, targeted implementation is often less glamorous, but it is far more likely to deliver measurable value.

To me, the gap between hype and execution is now the most important thing to understand. There is no shortage of enthusiasm for AI. There is no shortage of spending either. What is missing is discipline. Enterprises need to stop treating AI as a spectacle and start treating it as applied technology. That means aligning it to real business outcomes, building on clean and governed data, modernizing the surrounding architecture, and being honest about the amount of effort required to move from experimentation to production. Without that discipline, most AI programs will continue to generate more presentations than results.

I remain convinced that AI can create tremendous value for enterprises, but only when they abandon magical thinking. AI is not a shortcut around enterprise dysfunction. It is not a substitute for strategy. It is not a way to avoid the hard work of modernization. If anything, AI punishes organizations that try to cut corners. The enterprises that succeed will be the ones that understand their business clearly, clean up their operational foundations, choose use cases with real economic value, and implement AI with patience and rigor.

That is the central point I want to make. Enterprises are bad at AI not because AI is over, and not because the tools are useless, but because most companies are still approaching the problem backwards. They are starting with the excitement instead of the need, with the tool instead of the architecture, and with the narrative instead of the outcome. Until that changes, they will keep spending heavily, talking confidently, and wondering why the results never match the promise.

And also because they train their AI like humans with processes done for humans, instead of workflows, what AI needs

Like
Reply

This should be pinned to the top of every boardroom agenda. Rushing into AI to satisfy market pressure without fixing foundational architecture is the exact recipe for an operational and security crisis. When you layer autonomous agents or LLMs on top of disconnected systems and broken data plumbing, AI doesn't just amplify organizational inefficiency: it scales your attack surface. It transforms unmapped corporate data environments into unpredictable threat vectors, leaving the door wide open for severe data leakage and indirect prompt injections. True 'applied technology' requires architectural discipline. Real enterprise value—and real security—comes from doing the hard, foundational modernization work and wrapping strict governance boundaries around model execution before giving AI the keys to the kingdom.

Like
Reply

David Linthicum Increasing number of posts and articles basically saying similar things. Of course, your article articulates them very well ;-) Question is why does the enterprise keep making the same mistake? Those of us who have been around a while have seen this before. New tech, old mistakes. With AI, much bigger impacts. This isn't rocket science - it's largely common sense. I just don't get why "enterprises keep getting it wrong".

Like
Reply

Most “AI strategy” decks are really infrastructure debt with better fonts. If the data is bad, processes are political, and no one owns production outcomes, the model is not the strategy. It is just a very expensive mirror.

Most AI failures stem from weak enterprise discipline, not technology. Broken governance, poor data, and slow processes block real impact. Jumping in without clear problems leads to expensive experiments. True leaders modernize first, then apply AI where it solves value.

To view or add a comment, sign in

More articles by David Linthicum

Others also viewed

Explore content categories