AI adoption Has Two Failure Modes, and They Share a Root Cause.

Written By Max Vitro

My last article argued that AI adoption fails because organizations treat it as a tooling problem when it is closer to identity work. People resist not because they can't learn the tool, but because the tool threatens their autonomy and their sense of being valued for their judgment.

That covered one way adoption fails. Resistance. Refusal. Shadow AI. Sabotage.

There is a second way, and it is the opposite of resistance. It happens inside teams that adopted enthusiastically, hit their usage targets, and look like success stories on the dashboard. The research is only months old, which is part of why most companies can't see it yet.

Both failure modes come from the same place. To explain how, I need to start with a concept that predates AI by decades.


Adoption is cognitive offloading

Cognitive offloading is the use of external tools to carry out mental work the brain would otherwise do. Writing a phone number down instead of memorizing it is cognitive offloading. So is using a calculator, a calendar, or a grocery list. We have been doing it for as long as we have had tools.

AI offloading is different in three specific ways.

A calculator offloads arithmetic. A calendar offloads memory of dates. Each tool offloads one narrow function, and you stay in charge of everything around it. AI offers to offload across every domain at once: writing, analysis, judgment, and decision-making. There is no natural boundary on what you can hand over.

AI output looks finished. A calculator returns a number you still have to interpret. AI returns a polished paragraph, a confident recommendation, a complete answer. The polish signals "done," which lowers the felt need to check.

And AI is confidently wrong at unpredictable moments. A calculator that says 7 is right. An AI that says the contract clause is enforceable might be right, or might be inventing case law, and it delivers both with identical confidence. The signal that usually tells you to slow down and verify is absent.

When an organization pushes adoption, it is pushing cognitive offloading at scale, into a workforce and a set of workflows that were not redesigned to manage it. That is the root cause. Everything below is a downstream effect.


Three responses to offloading

People respond to large-scale cognitive offloading in three ways. The first is the subject of my last article. The other two are the subject of this one.

Response one: rejection

Some workers refuse to offload. They experience the demand to hand cognitive work to AI as a threat to their autonomy, their expertise, or their professional identity, and they push back. This is the resistance failure mode: the sabotage, the shadow AI, the quiet non-adoption documented in the Writer/Workplace Intelligence 2026 survey, where 29% of employees admitted to actively working against their company's AI strategy.

Reactance theory (Brehm, 1966) predicted this sixty years ago. Restrict someone's autonomy and they act to restore it. Most AI rollouts restrict autonomy by mandate, then are surprised by the reaction.


Response two: strained acceptance

Some workers accept the offloading but keep trying to oversee it, and the oversight load breaks them.

In a March 2026 BCG Henderson Institute study of 1,488 US workers (published in Harvard Business Review), 14% of AI users reported what the researchers named "brain fry": mental fatigue from oversight of AI tools beyond their cognitive capacity. Those workers showed 33% more decision fatigue and 39% more major errors than colleagues without it. 34% intended to quit.

The BCG team found a threshold effect. Productivity rose with up to three AI tools and fell off once workers were managing four or more. Each additional tool is another output to verify, another interface to track, another source of plausible-looking error to catch. The worker is still doing the cognitive work. They are doing more of it than before, because now they are thinking and supervising a machine that thinks differently than they do.

Brain fry is what offloading does to a worker who refuses to fully let go. They hold onto their judgment and pay for it in exhaustion.


Response three: disengaged acceptance

Some workers accept the offloading and stop overseeing it. This is the failure mode with the newest name and the sharpest edge.

Wharton researchers Steven Shaw and Gideon Nave (January 2026) call it cognitive surrender: adopting AI outputs with minimal scrutiny, overriding both intuition and deliberation. Across three preregistered experiments with 1,372 participants and 9,593 trials, they manipulated whether an AI assistant gave correct or incorrect answers. Participants consulted the AI on most trials. When it was accurate, their accuracy rose 25 points. When it was faulty, their accuracy fell 15 points.

People adopted wrong answers because the AI supplied them. Not because they were tired. Because they had stopped checking.

Shaw and Nave frame this with what they call Tri-System Theory. Classic psychology describes two modes of thinking: System 1, fast and intuitive, and System 2, slow and deliberate. They propose a System 3: artificial cognition that sits outside the brain and can either supplement the other two or replace them. Cognitive surrender is System 3 supplanting System 2. The deliberation step doesn't happen because the machine appears to have already done it.

Their data points to who is most exposed. Participants with higher trust in AI and lower need for cognition surrendered more readily. The people most likely to stop thinking are the ones already inclined to find thinking effortful and to trust the machine that offers to do it for them.


Brain fry and cognitive surrender are not the same problem

This distinction matters because the two look identical on the surface and require opposite fixes.

Both produce uncritical acceptance of AI output. Both degrade quality. But brain fry is an overloaded oversight, and cognitive surrender is an abandoned oversight. One worker is drowning while trying to swim. The other has stopped swimming.

The mechanisms differ. Brain fry is a capacity problem: the worker wants to oversee and cannot keep up. Cognitive surrender is an engagement problem: the worker is not trying to oversee at all.

The antecedents differ. Brain fry comes from too many tools and too much oversight load. Cognitive surrender comes from high trust in AI and low need for cognition.

The observable signs differ. The brain-fried worker shows rework, errors, exhaustion, and intent to quit. The surrendered worker shows the opposite surface signs: fast turnaround, few corrections, apparent confidence, and a quiet collapse in decision quality that only shows up when the AI is wrong, and no one catches it.

Treat them the same, and you will prescribe the wrong fix for half your people. Give a brain-fried worker an engagement protocol, and you add load to someone already overloaded. Give a surrendered worker workload relief, and you remove the last friction that might have made them think.


Why do companies build a system that produces all three?

This is the part that should bother any leader running an AI program right now. The standard adoption playbook generates all three failure modes at once.

Adoption is mandated without redesigning roles. Workday's January 2026 research found that 89% of organizations have updated fewer than half of their roles to reflect what AI has changed about the work. The tool arrived. The job description, the workflow, and the cognitive demands did not move with it.

Success is measured by usage, not by judgment quality. Dashboards count logins, prompts, and self-reported time saved. The same Workday study found that while 85% of employees report saving time with AI, only 14% achieve a consistently net-positive outcome once rework is counted. Usage metrics see adoption working. They are blind to whether the work got better.

Failure is diagnosed as a skills gap. The widely cited MIT report on stalled enterprise AI framed the problem as a "learning gap" and pointed toward better tools and more training. Training addresses the rejection failure mode. It does nothing for brain fry, which is a load problem, or for cognitive surrender, which is an engagement problem. A worker who has surrendered their judgment does not need another prompt-engineering course.

So companies push adoption, reward usage, punish non-use, and train for skills. That approach manages exactly one of the three responses and actively worsens the other two. Mandates increase reactance. Usage rewards encourage the heavy tool stacking that produces brain fry. And nothing in the playbook even looks for cognitive surrender, because the surrendered worker hits every adoption metric the company is tracking.


Interventions, by failure mode

The fix is not less AI. It is designing the human system around the offloading instead of pretending the offloading is free.

For rejection, the interventions are the ones from my last article: autonomy-supportive communication, moral reframing in the employee's value vocabulary, procedural justice in how the rollout is decided, and self-affirmation before the tool is introduced. The goal is to lower the threat so the worker does not have to defend their autonomy by refusing.

For brain fry, the interventions reduce oversight load. Consolidate the tool stack, because the BCG threshold suggests three tools is roughly where useful turns harmful. Redesign workflows so a human is not the verification layer for every AI output. Reserve human oversight for the decisions where it changes the outcome, and let go of the ones where it does not. The BCG team found that using AI to remove routine work actually lowered burnout; the damage came specifically from oversight-heavy use. The target is the oversight, not the AI.

For cognitive surrender, the interventions force re-engagement. Build deliberate friction back into high-stakes decisions: a required step where the human states their own answer before seeing the AI's, so System 2 fires before System 3 can replace it. Design roles around judgment that the worker owns and is accountable for, rather than outputs they merely pass along. Watch for the workers Shaw and Nave flagged, the high-trust low-effort profile, and structure their work so disengagement is harder. Restoring some uncertainty to the AI's outputs, rather than presenting them as finished, helps too. The polish is part of what triggers the surrender.

Notice that the brain fry and cognitive surrender interventions point in opposite directions. One removes friction. One adds it. That is the whole reason the distinction matters.


The underlying move

Stop treating AI rollouts as software deployments. A software deployment asks whether people are using the tool. A cognitive architecture redesign asks what happens to human judgment when the tool is in the loop, and builds the roles, workflows, and incentives around that answer.

The companies struggling with AI are not struggling because they bought the wrong models or wrote the wrong prompts. They are struggling because they changed how cognition flows through the organization and never redesigned the organization around the change. They offloaded thinking at scale and assumed the thinking would take care of itself.

It will not. Some people refuse the offload. Some drown in overseeing it. Some disappear into it. The technology works fine. The human system underneath it is failing in three directions at once, and a better model fixes none of them.

What strikes me, reading this research next to my own work on why people resist vaccines, is how familiar the shape is. We keep building campaigns and rollouts around the thing we want people to do, and we keep getting blindsided by what the ask means to them. The leaders who get AI right over the next few years will not be the ones who bought the most licenses. They will be the ones who treated the rollout as a question about human judgment and designed for the answer.



Sources (or order as they appear)

Max Vitro
Next

AI Adoption Is Identity Work