AI Adoption Isn't About Training. It's About Trust: A Values-Based Framework
Your employees have been through three AI training sessions. They still aren't using the tools. The problem isn't what they know. It's what they feel.
Here's something that might help: The Trust Before Tools Framework. It's a sequence of four conversations you need to have before any AI rollout, and the order matters. I've watched organizations skip straight to the "here's how it works" training and then wonder why adoption stalled at 15%. The ones who get the sequence right see entirely different results. Let me show you why.
The Training Trap
There's a comfortable assumption in corporate America that goes something like this: if people aren't using a tool, they must not understand it. So we train them. We train them again. We create tip sheets and lunch-and-learns and Slack channels full of prompts.
And adoption numbers barely move.
A Microsoft Work Trend Index report found that while 75% of knowledge workers now use AI at work, nearly half of them are bringing their own tools rather than using what their company provides. Think about that. People are going around the official systems to use AI on their own terms.
That's not a knowledge gap. That's a trust gap.
When someone knows how to use a tool but chooses not to use the version you gave them, the training isn't the variable. The relationship is.
What Trust Actually Means Here
I work with the Valuegraphics Database, which tracks what matters to people across a million surveys in 152 languages. Not what they say matters. What actually drives their behavior?
When we look at AI adoption through this data, we see something interesting. The values that predict successful adoption aren't the ones you'd expect. It's not Ambition (ranked 33rd globally). It's not even Personal Growth (ranked 6th), though that helps.
The values that matter most are relational ones.
Trustworthiness (ranked 19th) keeps showing up in profiles of people who resist AI. Not because they don't trust the technology. Because they've built their professional identity on being the reliable one, and they're not sure they can trust AI to protect that identity.
Loyalty (ranked 7th) appears constantly. Some employees feel that using AI is somehow disloyal to colleagues whose jobs might be affected, to the old ways of doing things, and to managers who didn't sign up for this change.
Relationships (ranked 2nd—second only to Family) shape everything. People don't adopt tools in isolation. They adopt them in the context of their working relationships. If their team isn't using AI, they won't either. If their manager seems skeptical, they'll be skeptical too.
Training addresses none of this.
The Trust Before Tools Framework
Here's the sequence that works. Four conversations, in this order.
Conversation One: The Loyalty Conversation
Before you talk about AI at all, talk about what's not changing. What commitments to employees remain in place? What aspects of their work are valued precisely because they're human? What does loyalty mean in both directions, their loyalty to the organization and the organization's loyalty to them?
If people sense that AI is being deployed to reduce headcount, no amount of training will overcome that suspicion. You have to address it directly, and you have to mean it.
Conversation Two: The Identity Conversation
Find out what people take pride in. What's the thing they do that makes them feel professionally valuable? The thing they'd be embarrassed to get wrong?
Now show them specifically, concretely, with examples, how AI protects that thing rather than threatening it. If someone's identity is wrapped up in being thorough, show them how AI helps them be more thorough. If they pride themselves on creativity, show them how AI handles the uncreative parts so they can focus on what matters.
This is about Trustworthiness and Personal Responsibility. You're not asking people to abandon what they value. You're showing them a better way to protect it.
Conversation Three: The Relationship Conversation
Adoption is social. If you train individuals but ignore teams, you'll get isolated pockets of usage and large swaths of resistance.
Identify the informal leaders, not the managers, the people others actually listen to. Get them using the tools first. Not as official champions with a mandate, but as curious early adopters who genuinely find the tools useful. Let adoption spread through relationships rather than org charts.
Conversation Four: The Capability Conversation
Now, only now, you do the training. But you do it differently. Instead of teaching features, you teach fit. How does this tool fit with the work you actually do? What problems do you actually have? The workflows that already exist?
Generic training creates generic resistance. Specific training, tailored to real jobs and real frustrations, creates actual usage.
What Changes When Trust Comes First
Organizations that follow this sequence report something odd. The training sessions get shorter. Not because they cut content, but because people show up actually wanting to learn. The questions change from "Why do we have to do this?" to "How do I make this work for my situation?"
That shift from compliance to curiosity is the difference between a tool that gets used once a month and a tool that becomes part of how people work.
I've seen rooms full of skeptics become rooms full of advocates over the course of a single session. Not because I convinced them AI was great. Because I showed them it aligned with what they already cared about.
The technology hasn't changed. The training materials haven't changed. The trust changed.
This is the work I do with organizations facing AI resistance. And it's the work you can start doing today, just by changing the order of your conversations.
Trust before tools. Every time.
Remember: if you know what people value, you can change what happens next.
Download free tools, data, and reports at www.davidallisoninc.com/resources
Want to know What Matters Most to the people you need to inspire?
Download free guides and resources.
Use the free Valueprint Finder to see how your values compare.
Find out why people call David “The Values Guy.”
Search the blog library for ways to put values to work for you.
