Everything you hand over keeps coming back
You delegated it. You explained it properly. You even sat with them while it got done. A month later it is on your desk again, and the obvious conclusion is that you hired the wrong person. Usually it is not that.
You hand something over. It comes back wrong, or it does not come back at all, and you take it into your own hands again because that is faster. Thirty days later you still own it. This is the rule that decides whether a handover sticks, and almost everybody breaks it while believing they are training someone.
The rule
The expert narrates and reviews. The successor executes and owns.
You cannot touch the keyboard.
If the expert does the work while the successor watches, nothing transfers. It feels efficient, it looks like training, and thirty days later the successor still cannot do it alone. The expert has to sit on their hands and let the job be done slower and worse than they would do it, because doing it badly is the mechanism, not a cost of the mechanism.
This applies identically to handing over a system, a process, or a whole role.
Repetition and iteration are not the same thing
Repetition is doing the same thing the same way, many times. It produces familiarity and almost no improvement, which is why someone can do a job for twenty years and be no better at it than they were in year three. Iteration is doing it, noticing what went wrong, and carrying that into the next attempt. Only the second one moves anybody up.
So the goal of any training is never that they understood it. It is that they did it, did it badly, and came back with something they learned. Design for that and everything else follows.
Why you cannot explain your own best work
Once something is truly learned it becomes automatic, and automatic things are invisible to the person doing them. Tying a shoelace is impossible at five and unconscious at eight. Ask an adult to explain it in words and they have to slow down and mentally re-run it, and they will still miss a step.
The same is true of an owner who has run their process for fifteen years. They are not being unhelpful or evasive. They genuinely cannot see it, which is why they contradict themselves and why direct questions produce vague answers.
Why the training session on its own changes nothing
You run the session, everyone nods, and a fortnight later the work looks exactly as it did before. The session was never the mechanism. It transferred information, and information is not capability.
Homework
Small, specific, and due this week. Not a principle to remember, a thing to go and do.
Accountability
A short check-in soon after, where they show you what they actually did.
Frequent first, then tapering
Daily for the first fortnight, then weekly. The support comes off gradually rather than all at once.
Deliberate positive reinforcement
Changing a habit is uncomfortable and people repeat what gets noticed. Acknowledge the small correct behaviour the first time it happens, not the tenth.
Train the whole layer at once, never by relay
If the same gap shows up in three or more people, stop coaching them individually. Run one session for all of them, to one standard, and put the enforcement inside a meeting that already exists rather than creating a new one.
Training one person and having them pass it on loses most of the content and produces several slightly different standards. It is the same defect as a handover where the expert kept hold of the keyboard.
None of this is fast, and that is the honest part. A handover done properly costs you more time in the first month than doing the work yourself would have. It is the only version that costs you less in the sixth.
Handing over the work is most of the job
Developing a second in command and getting the owner out of the day to day is a third of what I actually do inside a business. The strategy call is free and you keep the plan either way. If the timing is not right, the community costs nothing.