Documenting your processes without losing six months

To document business processes is to write down how the work really gets done, clearly enough that a competent person can do it without calling you. It doesn't take six months. With the right method, a small business's key processes can be documented in a few weeks: each person writes what they do, you record, you test, you file.

Why most documentation projects fail

Almost every owner has tried. A binder, a shared folder, a New Year's resolution. Then the emergencies come back, and the project dies on page 12.

It isn't a lack of will. It's a method problem. Failed projects almost always share the same three flaws:

• The owner writes everything. They're the busiest person in the company, and often the one who knows the least about the details of daily work.
• The goal is perfection. You want a complete, well-formatted manual that covers every case. Nobody finishes it, and nobody reads it.
• You start at the wrong end. You document what's easy, not what's expensive when the right person is away.

The good news: if you've already done your business process mapping, you know where to start. The steps marked in red, the ones that go through you or through a single employee, are your priorities.

The method in five moves

This is the method we use in step 5 of the path. It fits on one page, and it works because it spreads the work around.

1. Have the person who does the work document it

The billing clerk documents billing. The shop foreman documents production scheduling. You document what only you do: complex quotes, negotiations with certain suppliers, pricing decisions.

Give each person a simple template and one hour a week. No more. Rhythm matters more than speed.

2. Record before you write

Writing is slow. Talking is fast. Ask the person to do the task as usual while their screen is recorded or their hands are filmed, and to explain out loud what they're doing. A 15-minute transcript becomes a one-page procedure in half an hour of work.

No special equipment needed: a phone is enough to film a task on the shop floor, and the screen recorder built into your computer or video-call software handles anything on a screen. Keep the files on company systems, not on someone's personal phone: they often contain prices and client names.

3. Boil it down to a checklist

A useful procedure fits on one page. It says what to do, in what order, with which tool, and what to check before moving on. The detail goes in an appendix or in the video. To go further on format, read our guide to writing procedures employees actually use.

4. Have someone else test it

This is the step most often skipped, and the most important one. A procedure is only good if another person can follow it without asking questions. Every question asked during the test reveals a gap. Fix it on the spot.

5. Store everything in one place

One folder, a simple structure, one owner per document and a review date. If procedures are scattered across emails, USB keys and notes taped to the wall, they don't exist as far as a buyer is concerned.

An example in the Eastern Townships

Here's a made-up but familiar case: a builder of docks and boat lifts in Magog, working mostly for shoreline owners on Lake Memphremagog. Four million dollars in revenue, 28 employees, a 61-year-old owner who's thinking of selling in three years.

At the start, nothing is written down. Every quote goes through the owner. Shop scheduling lives in the foreman's head. Billing is handled by an assistant who has done it "her way" for 15 years.

The owner decides to try the method. He picks eight processes: quoting, shoreline and depth survey, material ordering, shop scheduling, manufacturing, launch and installation, billing, fall removal and storage. He names an owner for each.

Every Tuesday afternoon, one person records their process while doing it. The assistant turns the recordings into one-page checklists. On Friday, someone from another department tests the procedure and notes their questions.

After two months, all eight procedures exist and have been tested. The owner did his last: three recorded interviews on how he builds a quote, with his pricing rules and exceptions. That know-how was the most valuable of all. Our article on knowledge transfer shows how to capture it.

Nobody stopped working to make this happen: a few hours per person, spread over eight weeks. And when the owner takes a week off in July, the shop keeps running.

Your one-page template

Copy this template for each process. It's enough to start this week.

• Process name: for example, "Prepare a quote".
• Trigger: what starts it (a call, an email, a date).
• Expected result: what must exist at the end.
• Owner: one person, plus a named backup.
• Tools: software, forms, files used.
• Steps: 5 to 15 lines, each starting with a verb.
• Checkpoints: what gets verified before moving on.
• Common mistakes: what goes wrong, and how to fix it.
• Video link: if software is involved.
• Last review date: and who did it.

For this week, do just three things: pick your five riskiest processes, name an owner for each, and get the first one recorded.

What it changes when you sell

A buyer won't read every procedure. But during due diligence, they'll ask to see them, and they'll ask your employees a simple question: "How do you handle this when the boss isn't here?" If the answer is "it's written down, let me show you," you've just lowered the risk they see.

These procedures then become the foundation of your Transition Document, the guide that lets a successor run the business without you. Without them, that document is a promise. With them, it's proof. They also go hand in hand with clear roles and responsibilities, because a procedure without an owner doesn't last long.

One last point: documentation ages. Put a yearly review date on every procedure, and make updating it part of the owner's job, not a special project. A buyer can tell the difference between a folder built in a hurry before a sale and one the team has been using for two years.

Documentation isn't a goal in itself. It's what makes your systems transferable, and it's what makes a business independent of its owner.

Do it with a pro

Alone, this work gets done in bits and pieces between emergencies, and it often drags on for over a year. With us and our regional partner, we run the interviews, structure the documentation and use tools that turn recordings into procedures. Your employees spend a few hours on it, not weeks.

Owner independence