How to Brief a Team on AI Before You Train Them
A short briefing before training changes what people bring to the room, and it costs one meeting. Here is what that meeting has to cover.
People arrive at AI training with nothing to try it on, and that is a decision somebody made by not making it. Skip the briefing and a training day defaults to generic examples nobody in the room actually needed, which is the single biggest reason a training budget produces enthusiasm on the day and nothing measurable a month later.
The fix costs one meeting, not a redesign of the programme, and it is the first thing we put in a client’s calendar before a single training session runs. The difference between a session that changes how people work and one that does not is set a week before anyone opens a laptop.
Key Takeaways
- A one hour briefing a week before training changes what people bring into the room.
- The briefing should name tasks, not tools, because a task is something a person already recognises.
- It should be run by the manager rather than the trainer, so it reads as an instruction rather than a pitch.
- Anyone who cannot name a task to bring is telling you something useful before the money is spent.
The evidence
A session works when somebody in it has a task they already resent. They know how long it takes, they know what a right answer looks like, and they can tell within a minute whether the tool did anything. Nobody has to invent a brief for them, and inventing the brief is the hard part of the work.
A session goes flat when the room is full of people who were told to attend. They have no task in mind, so the trainer supplies one, and a supplied example is always easier than real work. Everybody leaves having watched something succeed on a problem they do not have.
The difference is set before the day starts. So run the briefing a week out, keep it to an hour, and cover three things: which parts of this team’s work are in scope, an instruction to bring one real example each, and what is not allowed near these tools. What follows takes each of those in turn.
Whether you are running one of our core AI courses, a bespoke programme built from your own processes, or picking something from the full catalogue, the briefing is the same hour and it is the cheapest part of the whole thing.
What the hour has to cover
Name the scope as tasks, not tools. “You can use AI for the client update” is something a person can act on in the next week. “You now have access to an AI assistant” is not, because it names a capability rather than a task, and a capability with no task attached is exactly what produces a room full of people with nothing to bring. Go round the team and ask each person which one thing on their plate this week is worth trying it on, and write the answers down. Six named tasks from a team of eight is a good briefing. Zero is the result worth knowing about before the training is booked.
Ask for the real document, not a description of it. “Bring your worst client email” produces the email. “Think about a task this might apply to” produces nothing, because thinking about it later is exactly what does not happen once the meeting ends. The instruction has to be concrete enough that someone can act on it that afternoon: export the spreadsheet, save the transcript, print the contract clause. A task without the actual document attached to it is a task that gets forgotten by the time training starts.
Say what is out of bounds, even though nobody has asked yet. Client data, anything under an NDA, anything that would need sign-off before it left the building. If this is not said in the briefing, it gets decided informally in the training room, by whoever is loudest, and a vague answer in that moment gets remembered as permission long after the meeting is forgotten. This is a one-sentence addition to the briefing and it is cheaper to say once here than to correct once it has already happened.
What follows
Put the briefing in the calendar before you book the training, not after. If the team cannot come up with six tasks worth bringing between them, that is worth knowing now rather than on the day. If you would rather talk it through first, book a 30-minute discovery meeting and we will work out what your own briefing needs to cover before you put anything else in the calendar.
FAQ
Questions we get asked
How long before training should a briefing happen?
About a week. Long enough that people have noticed the tasks they want to bring, short enough that they have not forgotten the briefing happened. A day before is too late to change what anyone brings with them.
Who should run the briefing, the trainer or the manager?
The manager. A trainer explaining what training will cover is a sales pitch. A manager saying which parts of their team's own work are in scope is an instruction, and people prepare differently for the two.
What if the manager does not understand AI well enough to run the briefing?
That is not what the briefing asks of them. The manager is not explaining how the tools work, only naming which parts of their team's existing work are in scope and asking people to bring a real example. Both of those require knowing the team's work, not knowing the technology, so a manager who has never used the tools can still run this meeting well.
Does this apply to a bespoke programme as well as an off-the-shelf course?
Yes, and arguably more. A core AI course arrives with its own examples if a team turns up empty-handed. A bespoke programme is built from what a team brings, so a bespoke session run without a briefing has nothing of its own to build from, and the trainer ends up improvising a generic session anyway, at bespoke cost.
What does it mean if a team cannot name a single task worth bringing?
It means the training is being scheduled before anyone has worked out what it is for. That is worth knowing before the budget is committed, not after, and the honest response is to spend the briefing finding out why, rather than proceeding to a training day with nothing real in the room.
Should the briefing happen in person, or is a short call enough?
A call is enough. The value is in the manager naming the scope and asking for an example, not in the room it happens in. What matters is that it happens roughly a week out and takes no more than an hour, not the format.
Ready to put this to work?
Tell us where your team is with AI and we will tell you honestly what would make the biggest difference.
