How small and medium businesses build Standard Operating Procedures (SOPs)
Tribal knowledge is not a feature of close-knit SME teams; it is an unmanaged risk. A practical guide to turning what is in your veterans' heads into something the business owns.
By Petar Zivkovic, Founder | Principal Consultant · Published 24 April 2026
Tribal knowledge vs institutional knowledge
In a small business, there is almost always one person who knows how the customer reorder process really works, and a different person who knows how to handle the awkward supplier, and a third who knows the password to the accounting system that nobody uses any more but cannot be deleted yet. None of this is written down. All of it lives in the heads of people who have been with the company for years.
This is tribal knowledge. It is one of the things that makes small companies feel warm and competent. It is also one of the things that makes them fragile. When the keeper of a piece of tribal knowledge takes a holiday, the business slows down. When they leave, the business loses the knowledge entirely.
Institutional knowledge is the same information, but written down in a form that the company owns. It is not better in every way; tribal knowledge is faster to update and more flexible to apply. But institutional knowledge is durable. It survives turnover, holidays, illness, and the occasional acquisition. For an SME that wants to grow, the transition from tribal to institutional knowledge is one of the most important investments the business can make.
What is a Standard Operating Procedure, exactly?
A Standard Operating Procedure is a written description of how a defined piece of work should be done. It is not a manual, not a process flow chart, and not a job description. It sits between those: more detailed than a flow chart, more focused than a manual, more action-oriented than a job description.
A good SOP answers five questions. What is this procedure for? When does it apply? Who does each step? What does each step look like in practice, with enough detail that a new hire could follow it? What does the output look like when the procedure is done correctly?
An SOP that answers those five questions is short, useful, and worth maintaining. An SOP that tries to be a comprehensive manual is long, ignored, and quietly out of date within six months. Brevity is a discipline, not a shortcut.
RACI: who is responsible for what?
RACI is a simple framework for assigning ownership in any process: who is Responsible (does the work), Accountable (owns the outcome), Consulted (provides input before the decision), Informed (told after the fact). One person should be Accountable for any given step. Multiple people can be Responsible. Consulted and Informed lists should be deliberately short.
RACI matters for SOPs because the most common operational failure in an SME is not that nobody could do the work, but that nobody was clearly accountable for ensuring it got done. Two people both thought the other one was handling it, and a week later the customer noticed.
When you write an SOP, write the RACI grid first. If you cannot agree, in writing, on who is Accountable for the procedure, the procedure does not yet exist. The SOP document is the artefact; the agreement on accountability is the actual work.
How do you write SOPs people will actually use?
There is a paradox at the heart of SOP work. The people who know enough to write a good SOP are the same people who do the work; if they spend their days writing SOPs, the work does not get done. The people who have time to write SOPs do not know enough to write good ones.
The way out is to use the doer as the source and someone else as the writer. The doer talks through the procedure for thirty minutes, ideally while doing it. The writer captures, structures, and asks the awkward questions. The doer reviews the draft. The writer revises. The result is an SOP that is grounded in real practice but written in a form that is usable by someone who is not yet an expert.
Length matters. Anything over two pages will not be read. If a procedure cannot be described in two pages, it is probably more than one procedure pretending to be one. Split it.
How do you keep SOPs from going stale?
An SOP that is six months out of date is worse than no SOP at all, because it actively misleads. The defence is a maintenance cadence built into the document itself.
Each SOP should carry a review date and an owner. The owner is the person Accountable in the RACI grid. Their job, once a quarter or once every six months depending on how fast the business changes, is to read the SOP, decide whether it still describes reality, and either confirm or revise.
The single biggest predictor of SOP rot is whether anyone ever revisits them. A simple recurring calendar reminder, owned by a real person, is more effective than any document management system.
Questions readers ask about this
- How many SOPs does a small business actually need?
- Fewer than you think. Most SMEs run their business on twenty to forty truly load-bearing procedures: how a sale closes, how an order is fulfilled, how a hire is onboarded, how an invoice is collected, how a complaint is handled. The Pareto principle applies: identifying which twenty matter is more valuable than writing down all eighty. The Organizational Healthcheck 360 is partly a tool for finding which procedures are load-bearing in your specific business.
- Should I document every process or just the critical ones?
- Just the critical ones, and start with the ones where tribal knowledge is concentrated in a single person. Those are the highest-risk procedures: if that person leaves, those processes break. Comprehensive process documentation is a multi-year project; high-risk-first documentation is achievable in a quarter.
- What software do I need to write SOPs?
- None, beyond a shared document store. Word, Google Docs, Notion, or a simple wiki all work. Software complexity tends to substitute for actual writing. The cost of an SOP is the time spent thinking and revising; the tool is incidental. Pick one and stop discussing it.
- How long does an SOP project take for an SME?
- For the load-bearing twenty to forty procedures, a focused project takes three to six months elapsed time, with the doer giving roughly two hours per procedure spread across that period. Trying to do it faster than that produces SOPs that look complete but describe how the work used to be done, not how it is done now.