How to get knowledge out of one person's head: writing procedures that people use 

Document a process by following it once with the person who does it, writing one page in their words with the trigger, steps, checks and exceptions, and then having someone else run the task from that page. Keep procedures short, keep them where the work happens and review them when something goes wrong.

A standard operating procedure, or SOP, is a short written description of how a task is done, so that anyone trained can do it the same way. The point is not paperwork. The point is a business that keeps running when one person is away.

Why does the business run smoothly only when one person is in?

Every business has someone who just knows. She knows which customer pays late, how the stock sheet really works and which supplier to call when a delivery slips. When she is in, the work flows, and when she is on leave, small things go wrong without anyone quite knowing why.

That knowledge usually grew by habit rather than by plan, and it now lives in one head, a trail of messages and a few private spreadsheets. It is valuable and it is fragile. If the person leaves, the business pays to learn it all over again.

Writing it down is the cheapest protection there is, and it also makes the work easier to teach, to check and to improve.

What should you document first?

Do not try to document everything at once. Start with the tasks where a gap would hurt most, and ask three questions of each one.

• Does it happen often, such as every day or every week?
• Would a mistake cost money, a customer or a legal problem?
• Does only one person know how to do it?

Any task that gets a yes to two or more goes first. Common starting points are raising an invoice, onboarding a customer, month-end closing, handling a complaint and ordering stock. Aim for five procedures in the first round, not fifty.

What is the one-page procedure format?

One page forces clarity, and if a task will not fit, it is probably two tasks. Use the same headings every time so people learn where to look. This template works for most routine work.

Write in short sentences and plain words, the way the person actually talks, and add screenshots wherever a screen is involved. Say go to the invoice tab and select the customer, not initiate the invoicing workflow.

How do you get the person to write it down?

Asking an expert to write a manual in their spare time rarely works, because the spare time never comes. Sit with them and watch the work instead.

1. Pick one task and agree a time. Thirty to sixty minutes is enough.
2. Ask them to do the task as normal while you watch and take notes, asking why at each step.
3. Write the page straight afterwards, using their words, and send it to them to correct.
4. Ask someone else to run the task from the page alone, without help, while the expert watches quietly.
5. Fix every point where the new person stops or guesses. Those are the gaps.
6. Save the final page where the work happens and tell the team where it is.

The test in step four matters most, because a procedure that only its author can follow is not really a procedure. Treat every question from the new person as a missing line on the page.

Thank the expert, and be clear about what they gain: fewer interruptions, fewer calls while on leave and credit for their know-how. People write down what they know more willingly when it does not feel like they are making themselves replaceable.

What does a finished procedure look like?

Take a simple task such as raising an invoice. A good page names the owner and states the trigger, which is a job being marked complete. It lists the inputs: the signed order, the agreed rate and the customer record. The steps are short: open the job, check the rate against the order, create the invoice, review the total, send it and record the date.

The checks come next: the invoice number is unique, the customer name matches the record and the total matches the order. The exceptions cover what to do when the rate is missing, when the customer asks for a change or when the job is only part complete, and each one names who to ask. Finally, the output is stated: the invoice is sent and the date is in the record.

Notice what the page leaves out. It does not explain why the business invoices, and it does not repeat company policy. It holds only what a trained person needs at the moment they do the work, because background belongs in training rather than in the procedure.

How do you train people on a new procedure?

A page on its own is not training. Walk the new person through it once with the page open, then let them do the task while you watch, answering questions by pointing to the page. After that, ask them to run it alone and tell you where it was unclear. Update the page the same day, while the question is still fresh.

Make using the page the normal way of working. If people can simply ask the expert instead, the page will go unused and drift out of date. Say it kindly and often: check the page first, and tell me if it is wrong.

Start small and show a result. After the first five procedures, count how many questions the team asks the expert in a week and compare that with before. A visible fall is the best argument for doing the next five.

Why do most procedure manuals die, and how do you keep yours alive?

Manuals die for ordinary reasons. They are long, so nobody reads them, and they sit in a folder nobody opens. They go out of date, and the first time one is wrong, people stop trusting all of them. Above all, nobody owns them.

Four habits keep yours alive.

• Keep each procedure to one page, so it is easy to read and easy to update.
• Store it where the work happens, such as a link inside the tool or a shared folder everyone already uses.
• Give each procedure an owner who is responsible for keeping it right.
• Review a procedure whenever something goes wrong with that task, because a failure shows exactly what the page missed.

A light yearly check also helps. Ask each owner to confirm the page is still true or to fix it, which takes minutes and stops quiet drift.

Once procedures are short, clear and in one place, a further benefit follows. Staff, and in time an AI assistant, can answer everyday questions from them instead of asking the founder. That only works if the pages are accurate, which is one more reason to keep them current.

If many of your processes sit in one head and you would like help getting them out, this is routine work for a business services team, usually done alongside a short review of how the business runs today.