A new volunteer arrives to open a community workspace and discovers that the instructions exist only in someone's head. A standard operating procedure turns a recurring activity into an accessible sequence: what needs to happen, in what order, with which responsibilities and relevant precautions.
A usable procedure specifies its scope, instructions, approval, and revision history. A procedure is more than a helpful personal note because the organization treats it as an agreed way of doing the work.
A living description of work
The workspace could document opening, equipment checks, and closing, with enough detail for someone already trained in the relevant tasks. That reduces repeated explanation and makes handovers less dependent on the availability of a particular person.
The document can also preserve a bad process remarkably well. If equipment changes but the instructions do not, diligent compliance may create problems. People need a way to identify an exception, report a misleading step, and have the procedure revised by someone with authority.
Not every activity benefits from detailed standardization. Creative or unusual work may require principles and judgment rather than a fixed sequence. An operating procedure is strongest where variation is unnecessary or costly, leaving attention available for the parts of the situation that genuinely need thought.
Real cases
- NUMMI: changing the work changed the culture — Can people learn a new way of organizing without replacing the workforce?
- Buurtzorg: small nursing teams with a shared backbone — What replaces middle management when a professional service scales?
- GitLab: written context with one accountable decision-maker — How can a distributed team combine wide input with clear decisions?