Training your team on AI in an hour
AI training for staff can fit into one hour if you teach four things: what to use it for, how to ask, what never goes in, and how to check what comes out.
Most small businesses don’t need a course or a certificate. They need everyone using the same tool, for the same few jobs, under the same rules. An hour covers that. What an hour can’t do is make the habit stick by itself, and that part decides whether the training was worth the time.
Why do staff stop using AI tools after the training?
Usually because nobody tied the tool to a job they already do. People sit through a demo, see something clever, go back to their desk and carry on exactly as before, because nothing about their actual Tuesday has changed.
The other reasons are just as ordinary:
- The first try went badly. A vague request got a vague answer, and they decided the tool was no good.
- They weren’t sure what was allowed. Without a clear rule on client details, the careful people simply avoid it.
- Too many tools. Three logins, two half-set-up accounts, and nobody sure which one the business pays for.
- Nobody mentioned it again. If the owner never brings it up after the session, staff reasonably assume it didn’t matter.
The running order below is built around those problems.
How to run a one-hour AI training session for your team
Keep it hands-on and keep it to one tool. Everyone brings a laptop, everyone logs into the same account, and everyone works on a real task from their own week rather than a made-up example.
A rough running order:
- Ten minutes: what it’s for here. Name three or four jobs in your business it should help with. Nothing abstract.
- Twenty minutes: how to ask. Everyone writes a request for one of those jobs, reads the answer, then improves the request and tries again.
- Ten minutes: what never goes in. The data rules, read out and agreed.
- Ten minutes: checking the output. Each person checks one answer against the facts and finds what it got wrong.
- Ten minutes: what happens next. Who to ask when stuck, and when you’ll talk about it again.
Before the session, check what you already pay for. Plenty of businesses have Copilot or Gemini sitting inside Microsoft 365 or Google Workspace and have never switched it on. Training people on a tool you already own is easier than adding another login to the pile.
How to teach staff to use AI: the four things worth covering
Teach what it’s for, how to ask, what stays out and how to check. Leave out the history of AI, the comparison of six chatbots and the party tricks. They eat the hour and none of them help anyone on Monday morning.
1. What it’s for in this business
Be specific. “Use it to draft replies to quote requests” works. “Use it to be more productive” doesn’t. Say you run a small accountancy practice: the jobs might be first drafts of client emails, a plain summary of a long letter from Revenue, and turning meeting notes into a list of actions. Three jobs written on one page is plenty for a first month.
2. How to ask
Most bad answers come from short requests. Show people the difference between “write an email about the late invoice” and a request that says who the client is, what happened, what tone you want and what the email must not promise. Then let them try it on their own work, because seeing their own draft improve is what convinces people. The post on writing AI prompts that actually work has a simple pattern you can print and hand out.
3. What never goes in
This is the part people remember, as long as it’s short. Agree what can’t be pasted into the tool, for example client names and contact details, health information, bank details and anything covered by a confidentiality agreement. Then write it down so nobody has to guess. If you don’t have rules yet, the post on writing an AI policy for a small business gives you a one-page version to start from. This is general information, not legal advice, so if you handle sensitive client data, check your obligations properly.
4. How to check what comes out
AI writes confidently whether it’s right or not. Teach one habit: check every name, number, date and promise against the source before anything leaves the building. It takes seconds, and it’s the habit that stops an embarrassing email reaching a customer.
AI onboarding for a small business: what happens after the hour
The hour starts the habit, and the month after it decides whether it lasts. A few small things make the difference:
- Pick one person to ask. Usually whoever on the team is most comfortable with the tool. Questions go to them first.
- Keep a shared list of requests that worked. A document or a group chat where people paste a good request and what it was for. Over time it becomes your own playbook.
- Check in after two weeks. Ten minutes at a team meeting: what did people use it for, what went wrong, what should stop.
- Add it to onboarding. New starters get the same one page in their first week, so the rules don’t depend on who happened to be in the room.
If, after a month, people are using it every day for one or two jobs, the training worked. That beats a team that tried ten things once and went back to the old way.
Do you need an outside trainer?
Often not. An owner or manager who uses the tool themselves can run this hour well, and staff tend to take it more seriously from someone who knows their actual work. Outside help earns its keep on the part before the training: deciding which jobs are worth handing to AI in the first place, and setting the tool up so it fits how you work. Get that wrong and you end up teaching people to use it on jobs where it saves nobody any time.
If you’d like help picking the jobs worth teaching before you run the session, the AI Assessment is where I’d start: a fixed-fee look at how your week actually runs, ending with a plain plan your team can begin on straight away.
The assessment is credited in full if you go on to a build, and if I can’t find you five hours a week you pay nothing. See how it works.





















