An AI enablement workshop is a hands-on session that helps a team learn to use AI tools inside their actual work, not in the abstract. Done right, people leave using AI on the tasks they were already doing. Done the way most of them are run, people leave with a folder of prompts they never open again.
Boon has watched a lot of the second kind. IT buys the licenses, someone books a vendor for a half-day session, everyone learns to write a decent prompt, and adoption still flatlines two weeks later.
Here's the thing. The workshop isn't the problem. The idea that a workshop, by itself, changes how people work is the problem.
What an AI Enablement Workshop Actually Does
A good session does one thing well: it gets people over the first hump of unfamiliarity. It shows a marketer, a recruiter, a finance analyst that these tools apply to their job specifically, and it lets them try one thing with someone in the room to catch them when it breaks.
That's real value. It's just narrow.
What a workshop cannot do is build a new habit. Habits form in the messy weeks after the session, when the prompt doesn't work on a real deadline and there's no one around to ask. That gap between "I saw it demoed" and "I do it without thinking" is where most AI rollouts quietly die.
Boon has written before about why AI adoption fails, and it almost never comes down to the tool being bad or the training being weak. It comes down to nobody owning the human layer of the change. IT ships the software. HR and L&D get handed a completion metric and told to make people ready to use it. A one-off session is the shape that request usually takes.
So run the workshop. Just stop pretending it's the finish line.
Why IT-Led Workshops Miss the Point
Most AI enablement right now runs out of the IT org. That makes sense on paper. IT owns the tools, the security review, the license count.
But IT is optimizing for the wrong thing. It measures whether the tool got deployed and how many seats got activated. Those numbers can look great while nobody is actually changing how they work.
The session that comes out of an IT-led rollout tends to be tool-centric. Here's Copilot. Here are the features. Here's a prompt library. It answers "what can this tool do" when the question people actually have is "how does this change my Tuesday."
Boon covered the deeper version of this in why IT-led AI rollouts stall. The short version: IT can ship the tool but it cannot lead behavior change, because behavior change is a people problem, and people problems belong to HR. The question of who owns AI adoption, IT or HR, isn't a turf fight. It's a diagnosis of why the workshop didn't stick.
This is HR's moment, and most HR teams are still waiting to be invited. Don't wait. The workshop is the way in. Own it.
Design the Workshop Around Real Work, Not the Tool
The single biggest fix is boring and unglamorous: build the session around tasks people already do, not around the tool's feature list.
A generic AI workshop teaches prompting. A good one has the recruiter bring three real reqs and rewrite one screening rubric live. It has the finance analyst pull an actual variance report and try to draft the commentary. People remember what they made, not what they watched.
That means the prep work happens before the room, and it's the part vendors skip. Someone has to figure out the two or three highest-frequency tasks for each function, then design the exercise around those tasks.
Here's a structure that holds up across the engagements Boon sees:
- Name the task. Not "use AI for email." Instead: "the weekly status update you send your VP." Specific enough that everyone in the room recognizes it.
- Do it the old way, out loud. Ten minutes. Where does the time go, where's the friction. This is the baseline.
- Do it with AI, on real inputs. Not a sandbox. Their actual data, their actual deadline pressure.
- Compare and edit. What did AI get wrong, what needed a human, what would you change next time. This step is where judgment gets built.
- Write down the one thing you'll try Monday. Singular. One task, not ten.
That last step matters more than it looks. People who leave with one concrete commitment do something with it. People who leave with a 40-prompt library do nothing, because the library is a decision they have to make every morning, and they won't.
The Part Nobody Budgets For
There's an old learning principle that says people grow mostly from doing the work, some from other people, and a little from formal training. In the AI world it gets flipped into a similar split: a little into instruction, some into coaching and peers, most into hands-on application.
The number isn't the point. The point is that a workshop is the small slice. And almost every AI enablement program spends nearly all of its budget and attention on that slice, then acts surprised when the rest doesn't happen on its own.
The rest is the workflow, the peers, the manager who models it, the person you can ask when it breaks on a Thursday. None of that comes in the box with the workshop.
So the real question isn't "how do we run a better session." It's "what carries the learning through the weeks after it." That's a coaching and reinforcement question, and it's where most programs have nothing planned at all.
Boon's whole point of view sits here. The workshop starts the change. The reinforcement is what sustains it. The difference between a program that changes behavior and one that doesn't isn't the quality of the session. It's whether anything exists to catch the moment three days later when someone hits a wall and quietly decides "this is more trouble than it's worth."
That moment is invisible to IT dashboards. It doesn't show up as a license deactivation. The person still has the seat. They just stopped using it.
This is why Boon delivers AI enablement through coaching that lives in the flow of work rather than a calendar event. When someone gets stuck applying AI to a real task, they can reach a coach in the tools they already use, Slack or Teams, in the moment it matters, not two weeks later at the next scheduled session. Boon's program data shows session attendance runs 89%, and the reason it holds is that the coaching shows up where the work already happens instead of asking people to break their day for it.
A workshop ends. The wall people hit doesn't respect the calendar. For the fuller argument, Boon laid out how HR can lead AI transformation and built an AI adoption framework for HR leaders around exactly this.
Managers Decide Whether Any of It Sticks
Here's the uncomfortable finding. You can run a flawless workshop, and if the manager doesn't use AI or doesn't ask their team about it, the whole thing evaporates.
People take their cues from their manager, not from the L&D calendar. If a manager never mentions the new tool again after the training, the team reads that as permission to drop it. If a manager asks in a one-on-one "how are you using this on the pipeline work," the team keeps going.
This is the same pattern Boon sees everywhere in leadership work, which is why we keep coming back to the middle layer as the real engine of growth. Managers are how change carries to their teams, AI included. Skip them and you're pushing change uphill.
So a session that actually sticks includes managers, and not as observers. Managers need their own version focused on how to coach the behavior, how to spot who's stuck, how to make AI use a normal part of the work conversation. Boon's manager-as-coach work goes deeper on how that habit gets built. The tools change. The mechanics of leading people through change don't.
Most enablement plans forget managers entirely. That's the tell of an IT-led rollout wearing an HR badge.
How to Know It Worked
Skip the smile sheets. "Did you enjoy the workshop" tells you nothing about whether anyone changed how they work.
Measure behavior and outcomes instead:
- Task-level usage. Are people using AI on the specific tasks the workshop targeted, four weeks out? Not overall logins. The tasks.
- Quality and time. Is the work getting done faster or better on those tasks. Ask the people doing it and their managers.
- Where people get stuck. Track the walls people hit. That's your next workshop, and it's more useful than any completion rate.
Boon measures its own coaching on competency change, and Boon's program data shows a 23% average improvement in the skills people are working on, with an NPS of +87. Those numbers mean something because they track whether the person actually got better at the thing, not whether they showed up. There's a solid breakdown in measuring coaching ROI and in Boon's guide to AI adoption metrics for HR.
The test is simple. If your only proof the workshop worked is that people attended and rated it highly, you don't have proof. You have attendance.
Put it all together and the workshop stops being a one-off event and becomes the first move in a longer play HR runs. HR designs the session around real tasks per function. HR brings managers in as coaches, not spectators. HR wires up reinforcement so the learning survives. And HR measures behavior, not sentiment. Boon's Adapt approach is built for exactly this handoff, and if you want the strategic frame first, start with how to build an AI adoption strategy.
Frequently Asked Questions
What does AI enablement do?
AI enablement helps people use AI tools productively in their real work, and helps leaders steer that adoption. It covers the training, the hands-on practice, and ideally the reinforcement afterward that turns a demo into a habit. The training part is the easy half. The reinforcement part is where most programs fall short.
How should you set expectations for what AI can do on a task?
A common mental model workshop facilitators use is that AI can realistically handle the early part of a task, the draft, the boilerplate, the starting point, while a human still owns the judgment, accuracy, and final call. It's a useful expectation-setter for a workshop: teach people to use AI for the head start, not the finished product.
What is the 10-20-70 rule for AI?
The 10-20-70 rule suggests splitting AI enablement effort as roughly a small share into formal training, a larger share into learning from peers and coaches, and the largest share into hands-on application in real work. The takeaway for HR is blunt: the workshop is the smallest slice, so if you spend all your budget there, you've funded the smallest part of what makes AI adoption stick.
Which 3 jobs will not survive AI?
No credible research names specific jobs as certain to disappear, and Boon won't invent a list. What research consistently shows is that tasks get automated faster than whole roles do, and the people who do best are the ones who learn to use AI on the routine parts of their job so they can spend more time on judgment and relationships. That's a coaching problem, not a headcount prediction.
Should IT or HR run the AI enablement workshop?
IT should provide the tools and the technical setup. HR should own the workshop and everything after it, because behavior change is a people problem. Boon covers this in who owns AI adoption, IT or HR, and the short answer is that IT ships the tool while HR drives the change.
The Cost of Getting This Wrong
A workshop that doesn't stick isn't neutral. It teaches people that the new tool is a passing initiative, that leadership doesn't really mean it, that they can wait this one out like the last three. Every enablement session that changes nothing makes the next one harder, because people have already learned not to bother.
That's the real cost. Not the vendor fee. The credibility you spend and don't get back. And it compounds, because the next time you ask a team to change how they work, they remember the folder of prompts they never opened.
Boon runs AI enablement as coaching that starts with a workshop and then lives in Slack and Teams alongside the actual work, so the moment someone hits a wall three days later, there's a coach there instead of silence. That's the part that turns a good session into a changed habit. If you want to see how it works on your team, talk to Boon.