What Is SOP Debt and How Do You Know If You Have It?
SOP debt works the same way as technical debt in software engineering. Every time a revenue-critical process gets established without being documented, you are borrowing against the future. The day will come when those people are not in the same role... and on that day, the debt comes due.
The Five Signals of Dangerous SOP Debt
- Signal 1: Things slow down or break when a key person is unavailable. If the business operates differently when a specific person is on vacation, that person is the SOP. The test: pick the three people whose absence would most affect revenue operations. Which processes would degrade meaningfully if they took an unplanned two-week leave?
- Signal 2: New hires shadow someone for weeks before executing independently. If the standard onboarding approach for a revenue-facing role is 'follow [person] around and watch what they do,' the process is not documented.
- Signal 3: The same operational questions get asked over and over. Track recurring questions for one month. Every question that comes up more than twice is a documentation gap.
- Signal 4: A departure in the last year created a knowledge gap, not just a capacity gap. If a departure left a knowledge gap that took weeks or months to close, you have experienced the cost of SOP debt firsthand.
- Signal 5: You could not write down how a critical process works right now. For your three highest-priority revenue processes, could you write down the exact steps in the next 30 minutes? If not, those processes are undocumented in practice.
The Compounding Cost
SOP debt does not stay the same size. It grows. Each new hire who learns the undocumented process informally becomes another potential single point of failure. Each time the process changes without documentation, the gap between what is written and what is practiced grows larger. The companies that fix SOP debt early spend significantly less time on documentation overall than companies that wait.