A standard operating procedure (SOP) is a documented, repeatable sequence of steps for a defined task or situation. It reduces variation, captures knowledge, and makes outcomes more predictable. When the same work is done the same way each time, quality and speed improve — and new people can be trained faster. The discipline is: document the best known method, follow it until you have a reason to change it, then update the document. SOPs turn tacit knowledge into explicit process so that the system doesn't depend on one person's memory or judgment for routine work.
SOPs have a cost: they can rigidify behaviour and slow adaptation. When the situation doesn't match the procedure, following the SOP can be wrong. The balance is between consistency (follow the procedure) and judgment (deviate when the situation warrants). High-reliability organisations often combine SOPs with clear escalation: follow the procedure unless X; if X, escalate or use a different protocol. The strategic question is: for which tasks is consistency worth more than flexibility, and where do we need judgment over procedure?
SOPs also need maintenance. Outdated procedures are worse than none — they give false confidence and block improvement. The best SOPs are living documents: used, reviewed, and updated when the work or the environment changes. When no one reads or updates the SOP, it's organisational debt.
Section 2
How to See It
SOPs show up wherever there is a written sequence for a recurring task. Look for: runbooks, playbooks, checklists, and "how we do X" docs. When someone says "we have a process for that" or "check the runbook," an SOP is in play. The diagnostic: is the procedure actually followed and updated?
Business
You're seeing Standard Operating Procedure when onboarding follows a checklist: set up accounts, assign buddy, schedule intro meetings, first-week goals. The procedure reduces variation and ensures nothing is missed. The same applies to sales: discovery script, demo flow, close steps. When the procedure is good, outcomes are more consistent; when it's stale, it blocks adaptation.
Technology
You're seeing Standard Operating Procedure when incident response follows a runbook: acknowledge, assess, communicate, fix, post-mortem. The procedure ensures consistent handling and capture of learning. Deploy and release procedures are SOPs: branch, test, stage, production, verify. The value is repeatability and audit trail; the risk is procedure that doesn't match the current system.
Investing
You're seeing Standard Operating Procedure when a fund has a defined diligence process: memo template, checklist, committee, approval thresholds. The procedure reduces omission and bias. The same for compliance: KYC, AML, and reporting steps. SOPs here protect against error and regulatory failure; they can also slow deals when the procedure doesn't fit the opportunity.
Markets
You're seeing Standard Operating Procedure when a trading desk has procedures for order entry, risk limits, and exception handling. The procedure ensures compliance and consistent risk management. When markets move fast, the tension is procedure versus discretion — follow the SOP or deviate. The best procedures specify when to escalate rather than follow.
Section 3
How to Use It
Decision filter
"Document procedures for recurring, high-stakes, or training-heavy work. Follow them until you have evidence to change. Build in review and update so procedures don't go stale. For edge cases, define escalation and exception paths — don't let the SOP block necessary deviation."
As a founder
Create SOPs for anything that repeats and where consistency matters: onboarding, support escalation, release process, key sales steps. Capture the best current method; make it easy to find and follow. The mistake: no procedure, so every time is ad hoc and quality varies. The second mistake: procedure that no one updates, so the doc is wrong and people work around it. Assign ownership and review cadence.
As an investor
Assess whether critical operations have procedures and whether they're used. Companies with no SOPs for key processes (e.g. compliance, incident response) carry operational and regulatory risk. Companies with stale or ignored procedures may have a false sense of control. Look for living docs and a culture of "follow or update."
As a decision-maker
Use SOPs when the task is recurring and the cost of variation is high. Write the procedure, train to it, and measure adherence and outcomes. When outcomes slip or the situation changes, update the procedure. For one-off or highly variable work, procedure may be less useful than judgment and principles.
Common misapplication: Following the SOP when the situation clearly doesn't fit. Procedures are for the common case; edge cases need escalation or exception. Build "when in doubt, escalate" into the design.
Second misapplication: Treating the SOP as permanent. Procedures decay. Schedule review; encourage updates when people find better ways. An outdated SOP is worse than no SOP.
Jiro's sushi preparation is a form of SOP: exact sequence, temperature, timing, and presentation for each piece. The procedure has been refined over decades; following it produces consistent quality. The SOP is the standard; deviation is only when the ingredient or situation requires it. The procedure is living — he still refines — but the discipline is follow or explicitly deviate.
Danny MeyerFounder, Union Square Hospitality Group
Meyer built SOPs for hospitality: how to greet, how to handle complaints, how to close. The procedures ensure consistent experience across locations and staff. The culture is "enlightened hospitality" — the SOPs encode how to deliver it so that every team member can. Procedures scale the experience; they're updated as the company learns.
Section 6
Visual Explanation
SOP: document the steps, follow until you have reason to change, then update. Consistency and knowledge capture; balance with escalation for edge cases.
Section 7
Connected Models
SOPs connect to repeatability, quality control, and checklists. The models below either depend on them (Quality Control), extend them (Checklists), or warn about rigidity (Organisational Debt).
Repeatable systems produce consistent output. SOPs are the mechanism: define the steps, follow them. The procedure is the repeatable pattern; the system scales when the procedure is documented and trained.
Reinforces
[Quality](/mental-models/quality) Control
Quality control measures output against a standard. The standard is often embodied in an SOP — "good" is what the procedure produces when followed. Control checks conformance to the procedure and the outcome.
Reinforces
Pre-Mortem Analysis
Pre-mortem assumes failure and asks why. SOPs reduce failure by making steps explicit; when failure still occurs, pre-mortem (and post-mortem) feed back into updating the procedure. Both rely on explicit steps and learning from deviation.
Reinforces
[Modularity](/mental-models/modularity)
Modularity is clear boundaries between parts. SOPs can define the interface between modules — how handoffs and interactions work. Procedures make modular processes predictable.
Reinforces
Section 8
One Key Quote
"Checklists seem to provide protection against such failures. They remind us of the minimum necessary steps and make them explicit. They catch mental flaws inherent in all of us."
— Atul Gawande, The Checklist Manifesto
Procedures and checklists don't replace judgment; they catch omission and drift. Even experts benefit from making the critical steps explicit and following them.
Section 9
Analyst's Take
Faster Than Normal — Editorial View
Document what you want to repeat. For any recurring, high-stakes task, write the steps. Make them findable and followable. The act of writing forces clarity; the doc enables training and consistency. Don't leave critical process only in people's heads.
Follow or update. The worst state is a procedure that no one follows — it gives false confidence and blocks improvement. Either follow the SOP or change it. Assign an owner and a review cadence so the procedure stays current.
Build in escalation. Not every situation fits the procedure. Define when to escalate or deviate so that the SOP doesn't force wrong behaviour in edge cases. "When in doubt, follow the procedure" is good; "when the procedure clearly doesn't apply, escalate" is essential.
Section 10
Summary
A standard operating procedure is a documented, repeatable sequence for a defined task. It reduces variation, captures knowledge, and makes outcomes more predictable. Document the best known method; follow it until you have reason to change; then update. Balance consistency with escalation for edge cases. Keep procedures living — review and update so they don't become organisational debt.
Hospitality as procedure and culture. How Meyer built repeatable experience through standards and training.
[Feedback Loops](/mental-models/feedback-loops)
SOPs need feedback: when outcomes slip or the environment changes, the procedure should be updated. Feedback loops close the circle: follow → measure → update procedure.
Tension
Organisational Debt
Organisational debt includes outdated or ignored procedures. When the SOP is wrong and everyone works around it, the "real" process is tacit again and the doc is debt. The fix: review and update, or remove the SOP if it's not the real process.
