A company buys an enterprise AI platform. Leadership sends an announcement. IT runs a two-hour demo. There’s a Slack channel, maybe a PDF guide.

Three months later, maybe 20% of employees are actually using it. The rest? They open the tool once in a while, feel lost, and quietly go back to the old way of doing things.

The company tells its board it has “deployed AI across the organization.” And technically, that’s true.

But deploying AI and building AI fluency are two completely different things. That gap is the real reason most AI investments underperform.

I’ve spent the last several years helping SaaS founders and enterprise teams build AI systems that actually get used — through SDTC Digital and across 100+ companies I’ve worked with. The pattern I see everywhere is the same: organizations treat AI adoption as a technology problem when it’s really a people problem. Fix the people side, and the technology starts paying off.

This article breaks down the 4-step playbook for building genuine AI fluency inside your organization — not checkbox training, not one-off workshops, but real, embedded habits that change how people work every day.

If you want practical insights like this every week — on AI adoption, product strategy, and what’s working in the real world — subscribe to my newsletter where 210,000+ readers stay ahead of the curve.

What Is AI Fluency at Work, and Why Does It Matter?

AI fluency is not the same as AI awareness.

AI awareness means you know tools like ChatGPT or Microsoft Copilot exist. Most employees have this. They’ve read about it. They’ve probably used it on their phone.

AI fluency is knowing when to use AI, when not to, how to communicate with it, how to evaluate what it gives you, and how to stay responsible while doing it. It’s a skill that shows up in daily work — not just in a training session.

The numbers tell a stark story. 74% of workers use AI at work, but only 33% have received any formal training. Most people are guessing their way through it. And 65% of employees say they’re excited to use AI, but 37% still don’t use it even when it’s available to them.

The excitement is there. The adoption isn’t. Something is missing in between — and that something is a structured approach to building fluency, not just access.

Step 1: Deal With the Fear First, Then Introduce the Tools

You cannot train people on tools they are afraid to use.

This is the mistake I see most often in AI rollouts. Organizations spend months choosing the right platform, getting security approvals, setting up integrations — and then they launch it and expect people to be excited. What they never addressed is the question every employee is quietly asking: “Is this here to replace me?”

75% of employees worry that AI will eliminate their jobs. Fear doesn’t create curiosity. It creates avoidance. And avoidance is quiet — people don’t tell you they’re avoiding the tool. They just don’t use it, and your adoption data looks bad six months later without anyone knowing why.

The first step is not a training session. It’s a conversation.

Before you roll out any tool, hold what I call a “fears and opportunities” session with each team. Ask people what worries them about AI in their specific role. Answer with facts, not reassurances. Then ask where they think AI could genuinely save them time. You’ll learn more in one hour than any pre-rollout survey will tell you.

Salesforce found that employees whose managers visibly use AI tools are 22 percentage points more engaged with those tools than employees whose managers don’t. That’s not a small number. It tells you that leadership behavior is the loudest signal your organization can send about whether AI is safe to try — and safe to fail at.

How to measure this step: run a short sentiment survey before and after the engagement phase. Ask employees how confident they feel using AI in their work. Track the shift.

Step 2: Make AI Part of the Daily Workflow, Not a Separate Tool

Once people aren’t afraid, the next problem is friction.

If using AI means opening a new tab, logging into a separate platform, and then figuring out how to apply it — most people won’t bother. Not because they don’t want to. But because anything that feels optional and unfamiliar gets skipped when the day gets busy.

McKinsey’s research shows 48% of employees would use AI more if they had formal training, and 45% would use it more if it was built into their daily workflows. The highest-impact move is to give them both at the same time — not training first and integration later.

The goal of this step is to move AI from something people try occasionally to something they use out of habit. And habits form when behavior is easy, tied to existing routines, and immediately useful.

This also means making it role-specific. A customer support rep’s AI needs are completely different from a product manager’s or a data analyst’s. Generic AI training that isn’t connected to real job tasks gets forgotten within weeks. Role-specific training drives dramatically higher retention and real-world application — the research is consistent on this.

A practical technique that works well: ask each team to list their top three time drains — the tasks that take the most time for the least value. Then run a live session showing exactly how AI can help with those specific tasks. Not a general product demo. A direct demonstration on work they already do.

This makes the value real and immediate. It shifts the conversation from “AI we’re supposed to use” to “AI that solves a problem I actually have.”

What to measure at this stage: weekly active usage by team and role. A benchmark of 60–80% weekly active usage within 60–90 days of rollout is reasonable. Below that, something in the workflow isn’t working and needs to be adjusted.

Step 3: Build the Four Skills That Make Someone Genuinely AI-Fluent

Most organizations think AI fluency is one skill. It’s four.

They develop at different rates across different roles. The framework I find most useful here is Anthropic’s 4D model — it defines what AI fluency actually looks like in practice.

Delegation: Knowing What to Hand Off to AI

This is the judgment to decide which tasks AI should handle and which need a human. It sounds simple, but it’s not. Employees who can’t delegate well either hand AI tasks that require human judgment and context — or they keep doing manually what AI could handle reliably and faster.

Building this skill means giving people clear criteria: here is where AI works well, here is where a human must review, here is where AI should never be the final answer.

Description: Communicating Clearly With AI

This is what most people call “prompting,” though that word carries a lot of hype with it. Description skill is the difference between a vague, generic output and something genuinely useful. It means knowing how to give context, set constraints, and iterate on responses rather than accepting the first thing the AI produces.

This is the most teachable of the four skills in the short term, and it has a visible payoff — which helps reinforce the habits built in step two.

Discernment: Knowing When to Trust the Output

This is the ability to critically evaluate what AI gives you. To spot when an output is wrong, incomplete, biased, or just not good enough for the task at hand.

This is where most organizations underinvest. They teach people how to use the tools but not how to question what those tools produce. BCG found that 70% of AI implementation failures are people- and process-related, with only 10% attributable to the AI algorithm itself. Most of those failures trace back to insufficient discernment — employees trusting outputs they shouldn’t have.

Diligence: Using AI Responsibly

This covers data privacy, transparency about when AI was used in an output, avoiding over-reliance, and staying accountable for AI-informed decisions. As regulations around AI tighten globally, diligence is moving from a soft expectation to a hard business requirement.

Professor Joseph Feller from University College Cork frames this well: “Just start using the language. It focuses attention away from the tech and back onto the human.” The 4D framework does exactly that — it gives your organization a shared vocabulary for what good AI work looks like, and shared vocabulary shapes behavior at every level.

The practical application: build a role-specific fluency matrix using these four dimensions. Customer support teams need to prioritize Description and Diligence — they communicate with AI constantly and their outputs represent your brand. Product managers need strong Delegation and Discernment — deciding which AI-generated insights to act on and which to challenge. The matrix turns fluency development from abstract to actionable.

Measure this through peer review of AI-assisted outputs and tracking output quality over time. It takes more effort than tracking course completion — and it’s the only measurement that tells you whether expertise is growing or just being reported.

Step 4: Measure What People Do, Not What They Attend

Here’s an uncomfortable truth about most corporate AI fluency programs: they measure attendance.

Course completions. Training hours. Certificates issued. These numbers are easy to collect and easy to put in a slide deck. They have almost no relationship to real capability or business results.

97% of enterprises still struggle to demonstrate clear AI business value. That’s not because AI isn’t producing value — in many organizations it is. It’s because nobody built a measurement system connected to actual outcomes rather than learning activity.

Three metrics actually tell you whether AI fluency is developing:

Activation rate is the percentage of employees using AI tools in real work every week — not enrolled, not certified, but actively using them. This is your most basic signal of whether fluency is taking hold or sitting dormant.

Application quality tracks whether the work is improving. Are tasks being done faster? Are outputs better than what was produced manually before? This requires a baseline measurement before rollout — which most organizations skip and later regret.

Business impact connects AI fluency to outcomes the organization actually cares about: time saved, error rates reduced, customer satisfaction improved, revenue influenced. This is the hardest to measure and the most important to attempt.

A simple monthly pulse survey keeps the loop closed. Three questions: Did you use AI this week? On what task? What blocked you? That third question is often the most valuable. The blockers are rarely technical — they’re almost always about uncertainty, unclear guidelines, or AI not being integrated into a specific workflow. Knowing the blockers tells you exactly where to focus next.

The organizations getting the most value from AI fluency programs treat measurement as an ongoing cycle, not a one-time post-program assessment. They check activation weekly, adjust workflows monthly, and report on business impact quarterly.

AI Fluency Is Infrastructure, Not a Training Program

Everything in this playbook depends on one fundamental shift in how you think about AI fluency.

It is not an event. It’s infrastructure.

When you treat AI fluency as a training course, you design something with a start date and an end date. People complete it, get marked as trained, and leadership moves on feeling like the job is done.

When you treat it as infrastructure, you build something embedded in how people work — continuously maintained, measured against real outcomes, and improved as the environment changes. You manage it the way you’d manage any operational capability that matters to the business.

The Salesforce AI Fluency Playbook was developed and tested across 70,000+ employees and follows exactly this logic: Engagement → Activation → Expertise → Outcomes. The sequence is intentional. You can’t build expertise on a foundation of fear and avoidance. You can’t drive meaningful activation without first removing the psychological barriers that stop people from genuinely trying.

BCG’s 10-20-70 framework is one I put in front of every executive sponsor before a rollout begins: 10% of AI success comes from the algorithm, 20% from the technology, and 70% from people and culture. Yet most organizations spend the majority of their time and budget on the 10%.

Where to Start If You’re Building This Right Now

If you’re a CLO, HR leader, or someone responsible for AI adoption — resist the instinct to immediately map this against your current training program and look for gaps.

Start with a more honest question: what percentage of your employees used an AI tool in real work last week? Not in training. In actual work. If you don’t know this number, that measurement gap is the first thing to fix.

Then ask your managers whether they personally model AI usage in team settings. Salesforce’s 22-point engagement finding is one of the strongest data points in this space. If managers aren’t demonstrating fluent AI use, the signal they send drowns out any training program you run.

Then ask your employees — directly, in a setting where it’s safe to be honest — what they’re actually afraid of and what’s blocking them. Not in a survey. In a conversation. The answers will be specific. And specific answers lead to specific, fixable interventions.

The organizations that win in 2026 won’t be the ones with access to the best AI models. Most organizations will have access to roughly equivalent models. The advantage goes to the teams whose people are confident, consistent, and responsible in how they use AI every single day.

Building that kind of capability is leadership work. It’s culture work. And it starts well before anyone opens a training platform.

If this kind of thinking is useful to you — practical frameworks, real data, and clear strategies for AI adoption and product development — join 210,000+ subscribers on my newsletter. Every week I cover what’s working, what’s not, and where things are heading.