Home › The Garage › Standard operating procedure
Process mapping

Standard Operating Procedures

An SOP captures the one agreed way to do a task, so it's done the same way every time, by anyone. Done well, it's how an improvement becomes permanent. Done badly, it's a document no one reads.

By LeanBean · Updated November 2026 · 6 min read
What's in this guide
  1. What an SOP is
  2. Why SOPs matter
  3. What a good SOP contains
  4. How to write one people follow
  5. SOPs and process maps
  6. Common questions
Step 1 Step 2 Step 3 the agreed flow SOP: Process name Purpose · scope · owner 1. Do this (who, how) 2. Then this — if X, then Y Done when: <clear outcome>
The map agrees the flow; the SOP writes down how each step is actually done, by whom.

What an SOP is

A standard operating procedure (SOP) is a documented, step-by-step instruction for carrying out a routine task the one agreed way. Its job is consistency: the same task done the same way, to the same standard, regardless of who does it or whether the usual person is away. In Lean terms, an SOP is standard work — and standard work is the baseline from which all improvement is measured. You can't improve a process reliably if everyone does it differently.

Why SOPs matter

What a good SOP contains

How to write one people follow

An SOP no one reads is waste, not control
The failure mode of SOPs is length. A 40-page document that's technically complete but never opened controls nothing. Write for the person doing the job under time pressure: short, scannable, one action per step, plain language, and a decision made explicit rather than buried in prose. If it can't be followed at the desk, it won't be.
  1. Map the process first — agree the flow and the steps before you write the words (see below).
  2. Capture the real way, not the ideal. Document how the work is actually done well, or the SOP will be ignored as fiction.
  3. Write each step as one action — verb + outcome, with the owner. No multi-action steps.
  4. Make exceptions explicit — the branches are where consistency usually breaks.
  5. Test it with someone who doesn't know the task. If they can follow it, it works; if they stall, fix that step.
  6. Give it an owner and a review date. An unowned SOP rots.

SOPs and process maps

A process map and an SOP are two views of the same standard work. The map shows the flow — the steps, lanes, handoffs and decisions — at a glance; the SOP writes down how each step is actually performed, by whom. The map is the 60-second executive view; the SOP is the operator's manual. Build the map first to agree the flow, then write the SOP against it — the map keeps the SOP honest and complete, and the SOP gives the map operational teeth.

Describe a process. Get the whole analysis.

LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.

Build your first map free →

Keep learning in the Garage

Short, practical lessons on Lean, process mapping and AI-ready operations — the same thinking that powers LeanBean, in two minutes or less. Follow along and build the habit.

Common questions

What is a standard operating procedure (SOP)?

A documented, step-by-step instruction for carrying out a routine task the one agreed way, so it's done consistently regardless of who performs it. In Lean terms an SOP is 'standard work' — the baseline from which all improvement is measured.

What should an SOP contain?

Purpose and scope, an accountable owner, the steps in order (one action each, verb + outcome, with who does each), the decisions and exceptions handled explicitly, a clear definition of done, and a version and date so people know it's current.

How do you write an SOP people actually follow?

Keep it short and scannable — write for the person doing the job under time pressure, one action per step, plain language, exceptions made explicit. Capture the real way the work is done well, not an ideal, and test it with someone who doesn't know the task.

How do SOPs relate to process maps?

They're two views of the same standard work: the map shows the flow at a glance (the executive view), the SOP writes down how each step is performed and by whom (the operator's manual). Map first to agree the flow, then write the SOP against it.

Related guides: How to map a business process · Kaizen · Process to AI readiness