Your C-Suite Loves AI. Your Frontline Doesn't Trust It Yet. That Gap Is an HR Problem.

A VP told me last month that their company had "cracked" AI adoption. Rollout numbers were up, the town hall got good reactions, and leadership felt genuinely energized about what was coming next. Then I sat in on a skip-level with a group of coordinators and claims processors, and the mood was completely different. Nobody said they hated AI. What they said, more than once, was some version of: "I don't know what this means for my job, and nobody's told me."

Those are two different companies living in the same building.

The Gap Is Real, and It's Not About the Technology

Recent workforce research has found something close to a 50-point gap between how engaged senior leaders feel about AI and how engaged entry-level employees feel about it — roughly three out of four executives reporting real enthusiasm, against roughly one in four frontline and early-career employees saying the same. When I read numbers like that, my first thought isn't "we need better AI training." It's: who got asked what they thought before this rolled out, and who found out about it in a company-wide email?

That's the part that gets missed. The anxiety isn't really about the tool. It's about being on the receiving end of a decision instead of part of making it. Executives who are excited about AI got to shape the pilot, choose the vendor, sit in the room where the ROI case got made. The person whose job is to process the claims that AI is now drafting first got none of that. They got a rollout date.

What This Looks Like on the Ground

I've had three separate conversations this quarter with employees who used almost identical language: "I feel like I'm training my replacement." I don't think that's paranoia. I think it's a reasonable read of a situation where the tool showed up, the "efficiency gains" got announced publicly, and no one from leadership said out loud what happens to the people whose efficiency just got gained.

Here's what I mean by psychological safety in this context, because I don't want to just drop the term and move on: it's whether an employee believes they can ask "does this replace me?" out loud, in a real meeting, and get an honest answer instead of a reassurance that avoids the question. Most companies I've worked with can't currently pass that test. Leadership either hasn't decided the answer yet, or has decided and hasn't said it plainly, and either way, the silence reads as confirmation of the worst-case scenario.

What Actually Closes the Gap

This isn't solved with a lunch-and-learn on prompt engineering. A few things I've seen actually move the needle:

Tell people what the tool is for, not just what it does. "This AI drafts your first-pass claim summary" is a feature description. "This AI exists to take the repetitive 40% of your job off your plate so you can spend more time on the calls that actually need a human" is a purpose. Employees can work with a purpose. They can't work with a black box that showed up on their desktop.

Put frontline employees in the pilot, not just the rollout. If the first time a claims processor sees the tool is the week it goes live company-wide, you've already told them their judgment about how it should work doesn't matter. Bring them in early. Let them break it. Let their feedback actually change something, and tell them when it does.

Say the hard thing about jobs, even if the answer is uncomfortable. If roles are going to shrink or shift, say so, and say what the plan is for the people affected — retraining, redeployment, timeline. If you genuinely don't know yet, say that too. What you can't do is let people fill the silence with their own worst assumptions, because they will, and they'll be right to.

The Part Leadership Usually Skips

The confidence gap between the C-suite and the frontline isn't just an engagement metric. It's a trust metric, and trust is the thing HR is actually supposed to be protecting. Every company I've seen roll out AI well — meaning employees stayed engaged instead of disengaging quietly — treated the people most affected by the change as people whose input mattered, not just people who needed to be informed after the decision was already made.

The VP who told me they'd "cracked" AI adoption wasn't lying. Their numbers were real. But the coordinators in that skip-level weren't wrong either. Both things were true at once, and that's usually how it goes when the people making the decision and the people living with it never actually talked to each other.

If your AI rollout is going well at the top and quiet at the bottom, that's not a training gap. That's a conversation you haven't had yet.

Questions? Reach out anytime.

support@workplayengage.store

WorkPlayEngage is a product of Dieza Publishing. © 2026 WorkPlayEngage. All rights reserved.

Privacy & Security Note: WorkPlayEngage templates are native Google Sheets. We do not host your data, and we never have access to your employee names or internal metrics. Your engagement remains 100% private within your organization’s Google Drive.

Play:
Baby Pool
NFL Survivor Pool (Coming Soon)
Super Bowl Squares (Coming Soon)
Office Bingo (Coming Soon)

Learn:
How It Works
Shop
Baby Pool
Big Guess
Our Story

Blog:
Employee Engagement
HR Operations
Office Culture
Games & Activities
Whitepapers & Guides

Help

WorkPlayEngage:
Our Story
Contact Us
Blog
Privacy Policy