The SOP Debt Problem: What Happens When Processes Live in People's Heads

The Five Signals of Dangerous SOP Debt

Signal 1: Things slow down or break when a key person is unavailable.

This is the clearest diagnostic. Pick the three people whose absence would most affect revenue operations. For each one: which processes would degrade meaningfully if they took an unplanned two-week leave? Every process on that list is a key person dependency and a documentation gap.

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. The time experienced team members spend on informal knowledge transfer is direct overhead created by SOP debt.

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. Experienced team members answer these questions because the answer is not written down anywhere.

Signal 4: A departure in the last year created a knowledge gap, not just a capacity gap.

If a departure left a gap that took weeks or months to close, if the team was asking 'how did [person] do this?' rather than just 'who is doing this now?' 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 SOP Debt Paydown Strategy

The goal is not to document everything at once, that approach almost always fails because the scope is too large and the team gets overwhelmed. The goal is to systematically reduce the highest-risk debt while building the habits that prevent new debt from accumulating.

Step 1: Identify your highest-risk processes.

For each undocumented revenue process, score it on two dimensions: what is the revenue impact if this process breaks? How key-person dependent is it? The processes that score high on both dimensions are your priority one SOPs. Which revenue processes should get SOPs first gives you a ready-made prioritization model based on revenue impact and key person dependency.

Step 2: Build the first three SOPs properly.

Choose the three highest-priority processes. Build each one to the transferability standard, numbered steps, explicit decision criteria, clear definition of done. Run the transferability test before calling them done. How to write a revenue SOP your team will actually use covers the format, decision criteria, and transferability test in full detail.

Step 3: Build the prevention habit.

Every time a new revenue process gets established, add 'write the SOP' to the definition of done for that process. Every time a process changes, add 'update the SOP' to the implementation steps. Preventing new debt is as important as paying down existing debt. If you want ThriveSide to run a full SOP debt assessment across your revenue operations, book a RevOps Strategy Session.

Why Building SOPs Early Is Cheaper Than Building Them Later

The counterintuitive truth about SOP debt: the companies that build documentation early spend significantly less time on documentation overall than companies that wait.

Here is why: building an SOP for a process that is currently running smoothly, where the person who owns it is available, the process is fresh in their mind, and there is no crisis pressure, takes a fraction of the time it takes to reconstruct the same process after a departure, after an inconsistency problem has emerged, or under the pressure of rapid scaling.

Reconstruction is the expensive version of documentation. It requires interviewing multiple people with partial memories, comparing inconsistent execution patterns, and filling in the gaps with best guesses. Building it proactively is straightforward: watch the process, write the steps, test the document.

The other compounding factor: SOPs built on a solid foundation are easier to maintain. SOPs built under crisis conditions tend to have gaps, because there was not time to run the transferability test, not time to get all the decision criteria right, not time to build the review cadence. Those gaps create ongoing maintenance overhead.

Every process that lives in someone's head is a liability. The question is not whether it will eventually cost you, it is whether you will address it before or after it becomes a crisis.

Start paying down your SOP debt this week:

1. Run the five-signal audit. Score each signal 1-5 for severity in your company. Total your score. This gives you an honest picture of your current SOP debt level.
2. Identify your top three undocumented processes. Score by revenue impact and key person dependency. Highest combined score goes first.
3. Block two hours for the first SOP. Interview the process owner. Write the numbered steps. Add decision criteria. Add definition of done.
4. Run the transferability test. Give it to someone uninvolved. Fix the gaps.
5. Build the prevention habit. For every new process established this quarter, 'write the SOP' is part of the definition of done.

Related: What Are SOPs | How to Write a Revenue SOP