The Echo Chamber Gap
Your company doesn't have an AI adoption problem. It has a confusion problem.
I keep hearing the same conversation play out. Executives and tech leads are buzzing about AI. They attend conferences, trade case studies, share demos in Slack channels. They’re believers.
Then there’s the other 90%.
The frontline. The people who actually run the business day-to-day. Their reaction to “AI adoption” ranges from a polite nod to silent dread. “Not another change initiative. We just finished the last digital transformation. Can I just do my job?”
Both sides think they’re right. Both sides are. And neither side is talking about the same thing.
The confusion nobody names
BCG’s 2025 AI at Work report found that 78% of managers use generative AI regularly. Frontline workers? 51%. And that number hasn’t moved in two years.
That gap isn’t about training budgets or tool access. It’s about a fundamental confusion baked into how we talk about AI.
When leaders say “AI adoption,” they usually mean one thing: deploying AI-powered features. Chatbots. Prediction engines. Recommendation systems. AI as the product. AI as the solution.
But there’s a whole other side of AI adoption that most companies aren’t even naming. Using AI to build better things faster. Not AI as the thing your team interacts with. AI as the way you create what your team interacts with.
A better onboarding flow. A cleaner data pipeline. A dashboard that actually answers the question someone had. None of these are “AI solutions.” But all of them can be built in days instead of months when you use AI as a development tool.
The distinction matters. Because only one of these requires your entire team to change how they work.
Two kinds of AI adoption
Let me make this concrete.
AI as solution: You deploy a chatbot that handles customer inquiries. Your team needs to learn how to manage it, train it, handle escalations. The end user interacts with AI directly. This is what most people picture when they hear “AI adoption.”
AI as development tool: You use AI to build a custom scheduling system that eliminates the three-hour weekly coordination nightmare. The end user sees a clean interface. They never touch AI. They just get their time back.
Both are real AI adoption. Both create value. But they require completely different change management approaches.
The first one demands that the 90% learn something new, trust something unfamiliar, and change their daily habits. No wonder there’s resistance.
The second one? The 90% just gets better tools. Faster. Their workflow improves without them having to become AI-literate. The “what’s in it for me?” gets answered before anyone even asks the question.
Why the echo chamber persists
The 10% who are excited about AI tend to be excited about AI-as-solution. It’s the flashy stuff. The demos. The future-is-here moments. And they talk to each other constantly. Executives validate each other. Tech leads showcase possibilities. They’re in an echo chamber of excitement.
Meanwhile, the 90% hears “AI adoption” and braces for impact. Because to them, it means learning new tools, changing processes, and wondering if they’re being replaced. Their skepticism isn’t irrational. It’s information.
Gartner predicted that [at least 30% of generative AI projects would be abandoned after proof of concept by end of 2025, citing unclear business value and escalating costs. And that number only covers the projects that got started. It doesn’t count the ones that died in the echo chamber before anyone built anything.
The pattern repeats. Excitement at the top. Resistance at the bottom. Paralysis in the middle.
The bridge is in the reframe
When you stop asking “how do we get everyone to use AI?” and start asking “what problems are we actually solving?”, something shifts.
Some of those problems will be best solved by AI-powered features. Great. Build them. But a surprising number will be best solved by solutions that are built with AI but don’t require anyone to interact with AI at all.
BCG’s report landed on the same conclusion: “Real value is generated when businesses reshape their workflows end-to-end,” not when they simply introduce AI tools into existing ways of working.
This is the reframe that bridges the echo chamber gap. You stop selling AI to the 90%. You start solving their actual problems. Sometimes AI is the solution. Sometimes AI is just how you build the solution. The team doesn’t need to know or care which one it is. They just need things to work better.
What this looks like in practice
The companies getting this right don’t start with an AI strategy document. They start with a problem. One bottleneck. One process that eats time.
Then they build. Fast.
Day one, they expand the team’s understanding of what’s possible. Not a pitch about AI. A demonstration of what it can do for THEIR specific pain points. This is where eyes open. Where frontline workers say “wait, that thing I spend three hours on every week... you could fix that?”
Days two through five, they build the fix. Some outputs are AI-powered. Some are just built faster with AI. The team leaves with working software, not a slide deck about AI strategy.
The gap between the 10% and the 90% closes not through training or mandates. It closes through proof. Through someone’s daily friction disappearing. Through getting their time back.
The question to bring to your next leadership meeting
Stop debating whether your company should “adopt AI.” That question is too vague to be useful.
Ask instead: what are the three biggest time-wasters for our frontline teams right now? Then ask: for each one, is the answer an AI-powered feature, or is it a solution that could be built faster with AI?
That distinction changes the conversation. It moves from “how do we get people to use AI” to “how do we solve problems faster.” One creates resistance. The other creates results.
The echo chamber gap doesn’t close with more excitement from the top. It closes when the 90% starts seeing their problems disappear.
And sometimes the best AI adoption happens when nobody even realizes AI was involved.
Damian Nomura helps scaling startups close the capability gap in a week. No slide decks. Working software. Follow for more.