Why most team training is forgotten by Friday

A team spends a day in a workshop. People enjoy it. The feedback forms are warm. Three weeks later, nothing about how they work has changed.

This is the normal outcome of corporate training, and it is expensive — not just the fee, but a day of everyone's time and, worse, the quiet lesson that training is something you sit through rather than something that changes anything.

The failure is rarely the content and rarely the trainer. It is three decisions made before the day begins.

Decision one: training was the wrong instrument

Training changes what people know and can do. It cannot fix a problem caused by something else, and most workplace problems are caused by something else.

If your team is not producing good marketing because no one has decided who the customer is, a marketing workshop will not help. If people are not speaking up in meetings because the last person who did got punished for it, a communication course will not help. If the work is not getting done because there are three competing priorities and no ranking, a productivity session will make it worse by adding a fourth.

The honest question before commissioning anything: if this team already knew how to do this perfectly, would the problem disappear?

If the answer is no, you have a structural problem wearing a training-shaped costume. Buying training for it is how organisations avoid a harder conversation, and everyone in the room can feel it.

Decision two: nobody defined what changes

Most training is commissioned as a topic. "We'd like something on communication." "Can you do a session on personal branding?"

A topic is not an objective. It gives the trainer no way to design and gives you no way to tell whether it worked. At the end you are left with the only measure available — did people enjoy it — which is a measure of the day, not of the outcome.

The alternative is to define the change in observable behaviour before anyone designs anything:

• In six weeks, everyone on this team can explain what we do in one sentence, and they all give roughly the same sentence.
• Our proposals stop opening with our company history and start with the client's situation.
• People raise concerns in the meeting rather than afterwards in the corridor.

Each of these is checkable without a survey. You can look, six weeks later, and know. That single act of specification changes the design of the session more than any other input, because now everything in the room either serves that change or gets cut.

Decision three: the room was built to be watched

You can predict how much a session will change by looking at how much of it is delivery.

If people sit and receive for most of the day, they will leave with the feeling of having learned, which fades within days. The feeling of understanding is produced by watching someone competent do something. Actual capability is produced by doing it badly yourself, in front of others, and adjusting.

This is why the sessions that stick are uncomfortable in specific ways. People present and get responded to. They rewrite their own material, not a case study about a fictional company. They try the difficult conversation out loud with a colleague watching. It is more exposing than a slide deck and it is the only part that survives contact with Monday.

Practical implication for anyone commissioning: ask what proportion of the day participants spend producing something of their own. If the answer is vague, it is low.

Use their real work

The fastest way to make training stick is to stop using examples.

A case study about a fictional company requires participants to do a translation step: understand the principle, then work out how it applies to them. That second step is where the learning is, and in a workshop setting it almost never happens — people do it in theory, agree it makes sense, and go home.

If instead people bring the actual proposal they are writing, the actual homepage, the actual pitch they are giving next month, the translation step disappears. They leave having improved a real thing. The improvement is the proof, and the proof is what gets talked about afterwards, which is what produces the second engagement.

It also exposes the real problems. Generic exercises produce generic difficulties. Real work produces the specific ones — the sentence nobody can write, the claim nobody can substantiate, the question everybody dreads.

What to do the week after

The half-life of an unused skill is short. Whatever people can do at 4pm on the day, they can do less of a fortnight later unless something forces the repetition.

Three things carry most of the weight, and none of them require the trainer:

One assignment within seven days. Not homework — a real piece of work due to a real person, using the thing. The first unsupported repetition is the one that decides whether any of it survives.

A shared reference. Whatever the team agreed in the room — the sentence, the structure, the checklist — written down somewhere they will actually see it. Not in the slide deck attachment nobody opens.

A manager who uses the language. If the person leading the team never refers to any of it again, the team correctly concludes it was an event rather than a change. This is the single strongest predictor and it costs nothing.

The blunt summary

Training works when there is a specific behaviour to change, when people practise on their own real work rather than examples, and when something forces repetition in the following fortnight.

Without those three, you are buying a good day. Sometimes a good day is genuinely what you want — for morale, for a team that has been through something hard, as a reset. That is a legitimate purchase and worth being honest about.

Just do not expect a good day to change how people work. Those are different products, and confusing them is what makes organisations believe training does not work — when what does not work is training bought for a problem it was never able to solve.