How to Get Processes Out of the Founder's Head and Onto Paper

Don't document everything. Document what keeps interrupting the founder. For one week, keep a tally of every time someone asks the founder a question, requests an approval or waits for the founder to do something. Note the topic each time.

At the end of the week, sort the tally by frequency. The tasks that appear five times or more are your first candidates. Then filter for two traits: the task follows a repeatable sequence, and a capable colleague could do it with clear instructions. Judgment calls that depend on years of context (which customer to fire) belong in a different conversation about decision rights, not in an SOP.

Aim for ten tasks. Rank them by how many hours per month they take from the founder and how costly a mistake would be. The top three are your pilot. For a longer view of who to hand things to, see the delegation framework for founders.

Book one session per process, and record it. The founder does the task or talks through a real recent example while sharing their screen. A second person, the interviewer, asks these three questions at each step:

1. What tells you it's time to do this? This captures the trigger: a customer email, a date, a threshold.
2. What do you look at, and what do you decide? This captures the decision rules, such as "if the order is over a set amount, I check credit first."
3. How do you know it's done, and what usually goes wrong? This captures the finish line and the traps.

The interviewer should interrupt with "why?" whenever the founder says "I just know." That phrase is where the valuable rules are hiding. Use a real example from last week, not a hypothetical, because founders remember specifics far better than generalities. Keep sessions under 45 minutes; beyond that, quality drops and the founder stops cooperating.

Give the recording to the person who will actually run the process, not to the founder. They write the first draft, because they'll notice the gaps that an expert can't see.

A good draft has a trigger at the top, numbered steps that each start with a verb, the decision rules stated as "if this, then that," a definition of done and a short list of common mistakes. Add screenshots only where a step is easy to get wrong. Keep each process to one page if possible. Long, narrative instructions get skipped.

Then have the founder review the draft for accuracy in ten minutes, marking only what is wrong or missing. Resist the urge to let the founder rewrite it, because that recreates the bottleneck. Store the result where people work, with an owner's name and a review date on it. Tools built for this, such as Trainual for playbooks and training, or Process Street for checklists you can run and track, can hold these documents so they don't scatter across drives.

The test is simple and humbling: hand the checklist to someone who hasn't done the task, tell them to follow it exactly and have the founder sit in the room without speaking. Every time the person hesitates, guesses or asks a question, write down what was missing. Fix those spots, then repeat with a second person.

Only after a clean run does the founder step out. Agree in advance how the new owner escalates a case the checklist doesn't cover, and to whom. Otherwise the escalations flow straight back to the founder and the bottleneck reappears.

There's a practical reason to do this before it's urgent. SHRM's 2025 benchmarking puts the median time to fill a nonexecutive position at 44 days¹, so when someone leaves, their knowledge stays missing for well over a month unless it's written down. The key person risk checklist helps you find which roles carry that exposure.

Watch for these patterns, which account for most stalled efforts:

• Asking the founder to write. Writing gets postponed indefinitely. Record and delegate instead.
• Documenting judgment as if it were procedure. If the honest answer is "it depends," write down the factors and the threshold for escalation, not a fake step-by-step.
• No owner and no review date. Documents decay within months without both. Put a reviewer's name and a date on every one.
• Storing it in five places. Choose one home, and link to it from wherever people ask questions. Process documentation vs a knowledge base explains how to split the two.
• Never retiring the founder from the process. The point is for the founder to stop doing it, so set a date and stick to it.