How do I train my team to use AI at work?
Train a team on AI by having them build something for their own job, on their own files, in one sitting — not by sending them a course. Start with shared vocabulary so everyone can talk about it, show what is possible with a real example, then protect a long hands-on block where each person builds, and end with everyone showing what they made.
- Shared words first: model, context, prompt, agent, connector — defined in plain language.
- One real, senior-approved problem beats ten hypothetical ones.
- Protect the build time. If the day runs long, cut the philosophy, not the building.
- Show and tell at the end is where the peer learning happens.
The 22-module library →Does my team need to be technical to do an AI workshop?
No. Rhai’s workshops are built for operators, founders and business teams — people who know the work but have never built software. Tools like Claude Cowork let someone point an agent at their real files and folders without ever opening a terminal. The one requirement is a senior person present throughout, so someone can say what actually matters.
How long does it take to teach a team AI?
A team can go from never having built anything to building something useful in a single session. Rhai’s formats run from a 60-minute talk or 90-minute leadership session, to a three-hour hands-on intro, to a full six-hour customised day, to a two-day engagement where day one is the full arc and day two is the build.
Session shapes →What should an AI workshop for a leadership team cover?
A leadership AI session should cover what a company is in the AI age, where institutional knowledge lives and leaks, what happens to the company’s data, and what a dashboard that acts — rather than just reports — looks like. Rhai’s 90-minute leadership format is built from exactly those modules: Vocabulary, Companies in the AI age, Privacy, and Dashboards.
The Frames modules →What happens after an AI workshop — does the team keep using it?
Teams keep using AI after a workshop when what they built runs on their own accounts and at least one person can extend it. Rhai sessions run on the company’s own Google or Microsoft tenant, and a customised day ends with a prioritised list of what to build next — so there is nothing to migrate and no dependency on the facilitator.