Day 19: Create a Personal SOP

The Concept

A Standard Operating Procedure is a document that captures how to do something reliably, so you do not have to reconstruct it from memory each time you face that task. The phrase sounds formal — the kind of thing that belongs in a large organisation's compliance folder — but the underlying idea is simple and useful at any scale. If you do something repeatedly, and doing it inconsistently costs you time or quality, writing down a clear version of how to do it well is one of the most practical things you can do. AI can create an SOP from your description of a task, or help you reverse-engineer one from what you already do, even if what you currently do is not fully consistent or consciously designed.

Most people have processes they run repeatedly — preparing a monthly report, onboarding a new client, handling a particular type of complaint, running a weekly review — but they run them slightly differently each time. They rely on memory, improvise when memory fails, and cannot easily hand the task to someone else or improve it systematically because it has never been articulated. The mental overhead of reconstructing the process each time is invisible when you are inside it but significant in aggregate. A written SOP eliminates that overhead for every future run of the same task.

What an SOP actually is and why it matters

A useful SOP is not a policy document or a mission statement. It is a specific, sequential description of how to complete a task — specific enough that someone doing it for the first time could follow the steps without asking questions, and complete enough that the output would meet the standard you care about. The sections that matter are simple: what triggers the process and what it produces, what you need before you start, the numbered steps in order, a way to verify the output is correct, and the common failure modes to watch for.

The value of an SOP is not that it tells you something you did not know. It is that it frees you from having to hold the process in working memory each time you run it. A task you have documented is a task you can do at lower cognitive cost, hand off without long explanations, and improve deliberately rather than accidentally. These three benefits compound over time in ways that are easy to underestimate when you are looking at a single process in isolation.

The three types of process AI captures best

AI is particularly well-suited to creating SOPs for three categories of task. The first is recurring individual tasks — things you do on a weekly or monthly cadence that are mechanical enough to follow a consistent structure but complex enough that memory alone is unreliable. Weekly reviews, monthly reporting routines, and regular admin tasks all fit here. The second is delegation tasks — processes you want to hand to someone else, whether a colleague, a family member, or a future version of yourself returning to something after a long gap. A good SOP makes delegation possible without a lengthy briefing. The third is quality-critical tasks — situations where doing something consistently matters because the output affects other people or carries real consequences. The SOP acts as a checklist that prevents the kind of errors that happen when you are tired, distracted, or rushing.

What makes an SOP actually usable

An SOP that sits in a folder you never open is not useful. The two factors that determine whether an SOP gets used are where it lives and whether you trust it. It needs to live somewhere you would naturally look when starting the task — not in a general archive but at the point of use, whether that is a pinned note, a bookmarked document, or a dedicated folder that opens at the start of your working day. Trust comes from the SOP having been tested and updated. An SOP that describes your actual process, including the adjustments you have made from experience, is one you will follow. One that describes an idealised version of the process that nobody actually runs will be ignored.

The most reliable way to build trust in an SOP is to run it once, note what you did differently or what was missing, and update it immediately. That first update is the point at which a generated document becomes a living tool. AI makes this iteration fast — paste the current SOP back in with your notes, ask for a revised version, and save the update. A process document that has been revised twice after real use is more valuable than a perfect first draft that was never touched again.