Write Down How You Do It

It's all in your head, and that's the problem

In most small businesses, the knowledge of how things actually get done lives in one or two people's heads. How a new client gets set up. What goes into the monthly invoice run. Which steps happen when a job is finished. Nobody has written any of it down, because everybody already knows it.

That works fine until you want to hand something off, until someone is out sick, until you hire, or until you want to automate a step. Then you discover that the process you've run a thousand times is surprisingly hard to explain.

What it costs to keep it undocumented

The cost shows up in ways that don't look like a documentation problem.

Training a new person takes weeks of over-the-shoulder watching instead of days. Work gets done slightly differently every time, so results vary. Steps get skipped when things are busy, and nobody notices until a customer does. You can't delegate the task, so you keep doing it yourself. And you can't automate any of it, because nobody can say precisely what "it" is.

That last one matters more every year. Every automation tool, and every AI tool, needs the same thing first: a clear description of the steps. If you can't write it down, you can't hand it to anyone, human or otherwise.

Start with the ones that hurt

Don't try to document the business. Pick the two or three things you do over and over that you'd most like to stop doing personally. Onboarding a new customer. Closing out a job. The end-of-month routine.

The right first target is usually whatever you'd have to explain if you were out for two weeks.

Keep it embarrassingly simple

Process documentation has a reputation for being a big formal project. It doesn't have to be, and the fancy versions are usually the ones nobody keeps up.

• Write it as a numbered list of steps, in plain language, the way you'd tell a new hire.
• Do it while you're doing the work. Run the task and write down each step as you take it. Far easier than trying to remember it later, and you'll catch the steps you'd forgotten you do.
• Name the tools and where things live. "Log into the billing system" is useless. Say which system, and where the file goes.
• Note the judgment calls. The parts where you decide something are the parts that are hardest to hand off. Write down what you're deciding between.
• Record it if writing is a slog. Talk through the task on a screen recording, then have that turned into a written list.

One page per process is usually plenty. If it runs to five pages, the process itself is probably too complicated.

Put it somewhere findable, and let it change

Keep everything in one place your whole team can reach - a shared folder, a shared document, whatever you already use. Documentation nobody can find is the same as none.

Then treat it as a living thing. When the process changes, change the page. When a new person follows it and gets stuck, that's the sign of a missing step; have them fix it. The people who use it should be the people who maintain it.

The bottom line

Writing down how you do something is the cheapest first step toward delegating it, hiring for it, improving it, or automating it. None of those are possible while the process only exists in your head.

Pick the one task you'd most like off your plate. Do it once with a notepad open. That page is worth more than any tool you could buy this month.