I do consultations with businesses every week or two now, and the question I hear has changed. It used to be "what is this AI thing?" Now leaders already have the licences. They want to know why nobody on the team is really using them.

Usually it is because the company did AI the expensive way: a policy, a stack of licences and a lot of fear.

Here is the short answer. AI training for teams works when the team builds something real, from their own work, in the same session. A policy and a pile of logins do not change how anyone works on Monday. A hands-on workshop does, because people leave with a tool they made, and the rules finally make sense once they have used the thing.

Nobody Learned to Drive From the Rulebook

Think about how you learned to drive. You did not read the highway code cover to cover and then go out on the motorway. You sat in the seat, someone sat next to you, and you pulled out of a car park very slowly.

The rules mattered. But they only stuck once your hands were on the wheel. "Check your mirror before you change lanes" is a boring sentence until the first time a car appears in your blind spot.

Most companies are handing their teams the rulebook and calling it training. A document about acceptable use. A webinar with slides. An email that says "you now have access." Then everyone goes back to their spreadsheets and nothing moves.

That is not a lack of discipline. It is a lack of driving lessons.

Why Most AI Training for Teams Goes Nowhere

The first problem is that people are asked to change their work without ever seeing AI touch their work. A demo of someone else's chatbot writing a poem tells a warehouse manager nothing about stock levels. Generic training produces generic interest, and generic interest is gone by Thursday.

The second problem is fear, and a policy written from fear makes it worse. If the first message your team hears is "be careful," the safest move for every person is to never open the tool.

What Changes When the Team Builds Together

We have taught more than 1,300 people through our workshops and team trainings, and the moment I watch for is always the same: someone shows the room a thing they built for their own job.

When I spent two days with one business training client in London, about 15 people took part, from leadership to inventory, design, content, SEO and regulatory. The goal was simple: every person leaves with a working tool for their own job. By the closing demo round on day one, the team had built 14 custom tools. On day two they built an ad generation machine for on-brand Facebook and Instagram ads.

At another business training client, the team demonstrated a morning arrivals report that pulled VIP arrivals, room allocation and a reception checklist into one handover. Nobody needed a slide to understand why that mattered. They do that handover every day.

In a third session, a participant compared a developer's prices with the company's own price list and found an apparent mismatch. It turned out to depend on whether parking was included. That is the kind of lesson no policy can teach: the tool was useful, and a person still had to check what the numbers meant.

That is learning to drive. Hands on the wheel, someone next to you, real roads.

The Real Policy Gets Written at the Keyboard

I am not saying rules do not matter. I am saying the useful ones show up when you start building, and most of them look nothing like a policy document.

Before that two-day training, we sat with the founder and decided what Claude was allowed to do with each connected system. Every connector was set to allowed, approval-only or blocked. Anything that moves money is blocked or needs approval. Team members only see the connections that were approved. That is a policy. It just lives in the settings instead of a PDF, so it actually gets enforced.

With another team, the rule that came out of the session was to experiment on a copy of the spreadsheets before letting AI change live operational data. One sentence, learned by doing, that everyone in the room will remember.

I learned this inside my own company too. Training my team to make website updates turned out to be a tough task, because, as I put it in a lecture, "it's not only Claude Code that they need to learn, they also need to learn what not to do." Things like how the API keys are set up. You only find those edges by driving near them.

The other rule that shows up in every team is about where information lives. I said it in another session: "in the past, having well-designed databases wasn't so important in companies, but now in the age of AI it's become incredibly important." Put your SOPs, your brand rules and your data in one place everyone can reach, and train the team to go there first. That single decision does more for safe, consistent AI use than ten pages of guidelines.

Keep the Car Running After the Lesson

A workshop is the first lesson, not the licence. The teams that keep going build a habit around it.

One client team created an AI Wins Slack channel during their training so people had a place to keep sharing what worked. That is small and it is exactly right. Wins spread sideways, from colleague to colleague, much faster than they spread from a memo.

With the people I coach, I ask them to create a Claude project and put the transcripts from our calls inside it, so they can talk to everything we covered. Everyone I work with is trained up in Claude, so it is a given. The training does not end when the call ends. It becomes something they can ask questions of.

I do the same for my own business. I used to spend about 45 minutes on every team training proposal. So I spent about 30 minutes drawing the whole process out by hand on paper, then put it into Claude Cowork. Now an inquiry lands on a board, an offer and a payment link get drafted, and all I do is approve and send. That is the shape I want every team to leave with: one real process, rebuilt, and the confidence to do the next one alone.

What You Can Do Right Now

You do not need a company-wide rollout to start. You need one honest lesson.

So skip the rulebook as a starting point. Put your team in the driver's seat, sit next to them for one real lesson, and write down the rules you discover on the road.

Questions People Ask

Do we need an AI policy before training our team?

You need a few decisions, not a long policy: which tools Claude can connect to, what needs approval, and that anything moving money is blocked or approval-only. Make those decisions in a setup session and put them in the tool settings.

What should a team build in its first AI workshop?

Something from their own repeated work. A daily report, an email review queue, an invoice tracker or a sales dashboard. If people build on real tasks and real data, they keep using it after the session.

Is online or on-site AI training better for teams?

Both work. On-site gives you more energy in the room and side-by-side help. Online suits distributed teams and multiple offices. What matters more is that every person builds and demonstrates something during the session.

Does my team need technical skills for AI training?

No. One two-day training I ran included people from leadership, operations, design, content and regulatory roles. They describe the work in plain language and Claude does the building, while they check the results.

How long should an AI workshop for a team be?

Long enough for everyone to finish one working tool and show it. One business training client trained for two days in person: day one for individual tools, day two for a shared ad generation workflow.

Bring This to Your Team

Light School trains teams online or in person: connect your real tools, build around your own work, and leave with your first projects. No coding experience needed.

See Team Training