── ── Strategy

SOP Systemization — Turn Repetitive Work into Repeatable Process

A Standard Operating Procedure captures a recurring task as a documented, repeatable sequence so it can be handed to a person or an AI agent and produce the same result without you. For a founder-bottlenecked business this is the unlock: it converts tribal knowledge in your head into an asset that scales, delegates, and automates. SOPs are also the raw…

How it works

1. Inventory recurring tasks — list what you do repeatedly; rank by frequency × time × how much only-you-can-do-it. 2. Pick the highest-leverage repetitive task first. Gate: systemizing rare one-offs is wasted effort — target frequency × time. 3. Capture the actual steps while doing it — record/screen-capture the real workflow, including inputs, decisions, and the "done" definition. 4. Write it so a novice (or an agent) can execute — explicit steps, decision rules, examples, and a clear output standard. Gate: if it needs your judgment to run, extract the decision rule; don't leave it implicit. 5. Test by delegation — have someone/something else run it; fix every gap they hit. 6. Assign an owner and a review date — SOPs rot; schedule updates. Then delegate or automate.

When to use it

• a founder is the bottleneck on repetitive work, or wants to delegate/automate to people or AI agents
• 'everything depends on me', 'how do I document this', turning recurring tasks into repeatable processes

Worked example

SOP Systemization — Turn Repetitive Work into Repeatable Process

A Standard Operating Procedure captures a recurring task as a documented, repeatable sequence so it can be handed to a person or an AI agent and produce the same result without you. For a founder-bottlenecked business this is the unlock: it converts tribal knowledge in your head into an asset that scales, delegates, and automates. SOPs are also the raw…

Related mental models