> Markdown version of https://www.growthtkms.com/guides/document-a-process.html
> TK Management Solutions LLC, Henderson, Nevada. Generated from the published page.

# How to document a process so it runs *without you*

Most small business processes live in one person's head, and that person is you. Here is a five-step method that takes an afternoon per process, plus the reason most SOP folders are abandoned by month three.

By Tristan Albach, PMP · Updated August 17, 2026

The short answer

Pick the process that **only works when you run it**. Record yourself doing it once. Turn the recording into a draft, correct the draft, and **put it where the work happens**, not in a folder. Then have someone else run it while you say nothing. That last step is the whole test.

Every owner has a version of this thought: "I can't take a week off, because nobody else knows how any of this works." The instinct is to write everything down. That instinct produces a folder of documents that are accurate for about six weeks.

The problem isn't discipline. It's that most process documentation is written from memory, stored away from the work, and owned by nobody. Fix those three things and one afternoon of writing outlives a year of good intentions.

## The five steps

1. **Pick the process that costs you money when it slips**
   Not the most complicated one. The one where a dropped ball has a price. For most small businesses that's lead intake: what happens between someone asking about your work and that work being scheduled. If a lead can go quiet for four days without anyone noticing, start there.
2. **Record yourself doing it, once, out loud**
   Screen recording, phone voice memo, whatever is nearest. Narrate as you go, including the parts that feel too obvious to say. Those are the steps a new person gets wrong. This is the step that turns a three-week writing project into an afternoon, because you're describing what you're doing instead of remembering what you do.
3. **Draft it, then correct it**
   Turn the transcript into numbered steps. AI is genuinely good at this part and genuinely bad at the next one: it will produce confident steps that are not how your business works. Read every line and fix what's wrong. The draft saves you the blank page, not the thinking.
4. **Put it where the work happens, with one name on it**
   A document in a folder nobody opens is a snapshot. Attach it to the tool where the work already runs, so someone doing the job sees the steps without going to look for them. Then put one person's name on it as owner. "Everyone maintains it" means nobody does.
5. **Have someone else run it while you stay quiet**
   This is the test, and it's uncomfortable on purpose. Every question they ask is a gap in the document. Write the answer into the document instead of saying it out loud. Two runs of this and the process genuinely belongs to the business instead of to you.

## What a usable process page contains

| Section | What goes in it | Why it matters |
| --- | --- | --- |
| Trigger | The event that starts it | Without it, nobody knows when to begin |
| Owner | One name, not a team | Shared ownership is how things go quiet |
| Steps | Numbered, with the actual click paths | "Update the system" is not a step |
| Done looks like | The observable end state | Tells you whether it actually finished |
| Exceptions | The two or three weird cases | Where every "just ask me" question comes from |

If the page runs past one screen, the process is probably two processes.

## Why most SOP folders die in month three

**They were written all at once.** A documentation sprint produces twenty pages, and twenty pages go stale together. One process a month, documented when you next run it, survives.

**They live away from the work.** If the steps are in a shared drive while the job happens in an inbox, nobody opens the drive. The document has to be one click from the task, or it may as well be in a filing cabinet.

**Nothing forces an update.** The only reliable trigger is the run itself: when the document is wrong, whoever hit the wrong step fixes it right then. Two minutes during, versus a rewrite in six months.

**They describe the ideal, not the real.** If the document says one thing and everyone does another, the document is fiction and people stop trusting all of them. Write what actually happens, then improve it on purpose.

## What this actually buys you

The obvious win is that you can take a week off. The bigger one is that a documented process can be improved. You cannot fix a process that only exists in someone's head, because there's nothing to point at. Once the steps are written down, "this takes too long" becomes a conversation about step four instead of a general complaint.

It is also what makes hiring survivable. The cost of a new person is not their wage, it's the weeks of your attention they need before they're useful. Documented processes turn that into a reading assignment. If a first hire is on your mind, [the books have to be current enough to support the decision](https://www.growthtkms.com/guides/catch-up-bookkeeping.html) too.

## Process documentation FAQ

### What tool should I use?

Whatever your team already opens daily. Confluence and Notion are built for this and worth it once you pass a handful of processes. Before that, a shared doc linked from the task is fine. Choosing a tool is the most common way to spend three weeks documenting nothing.

### I'm a solo owner. Is this worth doing?

Yes, for two reasons that have nothing to do with delegation. Written steps are how you stop rebuilding the same decision every quarter, and they're the asset that makes your first hire cheap instead of expensive. Documenting before you need to is the whole point.

### How detailed should the steps be?

Detailed enough that someone competent who has never done it can finish without asking you. That usually means naming the actual buttons and fields. The test in step five tells you exactly where you were too vague, which is more reliable than guessing at the right level up front.

### How many processes do I actually need?

Fewer than you think. Most small businesses run on about five that matter: getting a lead, quoting it, delivering it, invoicing it, and closing the month. Document those and the rest are variations you can work out on the day.

---

Full site index and guidance for AI agents: https://www.growthtkms.com/llms.txt