This Is Not About Writing SOPs
Knowledge Risk Advisory vs Process Documentation
SOPs record how tasks are done. Knowledge risk advisory identifies what happens to the business when the people who hold critical knowledge leave, are unavailable, or can’t delegate, and builds the commercial case for fixing it before it costs the business more than it is currently.
An SOP is a document. It describes a process step by step so someone else can follow it. This is useful, but it answers a narrow question: “how do we do this task?” It doesn’t ask whether that task is the right thing to document first, whether the knowledge it captures is the knowledge that’s actually at risk, or what the business stands to lose if it’s never captured at all.
What I do does sits above that entirely. The work starts at the leadership level with three questions that SOP projects never ask.
Three Questions SOP Projects Never Ask
1. What is undocumented knowledge costing this business today?
The Knowledge Cost Calculator puts a number on it. Not a guess, but a defensible annual figure built from the client’s own data. Most businesses have never seen this number. When a COO discovers that undocumented knowledge is costing them £230,000 a year in friction, rework, and departure losses, the conversation changes from “we should probably document some things” to “we need to fix this.”
2. Where is the risk concentrated?
The Knowledge Map Diagnostic shows which departments hold the most exposed knowledge, which areas are single points of failure, and which would cause the most damage if lost. This is risk mapping, not process writing. It answers “what should we protect first and why.” A strategic question that determines where documentation effort gets directed, rather than letting it scatter across everything at once.
3. What does the business gain by fixing it?
The ARG Calculator models the leadership time recovered, the revenue leakage reduced, and the strategic capacity unlocked when critical knowledge is documented and leaders can finally delegate. This turns a cost-avoidance conversation into a value-creation one. The kind that gets investment approved and makes the work fundable rather than something that sits on a wish list.
The Difference In Practice
SOP writing is a task.
Knowledge risk advisory is a strategic service that protects business value, enables leadership delegation, reduces key-person dependency, and builds the evidence base for investment in operational resilience.
An SOP project starts with “let’s document our processes” and produces a set of manuals. It’s a deliverable. It sits in a shared drive. It may or may not reflect what actually matters to the business.
A knowledge risk engagement starts with “let’s understand what your business would lose if key people walked out tomorrow” and produces a prioritised, costed, department-by-department picture of where institutional knowledge is exposed, along with the financial case for addressing it. The output isn’t a stack of documents; it’s a strategic diagnosis that tells leadership exactly where to act, in what order, and what the return on that action looks like.
SOPs might be one of the remediation tools that follow. But they’re a downstream output of the advisory work, not the work itself. The advisory work is what ensures the right knowledge gets captured, in the right order, for the right business reasons, rather than spending six months documenting processes that weren’t the ones putting the business at risk.