Every business has a version of the same conversation. Someone asks how a particular thing gets done — how a custom order gets priced, how the month-end close actually works, how that one customer's invoicing exception is handled — and the answer is a name. "Ask Dana." Nobody thinks of that as risk. It feels like competence.
It is risk. When a process lives in one person's head, your business has a hard ceiling: it can only grow as fast as that person can answer questions. And it has a soft floor: whatever happens when they're on vacation, out sick, or gone.
The fix isn't a documentation project. Most documentation projects produce a folder nobody opens. The fix starts with knowing exactly where the dependencies are and how much each one actually costs you.
Start With Handoffs, Not Job Titles
Org charts hide this problem. They show who reports to whom, not who is the only person who knows something. The dependency lives in the seams — the moment work passes from one person, team, or system to another.
So don't audit roles. Audit handoffs. Pick your core value chain — quote to cash, or lead to delivery, whatever it's called in your business — and walk it end to end asking one question at each step: if the person who normally does this were unavailable today, what would happen?
The answers sort themselves into three piles quickly. Someone else could do it. Someone else could figure it out with effort. Or the work stops.
Run the Two-Hour Version
You don't need a consulting engagement to get the first pass done. Get your ops lead and two or three people who actually touch the work into a room with a whiteboard, and go step by step through one process. For each step, capture:
- Who does it, and who is the only person who can do it
- What system or spreadsheet the work lives in
- What decision or judgment call the step requires
- How often it happens, and what breaks downstream if it's late or wrong
- Whether the knowledge exists anywhere outside someone's head
That last column is the one that matters. You'll find steps where the "documentation" is a saved email thread, a naming convention nobody wrote down, or a spreadsheet with formulas that one person built and nobody else understands.
Rank by Damage, Not by Discomfort
You'll surface more dependencies than you can fix this quarter. Rank them on two axes: how often the step runs, and how bad it is when it goes wrong.
A daily step that only one person can do is an operational bottleneck — it caps throughput every single day. A quarterly step that only one person can do is a landmine; it's fine until the quarter they're out, and then it's a scramble. Both matter. They get different fixes.
What you should not do is rank by how nervous the dependency makes you feel. Founders tend to over-index on the dramatic scenarios and ignore the small daily approvals that quietly slow everything down.
Fix in This Order
Writing an SOP is the third-best answer, not the first. Work down the list:
Eliminate the step. A surprising number of manual steps exist because a system was configured wrong years ago, or because a report has to be assembled by hand from three places. If the step shouldn't exist, deleting it beats documenting it.
Put it in the system. If the knowledge is a rule — this discount needs approval, this order type routes to that workflow, this customer gets these terms — encode it in your ERP or workflow tool. Rules in software don't forget, don't go on vacation, and don't need to be retrained. This is where a properly configured Odoo instance or a unified Business Hub earns its keep: the process becomes the path of least resistance instead of a document about the path.
Then document. What's left is genuine judgment — the exceptions, the escalation calls, the context. That's what SOPs are for. Keep them short and keep them where the work happens, not in a wiki nobody visits.
Train a backup last. Cross-training is real, but it's expensive and it decays. Use it for the judgment calls you couldn't systematize, not as a substitute for fixing the process.
Let AI Transcribe, Not Decide
This is where modern tooling genuinely helps. Recording a walkthrough and having AI turn it into a first-draft procedure removes the biggest reason SOPs never get written: nobody wants to type it. Have the person do the work while narrating, then edit the draft.
What AI shouldn't do is decide what the process should be. That's an operator judgment call — one made by someone who understands the tradeoffs, the customers, and the systems underneath. Use the tool to remove the drudgery, not the thinking.
What You're Actually Buying
A business where the work doesn't depend on specific people is a business that can hire without a six-month ramp, take on a bigger customer without panic, and survive a departure. It's also the difference between a company an acquirer will pay for and one that's really just a job with employees.
If your audit turns up more system problems than documentation problems — and it usually does — that's a good sign. Those are fixable. We help operators turn tribal knowledge into working systems, from ERP configuration to the integrations that eliminate the manual steps entirely. If you'd like a second set of eyes on where your dependencies actually sit, reach out and let's walk your process together.