Collective Campus
Blogs

AI training

How an AI upskilling programme for staff should run

Two desks along a neon path, one sheet finished and a stack of blank cards

Staff already have a window open. Some of them pay for a personal account because the company tool is slow, blocked or embarrassing to use where a manager can see. A programme that starts with a tour of logos will miss the task they finish in that private window on a Tuesday afternoon.

The OECD says people need the skills to use AI systems, and it names training through working life as one way a workforce keeps those skills. The programme you buy is that training for the people already on the payroll. It has to land on their work, in the tools they will still have after the facilitator leaves the building.

The first month

A single day can leave one person able to run next week's task. What that day should produce is in what a corporate AI training day should produce. A staff programme is the sequence around that day. You pick one workflow a named team already runs. You practise it on dummy or approved material. You write the check a human still does. You come back a few weeks later and look at what changed, including the places the output was wrong.

The AI training workshop is the hands-on day inside that sequence. People map uses for their own roles and get reps on the tools they can keep. The workshop also builds a 90 day plan to put the work into the week. The programme is what stops that plan dying in a folder. Someone owns the workflow. Someone looks again before the month ends. If nobody owns it, you have bought a class.

Cohorts built around one job beat a town hall where everyone watches the same demo. That case is in role-based AI training. A staff programme can still start with one function, the people who write to customers for example, when that is where the work sits. Refuse a catalogue of seats with no workflow attached. The warning against that brochure is in stop buying an AI academy brochure.

What to ask before you buy

Ask which tools the team may still open next month. We stay with tools the team can actually keep, and we teach what is useful on their work now. A day built on a product you will not renew is a demo with a certificate at the end. Ask which data may enter the room. We use dummy or approved material, and we cover what must stay out of a tool. If a provider wants production client files on the first morning, stop the conversation there.

Ask who will run the task without the facilitator. You want a named person, on their own work, with the prompt and the check written down. If the proposal measures course completion, you will get a chart and the same Tuesday afternoon. A completion chart records who attended. You still have to watch whether the workflow changed. Half a day can start a single workflow. A full day gives the reps and the plan. In person is better for the first session, because you can see who is lost while there is still time to help. Remote works for the return session, once the workflow has an owner. The return date is part of the buy. If you cannot name that date, you are buying a single day. Judge it by what one person can do the following week, and book the programme when you are ready to come back.

Source: the OECD

WorkshopBook the AI Training workshop