How to unfreeze managers and get AI deployed

Your AI strategy has stalled – not because of the technology, but because of the people expected to make it work.

Leadership approved the budget months ago and the roadmap exists. But execution breaks down in the middle layer, where managers nod in meetings then retreat to business as usual. See what aibl’s research found about manager-layer resistance for the research behind this.

At aibl we see this pattern constantly. One transformation lead put it plainly: “It’s a classic case of the Emperor’s new clothes. No one wants to admit they’re not quite sure of the outcomes they want.” Managers speak confidently about AI in meetings, then default to familiar workflows the moment they’re back at their desks.

It looks like resistance to change, but really they’re rational actors stepping into risk without cover.

Why managers protect legacy workflows

Managers worry AI will expose how their teams have been operating. If a tool can handle work that took three people and careful coordination, it raises uncomfortable questions – what was genuinely complex, and what was just an inherited process?

The ‘not my role’ defence also shows up constantly. Why should partnership managers whose stated job is to manage client relationships care about building automated workflows?

It means conversations about how roles will change haven’t happened yet. If you can’t explain how AI changes good performance, experimentation feels like someone else’s risk. And if you’re still evaluating teams on legacy KPIs, nothing changes.

The real stall begins higher up, even if it’s unintentional. Leaders want transformation without making the trade-offs that redesign requires.

Few leaders say “here are new tools, and here are new metrics to match.” They rarely admit integrating anything new means a dip in performance and productivity or build that awareness into the plan. Instead managers get judged on established outputs with no slack or incentive to try something new.

Why accountability without authority freezes adoption

Another barrier is control. Middle managers carry accountability for delivering on AI ambitions. But they’re adopting tools they didn’t choose, integrating them into workflows designed by someone else.

Leadership has an opaque view of what this looks like operationally, and managers are left to make sense of it alone. One automation lead described the scale of support needed: “It doesn’t just take the middle management to say yeah, I will actually do this, I will have the tough conversations, I will figure out how I will upskill by signing up to these classes. But you also need HR involved. You need business partners. You really need everyone on board. That’s really tough.”

Training helps, but it won’t shift behaviour on its own. This is a confidence problem wrapped in a structural one.”

How to get managers building

Mandate building to tackle exposure fears head on. This works best when leaders show how they’re using AI themselves, in real time, outside of polished demos where mistakes are inevitable.

When a CEO struggles in public to make something work, it normalises not knowing and removes the shame from experimentation. The team sees that being a novice is part of the process, not a disqualification.

Another approach is to pair builders with sceptics. At aibl we pair technical teams with finance or operations to demystify what’s possible and translate capability into business terms.

When a finance lead works alongside someone who can build, ‘AI in my function’ stops being abstract – it becomes specific automation they can see running. These partnerships handle both the knowledge transfer and the ownership problem.

Changing what you measure also creates slack. Adjust expectations to include building and experimentation. Or create protected time so trying something new doesn’t compete with this quarter’s numbers.

We’ve tested this approach repeatedly with mid-market teams. Require everyone, including the C-suite, to build something and present it. What changes isn’t the quality – it’s the shared understanding that building is now part of the role.

What to do Monday morning

Pick one function lead. Ask them to build one small workflow improvement using AI and show it back to their peers.

Not a strategy deck or plan – an actual thing that works, even if it’s rough.

Then ask what metric would change so that work counts as part of their job, not a side project. Your middle managers will either carry your strategy forward or slow it down. The question is whether you’re willing to unfreeze them.

Frequently asked questions

Why do middle managers stall AI adoption?

Managers carry the delivery risk, so a tool that threatens their targets or adds uncertainty gets quietly resisted. This frozen middle is usually rational caution rather than obstruction, and it blocks rollouts that leadership has already backed.

How do you get managers to back an AI rollout?

Tie the change to their targets, give them a safe way to test it, and remove the downside if it underperforms. Managers move when the tool clearly helps them hit their numbers rather than adding risk they own alone.

What is the frozen middle in AI adoption?

It is the layer of managers between strategy and delivery where AI initiatives stall. Leadership approves and teams are willing, but managers who answer for results hold back until the change is proven safe for their objectives.