Practice knowledge base
Process standardization (SOP)
An SOP describes recurring and critical work procedures so that people perform them consistently and can see the steps, roles, and expected result.
Documentation sections
What it is
Process standardization through SOPs means short instructions for tasks where consistency, quality, and clear expectations matter. An SOP documents the input, steps, owner, completion criteria, and exceptions. This practice helps when work relies on verbal agreements or the experience of individual people. It is less suitable for tasks where each case requires a creative solution and a stable sequence of actions cannot be described in advance.
When it helps
- The same task is done differently across teams or shifts.
- New people take a long time to get up to speed because the rules are passed on verbally and in fragments.
- Errors keep recurring in routine operations, but the team reviews them from scratch every time.
- Approvals and handoffs between roles depend on personal memory rather than a clear process.
- It is hard for the manager to verify that the result is complete because the criteria are not documented.
How to start
- 1 Choose one recurring procedure where errors or delays noticeably get in the way of work.
- 2 Assign an SOP owner who knows the process and can update the document after changes.
- 3 Describe the input, main steps, responsible people, result, and completion criteria in simple words.
- 4 Do a brief review with the people who actually carry out the procedure, and remove unnecessary steps.
- 5 Define where the SOP will be stored and agree on when the team will review it after process changes.
Expected effect
The team argues less about how to carry out routine tasks, brings new people up to speed faster, and can check the result more easily. The manager gets a shared standard of work rather than a set of personal habits from different performers.
Common pitfalls
- Describing too many details, so the SOP turns into a long document that no one uses.
- Writing the procedure without the people who perform it: on paper, the process looks logical, but important exceptions are missed in real work.
- Not assigning an owner to the document, so the instructions quickly become outdated after process changes.
- Using an SOP for non-standard tasks that require professional judgment rather than a rigid sequence of steps.
Further reading
- Standard: ISO 9001, requirements for managing documented information and the process approach.
- Book: Atul Gawande, The Checklist Manifesto.
- Book: Michael Hammer, James Champy, Reengineering the Corporation.
- Documentation: APQC Process Classification Framework, an example of process description.
FAQ
Who should own the SOP?
Usually the process owner or the team manager. This person does not have to write everything alone, but is responsible for keeping it up to date, clear, and aligned with the people who carry out the work.
Can you start without a consultant?
Yes. For the first version, it is enough to choose one recurring process, describe the real steps together with the people who perform it, and test the document on the next work task.
How can you tell whether the SOP is working?
People can find the right process without personal explanations, new people complete routine tasks faster, and repeated errors and questions about the basic steps become less frequent.
What should you do if the team resists documentation?
Start with a procedure where the pain is obvious: frequent errors, delays, or repeated questions. Show that the SOP removes unnecessary clarifications rather than adding formal work.