The Two Weeks After Training

What Is the Problem?

Three scenes repeat after training.

The person returns to their old method

Training ends, they return to the desk, work is waiting. The new method demands extra thinking each time, so on a busy day the old road gets taken. Two weeks later the learning has faded. A month later it is not remembered at all, and the hours spent are gone with it.

Permission gets waited for

The person wants to try what they learned but is unsure. May I use it? In which job, with which data? Nobody takes a risk under ambiguity. And the awaited permission never comes, because nobody gives it. Silence reads as prohibition, though usually nobody even thought about it.

The result never gets told

Even someone who tries it does not mention it. An untold trial leaves no trace in the organisation. Six months later somebody else tries the same thing from scratch, with the same mistakes. Because nothing was recorded, experience never accumulates.

Why Does It Happen?

Three reasons.

Training gets abandoned at the finish

Attendance is logged, a certificate issued, the file closed. Yet the real work starts there. If no step is defined after training, the process ends by itself. Nobody is acting in bad faith; the next job is simply waiting.

There is no space to try

Trying a new method carries the risk of error. If no space opens for that risk, nobody tries. Research also names the two barriers to application as time and management support. Both sit in the manager’s hands.

Nothing gets measured

Was it tried, did it work, by how much? These questions do not get asked, so the result stays unknown. An unmeasured gain cannot be defended. And it gets dropped at the first difficulty.

How Is It Done?

The transfer task builds in three steps.

Step 1: write the task before the training

Before sending anyone to training, form this sentence: “When you come back, you will try this job with that method.” Someone who goes knowing the task listens differently. They take notes. They ask questions. They translate examples into their own work. So the task starts the transfer before the training does. The same training produces a different result, and the only difference is a task assigned in advance.

Step 2: set two weeks and two numbers

The task must carry a date. Two weeks is enough; longer blends into daily work and the boundary blurs. Beside it write two numbers: how long does this job take now, and what is the target? Without numbers the result ends with “it seemed fine”. Two numbers end the argument. Keep them simple: time, count or error rate, whichever fits your work.

Step 3: have the result told in ten minutes

At the end of two weeks, a short sharing. What did you try? What came out? Where did you get stuck? Those ten minutes do three jobs at once. They verify transfer, spread the knowledge to the team and produce an example for the next person. The internal trainer arrangement makes these sharings permanent.

How Long, Where to Start?

An almost costless arrangement.

Ten minutes to set up, two weeks to run

Writing the task takes ten minutes; one sentence suffices. The application runs two weeks and the sharing ten minutes. So the extra cost is close to nothing. In return, the odds of the training reaching the work rise markedly. The difference is whether you get the value of hours already spent.

The return is recovering the training budget

Most of the hours spent on training normally go to waste. The transfer task reduces that loss. So the real gain is not adding something new. It is rescuing what was already spent.

First step: try it at the next training

You do not need to build a new system. Tell the next person you send about the task upfront. One sentence: “When you return you will try this, and in two weeks you will explain it for ten minutes.” That single sentence changes the outcome of the training. If you hold a level ruler, choosing the task gets easier too.

The Common Mistake

Three traps.

Choosing too big a task

The first transfer task should be small and clear. A large task does not finish in two weeks and stays half done. And a half-finished first attempt makes the second harder. A small task that gets completed is worth more than a large one that does not; in the first round the aim is finishing, not winning.

Asking for the result only if it succeeded

“It didn’t work” is a valid answer too. Someone explaining where they got stuck teaches the team a great deal, sometimes more than a success would. An arrangement that only wants successes hides the failures. And learning stops.

Turning the sharing into a meeting

Ten minutes means ten minutes. No presentation gets prepared. No slides get made. The screen opens and the work gets shown. A format that grows heavy leaves nobody volunteering in the second round. Staying light is essential.

Frequently Asked Questions