Getting it out of your head and onto paper

Every owner-run business has a set of jobs that only the owner can do. Sometimes that is real expertise. Far more often it is a job that only the owner has ever written down, which is to say a job nobody has written down.

The difference matters, because the second kind can be handed over, and until it is written down it cannot be delegated, improved, automated, or sold with the business.

Why this is the step that unlocks everything else

Every conversation about automating something eventually hits the same wall. Somebody asks how the job is done, and the honest answer is well, it depends, followed by twenty minutes of exceptions.

That is not a failure of memory. It is that the process lives in one person's judgement and has never been made explicit. And nothing can take on a job in that state: not a tool, not a new hire, not an assistant.

This is also why so many businesses that buy software end up disappointed. They bought a solution to a process that had never been described. The software was fine. There was nothing for it to grip.

Do not write it. Talk it.

Here is the part that makes this achievable. Writing a procedure is miserable and it is why everybody puts it off for years.

So do not write it. Next time you do the job, open the voice recorder on your phone and narrate it like you were training somebody standing next to you. Say what you are doing and why. Say the exceptions as they occur to you. Say and this is the bit that goes wrong when it goes wrong.

Fifteen minutes of that recording contains more usable detail than two hours of trying to write it down, because you already know how to explain your own work out loud. It is the transcription and the tidying that feels like homework, and that part is exactly what an assistant is for.

Which job to start with

Not the most important one. Start with the one that fits all three of these:

• It happens often enough that somebody does it weekly.
• If it is done wrong, you find out quickly and nothing catastrophic happens.
• You would genuinely like to stop being the person who does it.

Opening procedures, intake, how a job gets scheduled, how an invoice gets raised, what happens when a customer complains. Boring, frequent, recoverable. Start there and get one finished, because one finished procedure changes how the whole thing feels.

What you can do once it exists

A written procedure is not filing. It is a tool, and it immediately does four jobs.

• It trains people. New hires stop interrupting you with questions that have an answer.
• It shows you the waste. Almost nobody reads back their own procedure without spotting two steps that exist for no reason any more. This alone is often worth the hour.
• It becomes the brief. Paste the procedure in alongside a real case and an assistant can do meaningful parts of it, because it finally has the context it was always missing.
• It is an asset. A business whose operations exist only in the owner's head is worth measurably less than the same business with its procedures written down. Ask anyone who has sold one.

Getting the team to do it too

Do not announce a documentation initiative. People hear “I am being replaced” or “more paperwork”, and both readings kill it.

Do it yourself first, for one of your own jobs, and show people the result. Then ask one person to narrate one job, and do the tidying up for them so their entire contribution is fifteen minutes of talking. Once somebody has been handed a clean written version of their own work, with their own words in it, the resistance tends to evaporate. People like seeing what they do taken seriously.

One job a week. In three months you have the operating manual you have been meaning to write for years.