Your Managers Are the Bottleneck (And the Breakthrough) for AI

A lot of AI strategy still gets discussed at the wrong altitude.

Boards talk about platforms. Executives talk about investment. Tech teams talk about deployment. Everyone talks about adoption. Then the whole thing gets handed down into teams as if the hard part is done.

It is not.

The hard part begins when AI meets actual work. When someone has to decide whether to trust the output. When a team has to work out what good use looks like. When the first person quietly wonders whether they're falling behind because everyone else seems more fluent. When output goes up, but thinking gets messier. That is where AI either becomes useful or quietly starts creating drag.

And that is why managers matter so much.

Managers are the design layer between AI strategy and worker reality.

They're the people who translate a broad push into day-to-day norms, judgment, support, and boundaries. If they do that well, AI becomes more usable, more grounded, and less mentally taxing. If they do it badly, or they're left to avoid it altogether, people get stranded.

The Harvard Business Review "brain fry" study makes this point clearly. Workers whose managers take the time to answer their questions about AI report 15% lower mental fatigue than those whose managers do not. When managers expect people to work it out on their own, mental fatigue rises by 5%. The study calls it a small but measurable AI orphan tax.

That is not a training footnote.

That is a management signal.

The manager effect is not subtle

One of the most useful things about the Harvard Business Review research is that it moves this conversation away from vague instinct and into something much more concrete. It shows that mental fatigue with AI is not just about how many tools a person uses, or whether they personally like the technology. It is shaped by the environment around them, including what their manager does.

The same study found that the most mentally taxing form of AI use is not AI itself, but the oversight it requires.

It also found that when AI increases workload rather than reducing it, cognitive strain rises again.

That helps explain why manager support matters so much.

When AI arrives in a team, people do not just need access. They need interpretation. They need help knowing what this tool is for, when to use it, when not to use it, what good use looks like, and what still needs human judgment. They need someone who can make the rules of engagement visible.

That someone is usually the manager.

If the manager is present, AI becomes easier to place. If the manager is absent, AI becomes another source of noise, pressure, and second-guessing.

The AI orphan tax is what happens when leaders skip the middle layer

We think the phrase AI orphan tax is useful because it names something a lot of organisations are creating without meaning to.

They roll out the tools. They set a broad expectation that people should use them. They talk about productivity, speed, and innovation. Then they leave managers and teams to work out the rest themselves.

That gap does not stay empty for long.

People start improvising. One team uses AI heavily. Another barely touches it. Some managers are curious and engaged. Others are silent because they are unsure themselves. Some workers ask questions and get help. Others decide it is safer to stay quiet and figure it out alone.

That inconsistency becomes a tax.

It shows up as fatigue. It shows up as hesitation. It shows up as people doing extra cognitive work just to navigate the ambiguity. And because the expectations are often implicit rather than explicit, the burden sits with the worker.

The research makes that visible. When managers answer AI questions, mental fatigue drops. When managers expect employees to figure it out alone, fatigue rises.

That is the orphan tax.

Not because people are incapable, but because they have been left without a design layer between the tool and the work.

Team pressure makes it worse. Organised integration makes it better

The Harvard Business Review data does something else that leaders should pay close attention to. It shows that team conditions matter almost as much as manager behaviour.

When employees feel team pressure to use AI, mental fatigue goes up. The same happens when there is big variation in AI use across the team.

By contrast, when teams have organised integration of AI into their processes, mental strain drops. The study suggests that group norms can either reinforce productive use or create unhealthy pressure and confusion.

That is a management issue too.

Managers shape team norms. They decide whether AI becomes a status game, an unspoken competition, or a shared capability. They decide whether the team has a clear workflow or a patchwork of individual experiments. They decide whether people feel safe asking basic questions or feel they should already know the answers.

This is why we would argue the manager is not just a support role in AI implementation.

The manager is the operating system for it. They determine whether AI lands as organised integration or scattered pressure.

Most leaders still are not equipped for this part

The Deloitte 2026 Global Human Capital Trends Report makes that gap hard to ignore.

Deloitte is blunt on the consequence: most organisations are still designing work for people and technology separately, rather than designing for both together.

That is a serious problem, because AI does not fail only at the strategy level. It fails in the handoff between strategy and work.

And that handoff usually belongs to managers.

If only a small minority of leaders are adept at shaping human and AI interaction, then most managers are being asked to guide teams through something they have not themselves been prepared to design. Deloitte also points to this more broadly, noting that some organisations are not giving managers the tools they need to make effective decisions around how work is distributed.

So now we have a pattern.

Workers are already using AI.

Mental fatigue rises when AI oversight and workload rise.

Mental fatigue falls when managers engage.

Yet most leaders are not confident at shaping human and AI interaction.

That is not a tooling issue. That is a management capability issue.

This is why managers are both the bottleneck and the breakthrough

When organisations say AI is not delivering what they hoped, they often look first at the technology, the vendor, the budget, or the use case. Sometimes that is fair. But often the real issue is simpler.

The managers were never brought properly into the design.

They were expected to enforce adoption without being shown how to redesign work. They were given AI literacy when what they really needed was judgment, workflow design, and clearer decision rights. They were told to support innovation while managing rising ambiguity, hidden workload, and team anxiety.

That is why they become the bottleneck.

Not because managers are resistant by nature, but because they are carrying the unresolved middle layer of the rollout.

But the same thing makes them the breakthrough.

Because when managers are equipped to answer questions, set norms, reduce ambiguity, and embed AI into team processes rather than layer it on top, the whole experience changes. Mental fatigue drops. Use becomes more intentional. Teams stop treating AI as an individual differentiator and start treating it as a shared capability.

That is where the leverage is.

What managers actually need now

They need more than encouragement to experiment.

They need more than generic AI training.

And they definitely need more than a mandate to drive adoption.

They need the skills to design how their teams work with AI.

That includes knowing what work should shift to AI and what should stay human. It includes knowing when a human should override the tool. It includes setting clear expectations about workload, so people do not hear every productivity message as a signal that they should simply do more.

The Harvard Business Review study found that when employees felt their organisation expected more work because of AI, mental fatigue scores were 12% higher. It also found that people who felt their organisation valued work-life balance had 28% lower mental fatigue.

Those are management issues.

Managers need to know how to make good use easier, not just more likely. They need to know how to reduce cognitive load, not add to it. They need to know how to turn AI from private improvisation into shared practice.

You cannot design this from a dashboard

Here is the difficulty. Everything described above is invisible to the way most organisations currently measure AI.

They can tell you what tools are licensed. They can tell you who has access. They can tell you how many prompts are being run, how many pilots are active, or how many use cases are in flight.

None of that tells you whether a manager answered the question, or whether the person stopped asking.

Adoption metrics tell you who logged in. They tell you nothing about who felt able to say "I'm not sure about this."

You also cannot get at it with a survey, because you are asking people to report on the exact thing they have decided not to raise. Someone who has quietly concluded it is safer to work it out alone is unlikely to say so on a form.

So you have to watch what actually happens instead.

That is what the AI Readiness Experiment is built to do. It puts people on a real work problem for ten days, using AI, under real constraints, and captures what happens: where AI creates genuine value, where it creates rework and checking burden, where people struggle to verify an output, and where human judgment is quietly overriding the machine.

It also surfaces the conditions around the work. Where roles are unclear. Where demands are already too high. Where there is no time to test anything properly. Where support is thin. Those are the same conditions that determine whether a manager can do the job this article describes — and they show up in what people choose to work on, not in what they say about it.

That's why this matters so much.

Your managers are already shaping your AI rollout, whether you have prepared them for that role or not.

The only question is whether they are doing it by design or by accident.

If you want to know whether your managers are acting as a multiplier or a bottleneck, the AI Readiness Experiment is where to start. It will show you where your managers are already carrying the rollout, and where they need support to carry it well.