Accorda Advisory LLC · Camas, Washington

Why AI adoption fails when the technology works

The research puts the cause in the human layer rather than the technology.

70%

of AI value comes from workforce change.

  • 10% from the algorithms
  • 20% from technology implementation

BCG, AI Transformation Is a Workforce Transformation, February 2026

Which is why a company can have the tools installed, licensed and working exactly as sold, and still see nothing change in the work. In a founder-led company the pattern has its own shape, because what carried adoption at twenty people stops working once there are managers leading managers.

Why do AI initiatives stall, and how do you fix it?

Not for one reason. That is what makes it hard to fix. A stall is spread across all four PACE pillars at once, and each one is holding a different piece of it — which is why correcting the loudest problem so rarely changes anything.

How this gets found

A stall does not announce itself. From the inside it looks like ordinary friction — a slow quarter, a busy team, a tool nobody got round to. Nobody wakes up and calls it a stall.

So the work is to go looking in all four pillars rather than the one everybody is already arguing about, and to come back with counts instead of impressions. That is what the AI Adoption Gap Diagnostic™ is for: it names which pillar is carrying the strain, so the next twelve months of effort go where the return is not arriving instead of where it is easiest to spend.

The pattern underneath it is consistent. The budget goes where the value is not: licenses get bought, training gets scheduled, and the part that decides the outcome — whether people actually change how they work — gets left to happen on its own.

Three findings, from three different pillars:

  • It is human, not technical. 63% name human factors as the primary challenge. Prosci, 1,107 respondents. The obstacle was never the tool.
  • CEO accountability changes the result. Only 24% name the CEO or executive committee as ultimately accountable for AI-informed decisions. Where accountability does sit at CEO level, 57% report meaningful business value, against 21% where it does not — and are nearly four times likelier to report established ROI (14% against 4%). KPMG. Nearly triple the value, on ownership alone.
  • The perception gap. 75% of executives say their AI rollout succeeded. 45% of employees agree. EMARKETER and Writer. This is why a stall goes unnoticed. The people who would have to see it are the least likely to.

What if it is one team, not the whole company?

Why does a team agree
to a change and then
quietly not do it?

They say yes in the room. Then it quietly does not happen.

You do not need an organizational transformation for that. One team, one change, one thing being resisted. It is a smaller, cheaper piece of work and it starts at $350 — ninety minutes, a short assessment, and a written findings report you keep.

Read the long version

What are the four human barriers?

Resistance is rarely one thing, and the four causes need different responses. Nobody says any of these out loud. They sound like this on the inside.

  1. 01Identity threat

    “If the software does that part, what am I here for?”

    The role, not the job, is what feels at risk.

  2. 02Tech shame

    “I am not going to be the one who asks how it works.”

    Looking inadequate in front of peers is often a stronger fear than losing the job. It surfaces as a quiet preference for the old way, and it gets read as stubbornness.

  3. 03Cognitive overwhelm

    “I have not finished learning the last thing.”

    Too many tools, too fast, on top of the work that was already there.

  4. 04Lack of meaning

    “Nobody has told me what this is actually for.”

    With no stated purpose it reads as a cost exercise, and people brace accordingly.

All four get measured, not the loudest one. Each needs a different response, and a company that treats them as a single morale problem spends a year on the wrong fix.

Automation does not equal job loss. Tasks get replaced, roles evolve, and the human stays essential. Saying that plainly is most of what answers barrier 01.

How do you get employees to use AI?

The question skips a step, and it is the step that decides everything after it.

  • You cannot roll this down while the leadership team is not aligned. And they are almost never as aligned as they believe. Different executives quietly run different definitions of what AI is for, how far it is meant to go, and what happens to the people whose work it touches.
  • Employees hear all of those at once. What they respond to is the disagreement, not the plan.
  • So the first measurement is not of employees at all. The Accorda Leadership Index scores each executive individually, then shows where the team sits together and where it does not, including the gap between what the owners believe and what the executives and managers report. That gap is the finding, and it is almost always there.

So the answer to the question is an assessment, not a training plan. Either of two shapes:

  • One pillar, where you already know roughly where it hurts. A single domain assessment, scoped and priced, so you start where the strain actually is instead of buying a transformation programme.
  • All four, where you do not. The twelve-domain diagnostic reads every pillar and names the one carrying the strain, because the loudest complaint is usually not the constraint.

Underneath both sits the Accorda Leadership Index. It scores every executive and manager 1.0 to 5.0 across five dimensions, places each of them in one of four operating patterns, and shows the gap between what the owners believe and what their people report. That gap is what sets the pace everything else can move at.

What does an AI adoption assessment cover?

It starts by looking at what a person is protecting, rather than at the tool. That is the step almost every rollout skips.

People do not sustainably sacrifice their values. When someone believes there is only one way to protect what matters to them, resistance wins every time. They are not being stubborn, they are defending something real. Once they can see the value survives the new behavior, they choose the change themselves.

Protect the value.
Change the strategy.

The values people defend in a change like this are ordinary, and worth naming plainly.

  • contribution
  • competence
  • purpose
  • agency
  • belonging
  • recognition
  • security
  • autonomy
  • quality
  • predictability

ExampleA craftsperson resisting an AI draft is usually protecting quality. A long-tenured manager resisting a new workflow is often protecting competence. Neither of them is being difficult, and neither of them will say it out loud in those words.

Most of what gets called resistance is somebody carrying something they cannot name yet. Leading a team through an AI change you do not understand yet is the version of this written for the manager who was handed the rollout.

You do not remove the fear.
You give the value
a new way to survive.

What it actually looks at, pillar by pillar.

  • PPeople

    • What each person is protecting
    • Whether their expertise still counts
    • Reframing the belief underneath it
  • AAdaptive Culture

    • Where resistance is actually sitting
    • What gets rewarded against what was announced
    • Whether the culture can absorb change at all
  • CCapability

    • How the workflow gets redesigned around the tool
    • Who checks output before a customer sees it
    • What people are already using unapproved
  • EEvidence

    • One process measured before anything changes
    • A number that survives a budget conversation
    • The same instrument re-run afterwards

One more thing the assessment separates. The same visible behavior has three different causes, and each sits in a different pillar: People, where someone is defending whether their expertise still counts. Adaptive Culture, where it is not safe to try something and have it not work. Capability, where nobody was actually taught and saying so would cost them something. Guessing which one you are looking at is how a company spends a year on the wrong pillar, so the assessment reads all four rather than the one being complained about.

What happens in the workshop?

The diagnostic is what finds it, and what finally lets it be said out loud. The workshop is where it gets reframed and moved toward activation.

  • The reframe happens with the group, not to them. What the one-to-one conversations surfaced gets put in front of the team and worked in the room. The argument stops being about the tool and starts being about the value underneath it, which is the only version of the argument that can actually resolve.
  • Somebody skilled at moving a group from resistance to activation. That is the whole job. Not delivering content, not running an agenda. Taking a team that is quietly protecting something and getting them to move, in the room, while everyone watches it happen.
  • The outcome is movement, not a deck. You leave with the belief reframed and owners on the behaviors that change. Then the same instrument gets re-run a few months later to show whether it held.

The four moves it works through, on your own findings rather than a case study.

  1. 01Name what changesSay what actually changes about the role, rather than reassuring people nothing will.
  2. 02Permission to get it wrongLet people experiment without a penalty attached to a bad result.
  3. 03Start small enough to winKeep the first uses small enough to build confidence instead of confirming the fear.
  4. 04Make early movers better offThe people who try it first should be visibly better off for having done so.
And the order it runs in

People do not tell the person who signs their review what they are protecting. Not out of dishonesty. Naming it out loud feels like handing over leverage. So the work runs from the outside in.

  1. Outside. The first conversation is had by somebody with no stake in the org chart, who will not be in the room at anyone’s next performance cycle. That is usually the only way the real answer surfaces.
  2. Inside. It moves deliberately back in-house. A workshop gives the leadership team shared language for what was found, so the argument stops being about the tool and starts being about the value underneath it.
  3. One to one. Each executive and manager works it in their own department, because a manager in operations is protecting something different from a manager in sales.
  4. Re-scored. The same instrument, run again a few months later, after the new behavior has had time to either hold or quietly revert.

Anyone can run a workshop. Anyone can offer coaching. Step four is the one almost nobody does, and it is the only one that can tell you whether the first three worked. Without it you are holding a good day and a set of intentions.

Most executives have never been trained to run any of this. Not the one-to-one conversation that surfaces what somebody is protecting. Not reframing a belief a capable adult is actively defending. Not reading which of the four pillars a behavior is coming from when the same behavior has three different causes. That is not a gap in their ability. Nobody teaches it, because until recently nobody needed it.

Lesley Bodine, founder of Accorda Advisory LLC, Camas, Washington

Who runs this

The assessment is run by someone with no stake in your org chart

That is the point of it. People do not tell the person who signs their review what they are protecting, so the first conversation is had by an outsider who will not be in the room at anyone’s next performance cycle. I run every one of these myself.

About Lesley Bodine

Why do mid-level managers resist AI most?

Prosci’s research identifies mid-level managers as the most resistant group, and the reason is structural rather than personal.

They carry the change without having chosen it. They stay accountable for output while the method underneath is being rewritten. And a good deal of their authority was built on knowing the work better than the people they manage, so a tool that answers faster than they can lands very differently in that seat than it does in the executive suite.

Treating that as an attitude problem guarantees it stays one. Treating it as a role that needs redefining is what moves it.

Where it goes right, the difference shows up in daily use. BCG found 88% of managers at companies getting real AI value use it daily, against 25% at the laggards.

How this gets handled

Middle management is where communication stops being specific. The board hears a strategy. The floor hears a tool announcement. The layer in between is handed the job of turning one into the other, usually without being told what it means for the people they manage — or for their own role.

They are also the first to watch work get automated and often the last to be told what happens next. So they protect two things at once: their team, and their own position. Both are entirely rational responses to incomplete information, and most of us would do the same.

Which is why this reads as resistance and is usually something else. It is a communication gap wearing a behavior problem’s clothes — and the gap sits upstream of the manager, not in them. That is a People and Adaptive Culture finding, and it is one of the most common.

The Accorda Leadership Index scores each executive and manager individually, so the pattern shows up per person and per department instead of disappearing into a company-wide average. The work then happens where the vagueness actually starts, which is rarely where it is being felt.

Is AI adoption just change management?

Traditional change management assumes a defined end state with a finish line, which is exactly what makes a project plan work. You describe the destination, you move people to it, and you close the project.

AI does not offer a destination. Tools change monthly and use cases keep expanding, so there is no state to land in and declare finished. That makes adoption an ongoing transformation rather than a project that closes, and it needs a pace rather than a deadline.

Workplace paradigm shifts arrive roughly every fifteen to twenty years. The PC in the early eighties, the web in the mid-nineties, mobile in 2007. Almost nobody in the building has led an organization through one, which makes this a timing problem rather than a character problem.

Implementation has a deadline.
Adoption has a PACE.

See the four pillars and the twelve domains

What that looks like in practice

Change management runs a plan and reports whether the plan was completed. This measures which of the four pillars is under the most strain, works on that one, and then re-scores the same instrument a few months later.

The difference is what you are holding at the end. Not a record of activity, but a number that moved or did not, in your own reporting. Seeing where you actually stand is the first step.


The sources

  • 70% of AI value comes from workforce change

    10% from the algorithms, 20% from technology implementation.

    BCG, AI Transformation Is a Workforce Transformation, February 2026
  • 63% name human factors the primary challenge

    Roughly 38% of implementation difficulty is user proficiency against roughly 16% technical. Mid-level managers reported as most resistant.

    Prosci, n=1,107
  • 88% of managers at AI leaders use it daily

    Against 25% at laggard companies.

    BCG, Build for the Future x AI global study
  • 43% of U.S. employees never use AI

    One quarter strongly agree their organization has a clear AI plan.

    Gallup Panel, Workforce Study Q2 2026
  • 24% name the CEO or executive committee as accountable for AI-informed decisions

    Where accountability is clear at CEO level, 57% report meaningful value against 21% where it is not.

    KPMG Global AI Pulse Q2 2026, n=2,145
  • 75% of executives say the rollout succeeded

    45% of employees agree.

    EMARKETER and Writer, 2026

Start here

Find out where your adoption is actually breaking down.

If any of the four barriers sounded like your building, the Snapshot will tell you which one is widest. Five minutes, no sales call attached.

Not ready to talk yet

Get the next one in your inbox

People who find this page are usually reading something that finally names a piece nobody had named for them. Every week or two I publish one more of those — where AI adoption is actually breaking down inside companies, built from the research and from what I see in real leadership teams.

No pitch, no sequence designed to wear you down. If it stops being useful, one click and you are out.

Would you rather start with a read on your own organization? The AI Adoption Gap Snapshot™ takes five minutes and covers all twelve domains.