Skip to main content

You Bought AI Licenses. Why Is Nobody Using Them?

If you bought AI licenses and nobody uses them, the tool is rarely the problem. A license is not enablement, and access is not adoption. People start using AI when they have time to practice, a reason to change how they work, examples from colleagues they trust, and clear rules about what's allowed.

This is one of the most common things we hear from leaders in Cedar Rapids and across Iowa. The company buys Microsoft Copilot or ChatGPT Enterprise seats, holds a training session, and watches usage climb for two weeks and then flatten. A few people use it every day. Most opened it twice. The renewal is coming up, and nobody can say what the company got for the money.


Why aren't employees using AI tools?

It's tempting to read low adoption as resistance. In our experience, it's almost always a rollout problem. Five causes show up again and again.

The training was aimed at one band of people. A one-hour session for everyone tends to land with the people who are already about as skilled as the trainer. Beginners leave overwhelmed. The people who were already experimenting leave bored. Only the middle gets much out of it.

Nobody got time. Learning a new way to work takes practice, and practice takes time out of a week that's already full. If the message is "use AI" but the workload is unchanged, most people will reasonably keep doing what already works.

There's no reason to change. If the only reward for working faster is more work, why would anyone go looking for a faster way? People change when they can see what's in it for them: time back, a better role, recognition.

The good examples are invisible. Somewhere in your company, someone has already figured out how to cut a weekly report from two hours to twenty minutes. Nobody else knows, because there's no place or habit for sharing it.

The rules are unclear. If people aren't sure whether client data, financials or personnel information can go into the tool, the safe choice is not to use it at all. Uncertainty does more to stall adoption than a strict rule would.

The training gap is real outside Iowa too. In a 2025 global study of more than 48,000 people, KPMG and the University of Melbourne found that only 47% of employees say they have received AI training.


Why don't usage dashboards tell you the truth?

Every major AI platform gives administrators a usage report. It shows logins, active users and prompt counts. It looks like accountability.

But usage dashboards measure compliance, not capability. They tell you who opened the tool, not whether anything about the work changed. Someone who asks Copilot to rephrase three emails a day looks like a power user. Someone who spent one afternoon building a process that saves their team six hours a week might barely register.

When leaders manage to the dashboard, people learn to feed the dashboard. You get activity without improvement, and a renewal decision based on the wrong number.


What should you do when nobody uses the AI licenses you bought?

When AI licenses go unused, the fix is almost never a new tool or another all-hands training. Start by finding the few people already getting results and learning exactly what they do. Then figure out where everyone else is starting from, because a beginner and an experienced user need different help. Give people fifteen minutes a day of protected time to practice on their real work, so learning isn't squeezed into evenings. Make wins easy to share, so one person's good idea becomes a team habit instead of a private trick. Finally, make the rules clear and the safe path easy: say plainly which data is allowed in which tools, and make the approved option the convenient one. Do those five things for a quarter and adoption usually follows, because you've changed the conditions that kept people from using the tool in the first place.


The five-step recovery, in more detail

1. Find who's already getting results

Don't start with the dashboard. Start with a few conversations. Ask people to show you the last time they used AI for work: what the task was, what it produced, and what they did with the result. You'll find a handful of people doing genuinely useful things. They're your proof, and your best teachers.

2. Locate people by level, not by title

People start in different places, and treating them the same is why one-size training fails. We use a simple three-level scale (Beginner, AI Champion and Systems Builder) to describe where someone should start, not how good they are. We'll cover it in detail in a later post. For now, the key point is that a Beginner needs a first useful win, and a more experienced user needs a reason and a way to share what they've built.

It's also worth remembering that AI skill and process knowledge are different things. Your best opportunity-spotter may be a Beginner who knows exactly where the work hurts.

3. Give fifteen minutes a day

Protected, official, on-the-clock time. Fifteen minutes a day is about 75 minutes a week and roughly 65 hours a year. The simplest assignment we know: ask AI to teach you one thing from your own work. Steady, small practice builds more skill than a single long session, and it signals that leadership means it.

4. Make wins shareable

Create one low-effort habit for sharing: a standing ten minutes in a team meeting, a shared channel, a simple library of prompts that worked. The aim is to turn one person's win into something a teammate can use without them.

5. Make the rules clear and the safe path easy

Write down, in plain language, which data can go into which tools. Then make the approved tool the easiest one to reach. If the safe path is harder than the risky one, people will take the risky one, and you'll never see it.


Is this a training problem or a leadership problem?

Mostly leadership. Training helps, but it can't create time, incentives or clear rules. Those come from the people who set priorities and budgets.

That's the pattern we described in five signs your business needs AI leadership: tools bought, usage spotty, nobody steering. The good news is that the licenses you already own are usually enough. What's missing is someone who owns the conditions around them.

If you're trying to decide what kind of outside help that takes, our guide to what an AI consultant costs walks through the options honestly.


Before the next renewal, find out what your people actually need to use what you've already bought. That's the work we do through AI strategy and leadership for Iowa businesses, and it usually starts with a few conversations, not a new purchase. Learn more about our Advise, Educate & Lead services.

Frequently Asked Questions

Why aren't employees using the AI tools we bought?

Usually because the rollout gave people access and stopped there. Training was aimed at one skill level, nobody was given time to practice, there was no clear reason to change how they work, good examples stayed private, and the rules about what data is allowed were unclear. Fix those conditions and usage follows. Buying a different tool rarely helps.

How do you measure AI adoption?

Logins and prompt counts tell you who opened the tool, not whether work changed. Better measures are concrete: which tasks people now do differently, what one person built that a teammate uses without them, and which processes changed because of AI. Ask people to show you the last task they used AI for and what they did with the result.

Should we cancel unused Copilot or ChatGPT Enterprise licenses?

Look before you cut. Find the people who are getting results and learn what they do differently. If a few roles get real value, keep those seats and fix the conditions for everyone else. If almost nobody uses the tool after time, examples and clear rules are in place, it may be the wrong tool for your work, and canceling is reasonable.

How much time do employees need to learn AI tools?

Less than most leaders expect, but it has to be protected time. Fifteen minutes a day of using AI on real work adds up to about 75 minutes a week and roughly 65 hours a year. That steady practice builds more skill than a single long training session, and it's easy to fit into a schedule if a manager makes it official.

Drew Bloom, founder of Mosaic Solutions

Drew Bloom

Founder, Mosaic Solutions — Business Systems, Software & Automation

Drew is the founder of Mosaic Solutions. He spent several years as an automation consultant and Innovation Lead for Affinity, where he worked with law firms and enterprise clients on AI strategy, change management, and custom software. He works with small and mid-sized businesses in Iowa and beyond to fix the systems that slow them down — with better processes, software, and AI that actually works.

More about Mosaic LinkedIn Work with Drew

Bring Us the Decision in Front of You.

AI strategy, policy, vendor choices and fractional technology leadership, scoped first and billed for the time the work takes.