What the Trainer Can't Guess About Your Team

Most training days don't fail in the room. They fail a fortnight earlier, when a line manager clicks 'book' and sends a calendar invite with no context. The trainer arrives with a solid course, a flipchart and a deck built for 'a team like yours'. But yours isn't quite like that. It has its own stuck bits, its own shorthand, its own Monday morning reality. An hour spent telling the provider about it is the cheapest customisation you'll ever buy.

The trainer isn't psychic

External trainers are good at reading a room once they're in it. They can spot the sceptic at the back, the person who's been volunteered, the one who's quietly relieved to be out of the office. What they can't do is guess what happened last month, which system keeps falling over, or why the words 'month-end' make half the team go quiet. If you don't tell them, they'll fill the gap with generic examples. Generic examples are fine. They're just not yours.

What's actually worth saying

A useful pre-course brief isn't a procurement document. It's a note from someone who knows the team. Keep it to two sides of A4 and focus on four things:

• The live problems. Not 'communication could be better' but 'two teams keep duplicating work because nobody owns the handover'.
• The language that lands. What do people actually call things? If the team says 'the board' when they mean the weekly priorities meeting, say so.
• The behaviours you want to see at the desk. Two or three, max. 'Speak up in handover' is a behaviour. 'Be more confident' isn't.
• What good looks like a month later. A shorter meeting, fewer escalations, a checklist that actually gets used.

That's it. You're not designing the course. You're giving the designer raw material.

The two-page brief I'd copy

Here's a template I've used and recommended. Adjust the headings to taste; the structure matters more than the wording.

Page one: the team and the problem

• Team name and size:
• What the team is responsible for (one sentence):
• The three things that are working well:
• The two or three things that are stuck (be specific, with an example):
• What we've already tried:
• What happens if nothing changes:

Page two: the day and the follow-up

• Who's attending and why (note anyone who's sceptical or volunteered):
• The language and examples that will land:
• The language and examples to avoid:
• Two or three behaviours we want back at the desk:
• What 'good' looks like four weeks after the course:
• Who will check in with attendees afterwards:

You can fill this in during a single sitting. The trick is to write it as if you're briefing a new colleague, not pitching to a client.

Keep it short, keep it honest

There's a temptation to make the brief sound impressive. Resist it. The trainer doesn't need the polished version; they need the real one. If the team is exhausted after a reorganisation, say that. If half the room thinks the course is a box-ticking exercise, say that too. A good provider will use it. A poor one will ignore it, and you'll know something useful before the day begins.

Also: don't wait until the week before. Send the brief when you book, then offer a 20-minute call. That call is where the trainer will ask the questions the form didn't cover. It's also where you'll hear whether they've actually read it.

The bit people skip

The final section — what good looks like a month later — is the one most people leave blank. It's also the one that turns a nice day into a change in behaviour. A month after the course, someone should be able to point at something and say 'that's different because of what we did'. If nobody can, the training wasn't necessarily bad. It just wasn't pointed at anything.

An hour well spent

Customisation doesn't have to mean a bespoke programme with a six-figure price tag. Often it means telling the trainer what your team actually does all day. That's an hour of your time, a couple of pages, and a short call. Compared with the cost of a wasted day — the room hire, the backfill, the train fares, the quiet frustration of a team who've heard it all before — it's a bargain.

For UK teams especially, where training budgets are scrutinised and diaries are tight, that short brief is a simple way to make sure the day earns its place. It also gives you something to measure against afterwards, which is more than most booking confirmations can offer.

So before the trainer arrives, send the brief. Tell them what Monday morning actually looks like. It's the difference between a course that happens to your team and one that's built for them.