The gap is rarely technical

When a new system, brand or automation does not take hold, the post-mortem usually blames the technology. In our experience the technology works. What was missing was half a day of somebody sitting with the team, on their own work, answering the questions people are too busy to raise in a group email.

Training is treated as a line item to trim because it produces nothing you can screenshot. It is also the cheapest insurance available on the rest of the budget.

Why in person still wins

A recorded video answers the questions you predicted. A person in the room answers the ones you did not, and notices the two people quietly nodding without following. That noticing is the whole value, and it does not survive being turned into documentation.

What a session actually looks like

1. Start with their work, not our slides. Real cases, real files, from this week.

2. Show the thing once at full speed, then let them do it while we stay quiet.

3. Collect every hesitation. Each one is either a training gap or a design flaw, and both are useful.

4. Agree who owns it afterwards, and how they get help without opening a ticket.

5. Leave one page of notes written in their language, not ours.

Two hours structured like that will move adoption further than a fortnight of documentation. It also gives us the honest list of what to fix next, which is difficult to obtain any other way.

A recorded video answers the questions you predicted. A person in the room answers the ones you did not.

This applies to brand as much as software

Handing over an identity without teaching it produces the same failure as handing over a system without teaching it. Within a month somebody is stretching the logo to fit a slide, because they were given files and rules but never watched somebody use them well.

• Brand sessions: making a real slide, post and proposal cover with the new system, in the room.

• CMS sessions: publishing a genuine page, including the awkward one with a table in it.

• AI and automation sessions: where judgement stays with a person, and what to do when an output is wrong.

• Refreshers when the team changes, because knowledge leaves with people.

Budget for it deliberately

If a project has a training line worth roughly a tenth of the build, adoption tends to look after itself. If it has none, expect to spend more than that later on support, corrections and the slow erosion of whatever was delivered. The money gets spent either way; only the outcome differs.