The folder exists. It changed nothing.
You did the thing. You wrote them, or you paid someone to. There's a folder, or a Notion space, and it's genuinely not bad — steps, screenshots, the works. And people still ask you. The same people, the same questions, as though the folder doesn't exist. Which, functionally, it doesn't.
So you send the link, slightly pointedly. They read it. Next week they ask again. And you land somewhere between irritation and defeat, wondering whether the problem is that nobody reads anything anymore. That's not what's happening. Something much more rational is, and once you see it, the fix is obvious and mostly not about the documents.
You are a better SOP than your SOP
Put yourself in the seat of the person doing the work. They need to know how to handle something. They have two options. Option one: remember the doc exists, find it, read it, and hope it's current — and if it's wrong, they've just done the work wrong and it's on them. Option two: message you. Ninety-second turnaround, guaranteed current, and if the answer's wrong it's your answer.
Option two wins on every single dimension. Faster. More accurate. Lower personal risk. And it comes with something the doc structurally cannot provide: the ability to describe the specific weird thing about this situation and get an answer about that, rather than an answer about the general case. Nobody is being lazy. They're choosing correctly between two options, and you're one of the options.
So the SOP loses because it's beside the work rather than in it. It's a thing that has to be remembered. You're a thing that can be asked. Anything requiring memory competes with something requiring none, and loses, every time — which is the same reason the dashboard nobody opens is gathering dust one floor down in your operation.
Then there's decay, which turns losing into being actively wrong. It was written once, eighteen months ago, and it describes a process that has changed twice since. So people ask you instead, which is faster and confirms the doc was pointless. And once a team has followed a stale SOP once and been corrected for it, reading becomes the risky option. Now the doc isn't just losing. It's a liability, and ignoring it is prudent.
What the ignored folder costs
You paid for it twice: once to write it, and then continuously to be the thing it was supposed to replace. That's not a wash — it's worse than never having written it, because the folder tells you documentation is handled. You look at it and conclude the problem must be your team. So the real fix never gets funded, and the misdiagnosis is the expensive part.
It also caps the operation at your throughput anyway. Every question that routes to you is a decision made at your speed, and the whole point of writing the SOP was to stop that. So delivery still holds together because you personally remember things, which is not a system so much as a very expensive habit.
And it costs you the next attempt. Everyone in your business now has evidence that documentation here is theater. The next time you announce a documentation effort, people will nod and wait it out. Correctly.
Put the SOP in the path, and let it decay out loud
Three changes, none of which is writing better documents. First, put it in the path of the work rather than beside it. The doc gets linked from the task, not stored in a folder — the checklist item is the SOP, the Slack workflow that fires when the handoff happens carries the link, the step in the build is where the reasoning is. The correct test: could someone do this job without ever deciding to go look something up? If not, it's still competing with you.
Second, remove yourself as the competing option — gently and consistently. When someone asks, answer in the doc and send the link. Not as a reprimand, as a habit. Now their ask improves the asset instead of subsidizing its absence, and the doc becomes current because being asked is what updates it. That's the forcing function it never had.
Third, give it an owner and a trigger. Whoever hits the edge case updates it — that's the job, not an extra. And the trigger for review isn't a calendar reminder nobody honors; it's the fact that someone asked, which is the operation telling you the doc is now wrong. That signal is arriving in your inbox already, several times a week. It's free. You've just been consuming it as an interruption instead of reading it as telemetry.
Then document the judgment, not just the steps. The knowledge worth transferring is why we call in week one instead of emailing, what predicts a rocky account, what good feels like to a client. Steps only cover situations you already anticipated. Judgment is what stops the questions.
This is the Enablement pillar
OPERATE names this one directly: the SOPs exist and nobody uses them. There's a folder. It was written once, eighteen months ago, and it describes a process that has changed twice since. So people ask you instead, which is faster and confirms the doc was pointless.
And notice which force is actually failing. It looks like education — bad docs — but it's mostly environment: the system that supports action. You can give someone real authority and real knowledge, and they'll still stall if the environment makes acting harder than asking. Reading your SOP is harder than asking you. That's an environment fact, not a content fact, and no amount of rewriting fixes it.
The measure is the only one that means anything: not whether the folder exists, but whether the questions stop. If you have documentation and the questions haven't stopped, the useful work is finding where the work actually flows and putting the knowledge into that path. That's what an OPERATE Report maps — and it usually turns out the folder was fine and the plumbing was never built.
Nobody follows the SOP because it's competing with you and losing — a doc must be remembered, you can be asked. Put the knowledge in the path of the work, and answer the next question in the doc instead of the thread.