How do I know if my branch managers are actually blocking AI adoption?

Look at usage by branch, not by company. If one branch shows 80% weekly logins and another shows 20%, the tool is not the problem. The manager is. Pull the usage report your vendor already has and sort it by location. The pattern shows up in about ten minutes.

Should I train recruiters or managers first on a new AI tool?

Managers first, and it is not close. If you train recruiters while their manager stays neutral, the recruiter goes back to a boss who does not use the tool and does not ask about it. That signal kills adoption fast. Train the manager, get them using it in front of their team, then train the team.

What if my branch managers do not have time to champion a new tool?

Then the rollout will fail, and you should delay it until they do. A manager who is buried will not lead change. Cut their req load, pull a distraction, or push the launch back a month. Pretending they have capacity they do not have is how you burn a tool budget.

Why AI Rollouts Stall at the Branch Manager Level

Nearly every staffing firm bought an AI tool this year. Most rollouts collapsed mid-flight. The reason is not the tool or the recruiter. It is the branch manager, and the data proves it.

Almost every staffing firm bought an AI tool in the last 12 months. Most of those rollouts are already dead. The tool still shows up on the invoice, but nobody uses it past the first three weeks.

The easy story is that the tool was bad. That is almost never true. The real story is quieter and more expensive. Your rollout did not stall at the recruiter. It stalled at the branch manager.

Data shared at Bullhorn Engage Boston 2026 lines up with broader enterprise AI adoption research on one point. Only 35% of employees say their manager is an AI champion. Read that again. Two out of three of your people look up at their boss and see someone who is neutral or skeptical about the tool you just paid for.

That is your bottleneck. Not the software. Not the recruiter who says they are too busy. The manager standing between them.

Why the branch manager decides everything

A recruiter watches their manager for signals all day. What gets praised. What gets ignored. What the manager actually does versus what corporate sent in an email.

When you launch an AI tool, the recruiter runs a fast test. Does my manager use this? Does my manager ask about it in our one-on-one? Does my manager care if I skip it? If the answers are no, no, and no, the recruiter goes back to the old way by Friday. They are not lazy. They are reading the room correctly.

This is why company-wide training fails. You put 200 recruiters in a webinar, they nod, and then they return to 40 different branches. In 14 of those branches the manager is fired up. In 26 the manager shrugs. Adoption follows the manager, not the webinar.

The unit of change is the branch. The lever inside the branch is the manager. If you aim your rollout at recruiters, you are aiming at the wrong target.

What most firms get backward

Here is the common rollout plan. Buy the tool. Send a company announcement. Schedule recruiter training. Track logins. Wonder why logins drop.

Notice what is missing. Nobody prepared the managers to lead. They got the same email the recruiters got. They were treated as message-forwarders, not as the people who make or break the whole thing.

A branch manager who is not ready does three things that quietly kill your investment. They stay silent in team meetings, which reads as disapproval. They keep measuring their team on the old process, so the new tool feels like extra work with no reward. And they never use the tool themselves, so they cannot answer a single question when a recruiter hits friction.

You cannot fix that with a better recruiter training deck. You fix it by making the manager ready first.

The Build. Change. Adopt. view of manager readiness

My framework has three stages. Build the thing. Change how people work. Adopt it so it sticks. Most firms spend 90% of their energy on Build and almost nothing on Change. Manager readiness lives in the Change stage, and it is the part everyone skips.

Change work is not a webinar. It is getting a specific manager to do specific things in front of their specific team. Here is what that looks like in practice.

The manager uses the tool first. Before a single recruiter is trained, the branch manager should have logged in, run a real task, and hit the rough edges. A manager who has used it can coach it. A manager who has not will dodge every question.
The manager sets one visible expectation. Not ten. One. For example: every new req gets sourced through the AI tool first for the next 30 days. Clear, measurable, easy to check.
The manager talks about it weekly. In the team huddle, in one-on-ones, in the numbers they review. If the manager stops mentioning it, the team stops using it. Attention is the fuel.
The manager praises the early adopter out loud. When one recruiter closes a placement faster because of the tool, the manager names it in front of the team. That one moment does more than any training video.

None of this is complicated. It is just work that nobody assigns because everybody assumes the recruiter is the unit of change. They are not.

How to spot a stalled rollout before it dies

You do not need a survey to find your bottleneck. You need the usage report your vendor already produces. Sort it by branch, not by company.

You will see a split. A few branches at 70% or higher weekly use. A cluster in the middle. A tail of branches near zero. The tail is not a recruiter problem. It is a manager problem, and it is the same names every time.

Now overlay one more thing. Which of those low branches has a manager who has personally logged into the tool in the last two weeks? I will bet the answer is almost none of them. The correlation is that clean. Managers who use it lead teams who use it.

That report is your map. It tells you exactly which managers to sit with and which branches to save.

Do this week

Pull your AI tool usage report and sort it by branch. Find your three lowest branches. For each one, check whether the branch manager has logged into the tool in the last 14 days.

Then book 30 minutes with each of those three managers. Do not scold them. Ask one question: what would you need to feel confident leading this with your team? Write down the answer. That list is your real rollout plan, and it is worth more than the deck you launched with.

Fix the manager and the branch follows. Skip the manager and you will be shopping for another tool next year, wondering why this one failed too.

Manager Readiness Is the Real Bottleneck: Why Your AI Rollout Stalls at the Branch Level