You can tell a room of people to start using AI. That is not the same as your company starting to use it.
The training session goes well, people ask good questions, and everyone leaves saying they'll use it. Then they get back to their desk and the next thing on the screen is a deadline, so they do the task the way they already know how, and the same thing happens the next day. Three weeks later, two people are using it properly, everyone else has quietly gone back to how they worked before, and nobody is going to say so in a meeting.
Your team understood it fine. The problem is that you asked each of them, separately, to change how they work, and an individual good intention loses to an ordinary Tuesday every time. Adoption happens to a group, at once, or it tends not to happen at all.
So put the whole team in one room and start it there. Everyone brings a laptop, and you set it up together before anybody leaves: accounts created, logins working, and one task run start to finish on their own work. Call it an install party for lack of a better name. The point is that the whole team crosses the starting line in the same hour, in front of each other, instead of each person promising to get to it.
An hour of everyone's time, once. After that it is a thing your team does, and the person who gets stuck in week two sits next to someone who already got past it.
Knowing how to prompt is now the easy part
Knowing how to write a good prompt has stopped being an advantage. It still matters, everyone just has it now, the way knowing how to use a spreadsheet is the baseline nobody gets an edge from.
The teams getting work out of AI are the ones whose AI is plugged into something. An assistant that has your calendar, your last six client conversations, and your current pricing in front of it gives you a different answer than one starting from a blank page, and the gap has nothing to do with how well you phrased the question.
That's the other half of the hour you spend in that room. While everyone is together, connect each person's AI to the two or three things it needs to know about your business, the shared drive, the calendar, the client folder, whatever they actually work out of. In most tools this is a settings screen and a login, not an IT project.
So ask two things about any AI your team is meant to be using. Is it in use across your team this week, or was it approved in a meeting and nowhere else? And does it have access to anything about your business, or does it start every session from nothing?
If it starts from nothing, that's why the answers come back generic. Your AI is performing about as well as a new hire nobody briefed.
The AI Agent Workshop
Somebody has to run that room, and that person needs to know which tools are worth your team's time, what to connect them to, and what to do when three laptops behave differently. That is usually the part that stops it happening.
That's what the AI Agent Workshop that I run is for. Half a day, everyone on their own laptop, and every person builds a working agent before they leave, against their own email, calendar, or spreadsheets. No programming background needed. The first half covers how agents actually work and which of your workflows are worth automating first. The second half is hands-on, and I facilitate it personally.
Your people walk out with an agent they built themselves, their own setup configured against the work they actually do, and the framework to keep building without a developer.
Book the AI Agent Workshop now, or reply to this email if you want to talk it through first.
If a full session is more than you want to take on right now, start with the AI Readiness survey. 15 questions, 5 minutes, results to your inbox, and it tells you where AI would help your operation first.
David