You get a business out of your head by capturing it in the order it interrupts you, not by sitting down to write everything at once. Keep a running note for two weeks of every question you answer and every decision only you make, then turn the most frequent items into short written rules. This works because it captures the knowledge that is actually needed, rather than the knowledge you think is important.
Every owner in this position has attempted the big weekend documentation project at least once. It starts well, becomes tedious around hour three, produces something incomplete, and then sits unfinished as a small ongoing reproach. The method below exists because that approach reliably fails. Getting this right is the foundation of the systems work we do with professional services and local teams.
Why the big documentation project doesn't work
You cannot see what you know. Expertise becomes invisible. The things you do automatically are exactly the things you will not think to write down, because they do not feel like knowledge, they feel like obvious.
You document the wrong things. Sitting down cold, you write the impressive processes. The knowledge actually blocking your team is usually smaller and more mundane.
It has no natural end. A business contains an unlimited amount of documentable detail, so the project never feels finishable, and unfinishable projects get abandoned.
The method: let the interruptions write it for you
For two weeks, keep one running note on your phone. Every time someone asks you something, or you make a decision nobody else could have made, add one line. Just the question, nothing else. Do not organize it. Do not answer it in the note. One line each, as it happens. At the end of two weeks you will have a list, and the frequent items on it are the exact knowledge your business needs extracted from you. Not a theoretical list. A measured one.
Sort what you captured
Most items fall into four types, and each needs a different fix:
Facts. Prices, hours, specifications, supplier details. These need a single shared reference document, and that is the entire fix.
Rules. "Can we give this customer a discount?" These need a decision boundary written down, as covered in our bottleneck article.
Processes. "How do I do this?" These need a short SOP.
Judgment. "Should we take this job?" These are the hardest and need worked examples rather than rules.
Handle them in that order. Facts are almost free to fix and often account for a surprising share of interruptions.
Fixing facts: one shared reference
Create one document containing every fact people ask you about. Prices, hours, what is included, supplier contacts, standard timeframes, the wifi password. Two rules keep it alive: one named owner responsible for keeping it current, and it lives somewhere people can reach on a phone in seconds. This document is unglamorous and it will remove more interruptions than anything else you do.
Fixing rules: write the boundary, not the answer
For every recurring "can I..." question, do not answer the specific instance. Write the general boundary. The test of a good boundary: your staff can answer the next twenty versions of that question without asking. If they still need to check, the boundary is too narrow or too vague.
Fixing processes: short, sequential, where the work happens
Covered fully in our SOP article. The short version: one page, in the real order, with what "done right" looks like, kept where the task is performed.
Fixing judgment: use worked examples
Judgment resists rules, which is why it stays stuck in your head longest. The workaround is examples. Instead of trying to articulate a rule for "should we take this job," write down five real jobs, three you took and two you turned down, with a sentence each about why. People learn judgment from cases far more readily than from principles, and this takes twenty minutes rather than the hours you would spend failing to write the perfect rule.
Do it in small pieces, permanently
Rather than a project with an end date, make it a habit with a small slot: thirty minutes a week, working through the top item on your list. Thirty minutes weekly is roughly twenty-five hours a year of documentation, which is far more than any weekend project produces, and it targets what is actually blocking people because the list keeps regenerating from real interruptions.
Involve your team, for two reasons
Have your staff write the processes they perform. First, they know details you have forgotten. Second, a process written by the person who does it gets followed, while a process written at them often does not. Your job shifts from author to editor, which is both faster and produces better documents.
What to expect after a month
Interruptions drop, but not evenly. The factual questions disappear quickly. The judgment questions persist longest, which is correct and expected. You will also discover something uncomfortable: some of what was in your head was inconsistent. You have been making the same call differently on different days without noticing. Writing it down forces a decision, and that decision is usually an improvement in itself.
The part nobody mentions
Getting things out of your head changes how it feels to run the business, and not always comfortably at first. Being the person who knows everything is a form of importance. Watching your team handle things competently without you is genuinely good and can also feel like a small loss. Worth naming, because owners often sabotage this quietly at exactly the point it starts working.
When the list is too long to start
If two weeks of logging produces sixty items with no clear pattern, that usually means the business grew without any deliberate design and now depends on you in dozens of small unrelated ways. That is common and it is not something a single document fixes. It is also very hard to prioritize from inside, because every item feels equally urgent when they are all interrupting you. A readiness checklist can help you see the shape of it.