Nobody wakes up thinking their team has an SOP problem. The realisation tends to creep up on you. A senior colleague hands in their notice and you start noticing how many small things only they knew. A new starter misses something obvious in their third week and you discover nobody ever wrote it down. An auditor asks one question and you spend the evening searching Slack.
Here are ten signs that your team is quietly paying a tax on undocumented process. Each is concrete. None requires a consultant to diagnose. If three of them ring true, the rest of this article is written for you.
1. The same questions get asked, again and again
Listen to the chat channel for a week. Notice the questions. “How do we handle returns for item type X?” “What's the correct temperature for the walk-in on a Saturday?” “Who needs to approve this before it goes out?”
If the same questions surface every few weeks, you have a documentation problem, not a curiosity problem. The answer exists; it just does not live somewhere people can find it. Every repeat question is time someone senior spent answering, plus time the asker spent waiting.
2. New starters take four or more weeks to ramp up
There is no universal right number for ramp time, but for most operational roles it should be measured in a small number of weeks, not months. If your new starters are still asking basic procedural questions at week four, the cause is almost always that the procedures exist in heads rather than in documents.
The tell is when new starters say, two months in, “I only really got it when I watched Priya do it.” That is feedback about your documentation, not about your new starter's capability.
3. Quality varies by shift or by person
The same task done on Monday morning by one team looks different from the same task done on Thursday evening by another. Output quality swings. Customers notice.
Variation of this kind is almost always procedural. When the procedure is documented and followed, Monday and Thursday look the same. When the procedure lives in each person's interpretation of what was shown to them once, variation is inevitable. “This is how we do it on our shift” is a red flag disguised as team pride.
4. Key knowledge lives in two or three heads
List the processes your business depends on. Beside each, name the people who know how to run them. If any process has only one or two names against it, that process is a business continuity risk.
The risk is not hypothetical. Those people take annual leave. They get sick. They have babies. They get poached. When it happens - and it does - the process either slows dramatically or breaks. The organisations that handle this well are the ones that noticed before they had to.
5. Compliance is stressful every time an auditor calls
An audit should not cause panic. If every inspection, insurer questionnaire, or customer security review triggers a scramble to find records, the problem is usually not the audit - it is the absence of a standing system that produces the records as a by-product of the work.
A team with working SOPs answers “can you show me X?” in a few minutes. A team without them answers “can we come back to you next week?” That gap is the SOP problem showing through.
6. Training is ad-hoc and delivered differently every time
Ask three managers how they onboard a new starter. If you get three different answers, you have an ad-hoc training system. If one of them says “I tend to just show them as we go,” the answer is really “we have no training system.”
Ad-hoc training is not automatically bad. What makes it bad is the inability to verify what anyone learned and the predictable gaps that show up when the person who usually does the training is not available. Consistent training needs source material, and source material is SOPs.
7. Procedures exist, but nobody can find them
This is the worst version, because you have done much of the work and reaped none of the benefit. Someone wrote the SOPs. They are in a folder. Nobody looks at them.
The common reasons: the folder is not where people work (documents live in Drive, the team works in chat), the search is poor, the documents are too long to scan on a phone, or the documents have not been updated since 2022 and everyone has quietly decided they are unreliable. If your team's first response to a procedural question is “ask Sarah” rather than “check the SOP,” that is a verdict.
8. Nobody is quite sure which version is current
A customer onboarding SOP exists. There is also a “Customer Onboarding - Updated 2024” document. And a “Customer onboarding v3 FINAL” in a different folder. Which is the real one?
Version ambiguity is slow corrosion. Staff follow different versions, some of which are out of date. Auditors ask which version was in force on a given date and you cannot answer. The fix is not a naming convention; it is a single source of truth for each procedure, with a visible version and review date, and an unambiguous path to retire old copies.
9. Recent incidents trace to “we never told them that”
Look at the last few quality incidents, customer complaints, or safety near-misses. For each, ask whether the root cause includes the phrase “we assumed they knew” or “we never actually told them that.”
When incidents trace back to tacit knowledge that was never made explicit, the SOP problem is no longer hypothetical. It has a cost. Each incident is evidence that something important lives in the oral tradition when it should live in writing.
10. You cannot answer “was this procedure followed?” in five minutes
Pick any procedure your team runs daily. Pick a specific date last month. Try to answer, with evidence: was this procedure followed on that date, by whom, and correctly?
If the answer requires a phone call to a manager, a rummage through shared drives, or a shrug - you have not just an SOP problem but an evidence problem. The two are usually linked. Teams that write usable SOPs also capture evidence of execution, because the SOP and the evidence belong to the same workflow.
If three of these feel familiar
If three or more of the above ring true, the tribal-knowledge model of running a team has outgrown its usefulness. You do not need a dramatic intervention. You need a small, deliberate move from head-based to document-based, starting in one place and expanding.
A plan that usually works:
- Pick the three processes that matter most. Not the easiest. The ones where variation costs you the most - customer onboarding, a core operational task, a compliance-sensitive procedure. Document those first.
- Write them with a specific reader in mind. The person on shift, on a phone, trying to do the task. Imperative verbs, sequenced steps, evidence points on the steps that matter.
- Pilot them with two people who did not write them. Watch them follow the SOP. Fix what does not work. Publish the fixed version.
- Make them the source of training. The SOP is the thing new starters learn from, not a separate onboarding deck that duplicates and diverges.
- Capture evidence of execution. Completion logs, photo proof on the steps that matter. Start with the three processes. Expand to more as the habit takes.
- Set a version and review date. Every document has a named owner and a twelve-month review at most. Out-of-date documents get the same trust as no documents.
This is not a six-month transformation project. Three processes, properly documented with execution evidence, can be in place in a few weeks. The compounding benefit - fewer repeat questions, faster onboarding, lower variation, calmer audits - starts almost immediately.
If this diagnosis lands, the next read is on turning undocumented knowledge into real SOPs. How to get knowledge out of people's heads and into a format your team can use.