All articles

Training

Why your AI training stops working three months later

Agile UP, 1 min read

A day of demos gets everyone excited. Three months later, few habits have survived. The cause almost always lies in the format.

Agile UP, 2 min read

The great-day syndrome

The trainer shows impressive things. Participants leave with a list of prompts to try. The following Monday, urgent files take their place again, and the list ends up in a drawer. Nobody lacked willpower: we quickly forget what we haven’t practised on our own work.

Start from real files

Everything comes down to one simple point. During the training, everyone works on their real files. The salesperson rewrites a real proposal in progress, the accountant processes a real batch of invoices, the manager prepares their real meeting for the next day. People leave with a result already produced, and above all with a habit they have carried out themselves at least once.

Space it out rather than packing it in

Two half-days two weeks apart are worth more than one full day. In between, everyone tries, gets stuck, and comes back with precise questions. The second session starts from those real difficulties rather than from a fixed programme.

Train managers first

A team adopts a new practice when its manager uses it too. If the manager keeps asking for reports the old way, the team will go back to the old way. Starting with management, even for two hours, changes a great deal of what follows.

Measure at three months

The measure that counts comes three months later. Who still uses what they learned, and for what? A short questionnaire is enough. If it reveals little use, face it squarely: it’s the most useful signal for adjusting what comes next.

Next article Leading a transformation without breaking your teams