How Does Your Team Learn?

What Is on the Agenda?

Five findings on the table.

The transfer problem is universal

No sector or country escapes it. Studies keep implicating the surroundings rather than the teaching. Someone finishes a course, sits back down, and the familiar routine takes over within days. The unfamiliar method asks for a moment of deliberate choice, and that moment rarely survives a full inbox. Hence the low transfer rate.

Skill forms at home and never visits work

Official data shows a striking gap: most AI users apply it personally, while professional use stalls at a third. So a ready skill sits in the team without flowing into the work. A skill whose cost has already been paid.

Everyone plans training and the gap stays open

The large majority of employers plan to train their staff. Even so, the skills gap remains the first obstacle. There is a serious distance between planning and doing. Setting a budget is not the same as building a skill.

Tools change faster than learning

The shelf life of a training has shortened markedly. New versions appear within months; methods change, habits get renewed. That makes the annual training calendar unworkable.

The learning gap compounds

A business that falls a year behind falls further the next year. Because a learning team accelerates as the basics settle. So the starting date matters more than the pace. Someone starting early and slowly overtakes someone starting late and fast; continuity beats tempo.

Why Is the Question Being Asked Now?

Four reasons.

Knowledge is free, time is not

Free content is abundant. What is scarce is the time and space to try it. The training budget debate is therefore the wrong debate. The real subject is an hours budget — a business with money but no hours cannot use the training it buys.

Level differences inside the team are wide

Very distant levels sit in the same team. Some use the tools regularly, some have never tried. The gap is measured in months. A single content cannot cover that range, and content that tries stays too general.

Competition runs on learning speed

The tools are open to everyone. The difference forms in learning speed, and what determines speed is not one-off training but the arrangement you build.

Knowledge stays with the person

When an employee leaves, what they learned leaves too. In a business without records, every new arrival starts from zero. The organisation treads water instead of advancing, and last year’s lessons vanish with it.

What Is Wrong?

Four measurement errors break the arrangement.

Measuring success by attendance

How many attended is only a cost figure. How many applied it is the result figure. A business that never asks the second never notices the hours it wastes. Certificate counts document the same illusion. The right question: can this person show what they learned using an example from their own job?

Treating training as a one-off event

One day, one room, one attendance list. That design does not work in a field where tools change several times a year. Learning is not an event but a repeating rhythm. Without a rhythm, knowledge does not accumulate; each time you start again.

Leaving the choice to job titles

The youngest or the most technical person gets picked by reflex. Yet the right candidate is found with four criteria and usually turns out to be whoever has done the job for years. A wrong choice leaves even good training without results. Learning the tool takes weeks; learning the process takes years. Teaching the shorter one is smarter.

Leaving knowledge with one person

If the learner does not explain, the knowledge sits there. When they leave, it goes. Explaining is separate work and takes time; without an assigned duty nobody explains, and everyone returns to their own job. The explaining duty is the only guarantee of spread.

The Real Mechanism

The learning arrangement has four parts.

Part 1: level distinction

Not everyone learns the same thing. Three levels suffice: safe user, applies it to their work, designs the process. Everyone should reach the first. For the third, one or two people are enough; trying to make everyone a process designer produces exhaustion. Many users and few designers is the normal shape. Training given without this distinction fits nobody exactly, and the person who needs it most gets lost in the crowd.

Part 2: the weekly hour

A fixed block in the calendar. The content can change; the hour should not. Without this block, learning falls to spare time. And spare time never arrives. It is the first element that makes learning part of the work.

Part 3: the transfer task

What is learned must be tried on real work within two weeks. The task gets written before the training: on your return you will run this particular job the new way, and a fortnight later you will walk us through what happened. That instruction changes how somebody sits in a course. They stop being an audience and start hunting for what applies to them. In effect, the transfer begins before the teaching does.

Part 4: record and sharing

Three lines after every trial: what did we try, what came out, what did we decide? Add a brief monthly gathering where people report their attempts and their dead ends. The two together keep what is learned inside the organisation.

Who Is Affected, and How?

The same arrangement gets built differently in four settings.

The founder and the one-person business

Here the learner, the decider and the doer are one person. The advantage is speed; the risk is continuity. Without a block in the calendar nothing moves. The record carries extra value here too: the notes you write for yourself today become your first employee’s training material. So keeping records is also part of preparing to hire.

The business working with few people

The scale where knowledge spreads fastest. What one person learns reaches everyone within months. The real risk here is the arrangement depending on a single person: when that colleague leaves, progress stops. Written records and regular sharing reduce that dependence.

The business grown into separate units

Spreading by conversation no longer suffices. Each unit needs someone responsible and content that changes by unit. One central training fits nobody exactly at this scale; a local trainer network works better. Each unit learns through its own examples — the example given to accounting is not the example given to the field.

The business bringing in outside help

Name the person who shadows the consultant before work begins. Nobody shadowing means the expertise walks out at the end of the engagement, and what you paid for was a service rather than a capability. That same invoice could have left something behind.

Decision Order

Four steps, in order.

One: open the weekly block

Open a block in the calendar and name who attends. The duration can be short; what matters is that it repeats. Having the manager use the first session is a strong signal too.

Two: split the levels

Distribute the team list across three levels: safe user, applies it, designs it. That distribution takes a few hours and makes content selection easier. Everyone’s need becomes visible as well.

Three: choose the right person

Run the four checks: process knowledge, patience in explaining, a job that recurs, and genuine willingness. Whoever clears all four goes first. Then give them room. Someone taught halfway ends up concluding the whole thing does not work.

Four: attach the task and the record

A two-week task for every learning, three lines for every trial. Without these two the earlier steps produce nothing: a person gets chosen, an hour gets opened, and the workflow stays the same. Task and record produce the change.

Where to Start?

The first month, four weeks.

Week one: block and distribution

Open the block in the calendar and distribute the team across three levels. Together they take a few hours and lay the ground for everything else.

Week two: identify the candidate

Look with the four criteria and produce one name. Then ask that person: would you like to learn this and explain it to the team? Willingness is half the outcome.

Week three: the first task

One person, one task, two weeks, two measurements. Keep the task small. In the first round the goal is not a large gain but completing the loop.

Week four: the log and the round

Open the shared document and write the first entry. Add the monthly sharing round to the calendar. By month’s end you hold not an intention but a working arrangement.

What Not to Do?

Four application errors stop the arrangement.

Thinking about the task after the training

The task should be written before anyone goes. A task considered afterwards usually never gets assigned. And someone who goes knowing the task listens differently.

Making the learning block negotiable

A block debated every busy week disappears by the third month. It should not be a negotiating item. Shorten the time, shift the date, but do not cancel it; one cancellation easily becomes a habit.

Starting with more than one person

Learners need somebody checking on them and answering questions. Spread that across three people simultaneously and none of them gets it. Sequencing wins on speed, oddly enough: whoever you taught first can coach the next one, which takes the burden off you.

Leaving trials unrecorded

An unwritten trial counts as never having happened. The same idea returns a year later and gets tried again. A few lines prevent that repetition, and nobody has to be asked what was tried; the log holds the answer.

What to Watch?

Four indicators.

The transfer rate

Two months on, ask: where did you use this method? Ask for a concrete example; no example means no application. The question needs no system but shows the real state, and a one-sentence answer is enough.

Continuity of the learning block

How many times did the weekly block actually happen? If the cancellation rate rises, progress has stopped. The block reads like the arrangement’s pulse; if the pulse drops, there is no need to check anything else.

Spread

How many learned it, and how many explained it to someone else? The second number matters more. Unexplained knowledge does not spread. Nor does it stay; it leaves with the person.

Freshness of the log

When was the last trial recorded? If it has been empty for months, there are two possibilities. Either no trials are happening, or the recording habit has died.

How Does This Period End?

Three separations will show.

Those who build the arrangement will speed up

Everyone will hold the tools. The difference will appear in businesses that tie learning to an arrangement. A weekly block, a transfer task and a record; a business running all three will get a little faster every year.

The learning gap will compound

A learning team learns faster each year, because the foundations settle. A business two years behind cannot catch up with two years of effort; a speed difference forms in between as well. That is why starting early beats starting fast.

Businesses that keep records will prove durable

Staff turnover happens everywhere. A business whose knowledge sits in records rides through it without shaking. One whose knowledge sits in people starts again with every departure, repeating the same trainings and the same trials.

A Solid Digital Foundation

Four documents, each one page.

The level distribution

Every name on the team and the level targeted beside it. An annual review is enough; as roles change, so does the distribution.

The block in the calendar

Fixed day, fixed duration, fixed participants. The arrangement’s heart beats here; if the block stops, the rest stops too.

The task template

Which job, which date, which two numbers? The same template gets used after every learning, and preparation drops to ten minutes.

The trial log

Short entries in date order. A year later this log is the business’s learning history and the first thing a new arrival reads.

Frequently Asked Questions