A few months back, I was on a check-in call with a CPA client of mine. She’d been using an AI inbox manager for a few weeks and we were walking through what was working and what wasn’t.
Midway through the call, she said something that’s stuck with me.
“I think I need people who are NOT seasoned. Because they don’t come in with those preconceived notions.”
She wasn’t complaining. She was having a genuine insight in real time.
Her senior bookkeepers… the ones with 10 or 15 years under their belts… kept dragging their feet with the AI tools. Not openly hostile, just passive. “I like checking it myself.” “What if it misses something?” They’d give it a try, notice one small thing it got wrong, and use that as proof it wasn’t ready.
Her junior staff? Two days. Done. Using it, trusting it, moving on.
The problem with expertise
Here’s what I think is happening.
When you get really good at something, you build systems inside your head. Not formal systems. Just… the way you do things. The order you check stuff in. The mental shortcuts you’ve developed. The feel for when something’s off.
That’s valuable. My client’s senior bookkeeper caught a $65K error last tax season that three other team members had missed. The client’s tax bill had been calculated at $90,000. Should have been $25,000. The preparer missed it. The reviewer missed it. A second reviewer missed it. She caught it in about 30 seconds because she knew the client well enough to know the number was wrong.
That’s expertise. Real expertise. Hard to replicate.
But the same pattern that makes expertise powerful also makes it resistant. When AI enters the picture, it doesn’t just change the tools. It changes where the skill lives. And that feels threatening to someone who’s spent years building competence in a specific way.
The junior person? They haven’t built that identity yet. The new tool isn’t replacing anything. It’s just… how they learn to do the job.
What this actually means for hiring and onboarding
I’m not saying you should replace experienced staff with fresh graduates and call it an AI strategy. That’s a terrible idea.
But I do think the client’s insight points to something real: the way you onboard people into AI tools matters a lot, and it probably needs to be different for different team members.
For newer staff, get out of the way. Give them the tool, a basic orientation, and let them explore. They’ll figure out where it helps fastest.
For experienced staff, you have to do the opposite. You have to explicitly honor what they already know. The framing isn’t “here’s a tool that will make your job easier.” It’s “you have expertise this tool doesn’t have. Here’s how we use the tool for the repetitive stuff so your expertise has more space to do what only you can do.”
That framing matters. Because it’s also true.
Before you automate: map it first
One thing I always tell my consulting clients is that AI adoption problems are usually workflow problems in disguise.
Before we build any agents or set up any automations, I want to do a process mapping session first. Literally get a visual of every step someone takes in their workflow. What happens when an email comes in? Who touches it? What decision gets made? Where does it go next?
Once you can see the whole workflow on a whiteboard or a screen, it becomes obvious where automation helps and where human judgment is non-negotiable. And that map is also the tool you use to show your experienced team: “Here are the parts we’re automating. Here’s the part where you’re still the expert.”
That conversation goes much better when people can see it.
The real question isn’t “will they adopt AI”
It’s “what are they afraid of losing?”
A front desk person who’s built a career on being the hub of information at a clinic… she’s afraid AI makes her redundant. A bookkeeper who’s proud of never missing an error… she’s afraid AI gets the credit for the work she’s been doing for 15 years.
Those fears are reasonable. They need to be addressed directly, not assumed away.
The clients I’ve seen do this well are the ones who bring their team into the process early. Not to teach them how to use the tool. To ask them: what are the parts of this job you hate? What takes the most time but adds the least satisfaction? Let’s start there.
When you automate the stuff they hate, it stops feeling like a threat. It starts feeling like a gift.
One thing to try
If you’re rolling out AI tools at your company and hitting resistance, try this before anything else.
Talk to the resistors one on one. Not about the tool. About their job. Ask them what parts of their week feel like a waste of their skill. Ask what they’d do with that time if the repetitive stuff disappeared.
You’ll probably find out the problem isn’t the tool at all.
And you’ll learn something useful about your own workflow in the process.
Thanh Pham runs AI workshops for business teams and consults on automation strategy. If you want help mapping your team’s workflows before rolling out AI tools, the workshop is a good place to start.
