AI Adoption Is Stuck Because Leaders Can’t Articulate the Real Problem

There's a question being asked in boardrooms across financial services, technology, and consulting firms right now. It sounds simple: "Why isn't our AI investment working?"

The answers you're hearing are probably familiar. Change management issues. Adoption resistance. Training gaps. Governance concerns. All true. All symptoms. None of them the actual disease.

The real problem has a name, though most leadership teams haven't heard it yet: the articulation problem. And it's costing you more than low utilisation rates. It's costing you the ability to move at the speed AI is now moving.

Founders spend too much time drafting the same kinds of messages. Wispr Flow turns spoken thinking into final-draft writing so you can record investor updates, product briefs, and run-of-the-mill status notes by voice. Use saved snippets for recurring intros, insert calendar links by voice, and keep comms consistent across the team. It preserves your tone, fixes punctuation, and formats lists so you send confident messages fast. Works on Mac, Windows, and iPhone. Try Wispr Flow for founders.

Start flowing free

When your VP of Operations says "we need better pipeline tracking," they believe they've articulated a clear need. They haven't. They've described a symptom of a workflow designed around constraints that no longer exist.

The real need might be "eliminate pipeline tracking entirely and automate qualification-to-close." But they can't say that. Not because they're hiding it, but because they don't know it's possible. And even if they suspected it was possible, they wouldn't know how to specify it without a mental model of agentic workflows they don't yet have.

This isn't a communication problem. It's a conceptual problem masquerading as a strategy problem.

Your teams are trying to adopt AI into operating models designed for pre-AI constraints. It's like asking someone in 1905 to articulate how electricity should change factory design when their entire mental model is built around water wheels and steam engines. They can tell you they want "better power distribution," but they can't tell you to redesign the entire facility around electrical motors because they've never seen it done.

The articulation problem doesn't get solved by more strategy documents. It gets solved by short, structured interventions that surface how work actually happens before anyone talks about tools. Most organisations skip this step and go straight to pilots. That's why the pilots don't scale.

You've spent six figures on AI tools. Usage is at 15%. Leadership wants answers. You've tried:

The Head of AI says "we need executive sponsorship." The Change Director says "we need better change management." The VP Operations says "we need clearer use cases." Risk says "we need better controls."

Everyone's right. No one can articulate what they actually need because the thing they need doesn't exist in their current frame of reference.

Here's what's really happening: AI is exposing that your "processes" were never really processes. They were collections of workarounds, tribal knowledge, exception handling, and political compromises that only worked because humans could navigate ambiguity.

When you try to codify them for an agent, there's nothing coherent to codify.

Let me tell you what's happening in the conversations AI Heads are having after hours, not in steering committee meetings:

"Our business processes were designed in 1997 and we don't know which ones AI fundamentally breaks."

"Middle managers are terrified and blocking everything, but we can't say that in front of executives."

"We're scared of liability but we don't actually know what we're liable for."

"We have no idea what to do first or how to sequence anything."

These are the real articulation failures. Not the inability to write a requirements document. The inability to surface the actual problem in a room where admitting you don't know costs you credibility.

So instead, we get theater. AI strategies that are really just lists of pilots. Roadmaps that are really just procurement timelines. Governance frameworks that are really just risk avoidance dressed up as controls.

Big Four consulting firms are selling 18-month implementation roadmaps. They can't tell you the truth: their entire business model is what's being disrupted. They're optimising for billable hours. AI destroys billable hours. They cannot be honest brokers.

AI vendors are shipping powerful tools and saying "you figure out how to use them." They're optimising for API consumption, not for helping you articulate what you actually need. Their incentive is token usage, not your transformation success.

Internal innovation teams are running pilots. Random acts of AI with no strategic coherence because they're politically weak, have no operational authority, and get blamed when adoption fails.

Change management consultancies are right that it's a people problem. They're wrong about the solution. You can't train people to imagine workflows they've never seen. Training doesn't fix articulation gaps.

While you're running another steering committee to discuss your AI strategy, here's what happened in the last 72 hours:

A markdown file, 200 lines of prompts from Anthropic, triggered a $285 billion market correction in enterprise software. Not because the technology was revolutionary. Because it made visible what the market had been quietly pricing in: the per-seat SaaS model is broken.

KPMG used AI as negotiating leverage to cut their audit fees by 14%. They didn't deploy AI. They didn't automate anything. They just pointed at the fact that AI exists and demanded price cuts. The tactic worked.

OpenAI shipped Codex, which generates production code at a thousand commits per hour. Cursor is shipping desktop apps end-to-end from prompts. The cost of building software is approaching zero.

This isn't coming. This happened this week.

Your 18-month AI roadmap was obsolete before you presented it. Your phased rollout strategy assumed you had time to figure out articulation. You don't.

The enterprises that will survive the next 18 months aren't the ones with the best AI strategy documents. They're the ones that created the conditions for honest articulation of the real problems.

This requires three things most organisations don't have:

1. Safety for middle managers to admit "I don't know what this breaks"

Your middle management layer, the people who actually understand how work gets done, are terrified. They see AI as a threat to their relevance. They're not wrong. But their fear is blocking the articulation you need.

You need structured environments where admitting uncertainty is rewarded, not punished. Where "I don't know how to redesign this workflow" is the starting point, not a career-limiting admission.

2. Access to the people who actually do the work, not just the people with titles

The VP doesn't know how the work actually happens. The person with "Senior Analyst" on their business card does. But that person rarely gets into the rooms where requirements are articulated.

Articulation requires surfacing organic leadership, the people who've built the workarounds and know where the bodies are buried. Your org chart doesn't identify them. Community engagement does.

3. Permission to redesign, not just optimise

Most AI initiatives fail because they're trying to optimise existing processes. "Take current workflow, add AI, get efficiency gains."

That's not transformation. That's decoration.

Real articulation starts with: "If we had unlimited interns who worked instantly for free, what would we change?" The answer to that question reveals what's actually valuable versus what's just human workaround.

Then you map agent capabilities against that redesigned workflow. The gap is your actual requirements. Now you can articulate.

We've spent 15 years inside financial services, working across transformation programs at HSBC, Mastercard, Bank of England, BMO Capital Markets. We've seen every flavor of failed change initiative.

What we've learned: community isn't a nice-to-have for adoption. It's the discovery mechanism that makes articulation possible.

The reason you can't articulate what you need is because the people doing the work can't talk to the people making decisions, and both are operating from outdated mental models.

Community creates the conditions for:

This isn't soft skills. This is the hard work of facilitated articulation through structured community engagement.

You've tried training. You've tried governance frameworks. You've tried pilots. Usage is still below 25%. Leadership wants answers you don't have.

This isn't a tooling problem. It's an articulation failure.

We run a 30-day intervention that:

No 18-month roadmaps. No phased rollouts. No more strategy documents.

If your AI usage is stuck below 25% and you're responsible for fixing it, let's talk.

Email: [email protected] Book 30 minutes: Zoom details

You already know if this is your situation. The only question is whether you're ready to fix it now or explain the delay in six months when the window has closed.

Emeka Ogbonnaya is the founder of BuildMoat, an AI transformation consultancy positioning community as the operating infrastructure for enterprise AI adoption. With 15+ years across major financial institutions, he helps organisations move from AI pilots to AI-native operating models.

Building human infrastructure for AI adoption isn't theory for us. It's what we do: champion networks, behavioural pilots, AI Adoption Offices. The MOAT Framework applied to real enterprises.

Questions about scaling AI adoption in your organisation? Book a call. We'll assess where you are and show you exactly what's missing.

Did someone forward this to you? Subscribe here for weekly insights on AI adoption that actually works.

Keep building,

BuildMoat
Human infrastructure for AI adoption