Turning a Task Into a Documented System

Imagine your best employee doesn't come to work tomorrow. Could someone else do their job, the same way, to the same standard? If the answer is no, the business has a person, not a system.

A documented system lets anyone with the right training do the same job the same way, whether or not that one person is there that day. That makes the business more reliable, easier to grow, and far less dependent on any single person.

The step-by-step document that describes how to do a job is called a Standard Operating Procedure, or SOP for short. This chapter shows you how to build one properly, and how to turn it into a complete system.

A system isn't something you write in one sitting. You build it step by step. These seven steps turn a task that lives in one person's head into a system that anyone can follow.

Step 1: Choose the Right Task

Don't try to document everything at once. Start with the one task that would cause the biggest problem if it were done incorrectly.

Good first choices are:

• A task that recently went wrong.
• A task only one employee knows how to do.
• A task involving cash or valuable items.
• A task customers complain about.

These usually give the biggest improvement for the least effort, because they're the ones where a single mistake, or a single person being unavailable, causes the most damage.

Step 2: Watch Someone Do the Job

Watch the person doing the job in person. Don't sit in an office trying to write the procedure from memory.

People often leave out small but important details because they do them automatically, without even noticing. For example, someone making tea may always warm the cup first without thinking about it. If they forget to mention that step out loud, the written procedure won't match what actually happens, and the tea will come out wrong every time someone follows the document instead of the habit.

Always document the real process, not the remembered one. What people say they do and what they actually do are often different.

Step 3: Write the Procedure

Now write down what you watched, in the exact order it happened. This numbered document is what's called a Standard Operating Procedure, or SOP. Keep it simple:

• Number every step.
• Give one instruction per step.
• Start each step with an action word.

For example, write "Unplug the machine", not "The machine should be unplugged." The first version tells someone exactly what to do right now; the second just describes a state, and leaves the reader to work out the action themselves.

If there's one step people often get wrong, make it stand out. For example: "Add ONE drop of oil. More than one drop attracts lint." A photo or a short video is often clearer than a paragraph of text, especially for a physical, hands-on skill.

Step 4: Complete the System

The steps you just wrote explain how to do the task. On their own, that's only a procedure, not a full system.

A complete system, per Chapter 2, answers six questions in total. You've already answered one of them (how it's done, the steps themselves). You still need to answer the other five:

• Why does this task exist?
• Who is responsible for it?
• When should it be done?
• How is success measured? How do you know it was done correctly?
• What happens if it fails? What should happen if something goes wrong?

Once all six questions are answered, including the steps you already wrote, you have a complete system, not just a procedure. Use the System Design Worksheet, a simple fill-in-the-blank page for exactly these six questions, to capture it all in one place.

Step 5: Test It with Someone New

Now give the written procedure to someone who has never done the task before. Don't explain anything out loud first. Simply hand it over and watch them follow it.

• Every time they ask a question, your procedure is missing information.
• Every time they hesitate, something in it isn't clear.
• Every time they invent their own method, you forgot to write down part of the real process.

The goal is for them to complete the task correctly with no help from you at all. That's the real test of whether the document works, not whether you personally can follow your own writing.

Step 6: Improve It and Test Again

Update the procedure as soon as the test is finished, while the problems are still fresh in your mind. Then repeat the test with the corrected version. Keep improving the document until a new person can complete the task confidently, without asking questions.

Step 7: Store It Where the Work Happens

A procedure can't help anyone if they can't find it when they need it. Keep it exactly where the task is performed: attach a laminated instruction card to the machine, keep a checklist at the counter, or place a call script beside the telephone.

Finally, write a review date on the document. As the business changes, the procedure needs to change with it. A good system is a living document that gets checked and revised, not something written once and forgotten.

Let's put everything you've just learned together, in one real example.

A Standard Operating Procedure, or SOP, is a written set of instructions that explains exactly how to perform a task, step by step, so that anyone can do it the same way every time.

Imagine you're writing an SOP for taking a customer's measurements in a tailoring business. This is one of the most important procedures at MANIAC MINDZ, because a single wrong measurement can waste fabric, waste hours of work, and leave a customer unhappy with the finished garment.

A complete system answers all six questions, not just how to do the job. Here's what that looks like for this one:

Why This Is a Complete System

Notice that this document does much more than list a few steps:

• It tells everyone when the process begins, so staff know exactly when to use it.
• It tells everyone who is responsible, so there's no confusion about ownership.
• It gives the steps in the same order every time, which makes a missed measurement easy to spot.
• It explains how to check that the measurements were recorded correctly, by repeating every number aloud.
• It includes a failure plan, so everyone knows exactly what to do if a mistake is discovered.
• And it includes a review date, reminding the business to keep the procedure up to date as the way it works changes over time.

Build one complete system this week, start to finish:

1. Choose a task using Step 1's rule (a task that would cause real problems if done incorrectly).
2. Watch the real task being done once. Note the small habits people use without thinking about them.
3. Write numbered steps; make the one big problem point stand out in bold.
4. Complete the System Design Worksheet around it, answering the other five questions.
5. Run the Stranger Test on someone new. Count how many questions they ask, that number is your gap score.
6. Fix the document the same day, retest, then store it exactly where the work happens with a review date written on it.
7. Aim for a gap score of zero on the second test.