The Part of the Job You Can’t Put in an SOP

We spend a lot of time trying to get what people know out of their heads and into a process. That is usually a good thing. If a task is repeatable, the answer should not live with one person.

But there is a point where documentation stops helping.

You can document the answer. You can’t document judgment.

The easy 80 percent belongs in the process

Standard work matters. Receiving steps, reorder rules, approval limits, system transactions, safety checks, escalation paths. If the same situation happens repeatedly, we should not require someone to rediscover the answer every time.

Good documentation reduces variation. It makes training easier. It gives people a place to start. It protects the operation from becoming dependent on whoever happens to remember how something was done three years ago.

That is the part we can write down.

Then reality walks through the door

The supplier is late, but the job cannot stop. The system says there is inventory, but the shelf says otherwise. Two reasonable rules point in opposite directions. The problem looks familiar, but one detail makes it different.

Now the SOP is not the answer. It is context.

Someone still has to notice what is different, ask the next question, understand the tradeoff, and make a decision with incomplete information.

That is judgment.

Experience is not the same thing as memory

Experienced operators are valuable because they have seen enough patterns to recognize when the current situation does not quite fit the standard one. They know which detail matters. They know when to keep following the process and when to stop and ask why.

That kind of knowledge is difficult to capture because it is not a list of answers. It is a way of thinking.

Curiosity matters. Problem-solving matters. Ownership matters. The willingness to say, “Something about this doesn’t look right,” matters.

So what should we document?

Document the repeatable work. Document the known failure modes. Document the decisions we make often enough that people should not have to reinvent them.

Then use the process to develop people, not to replace thinking.

When someone encounters an exception, do not just give them the answer. Ask what they tried. Ask where they got stuck. Ask what they think the answer is and why.

The goal is not to create a library big enough that nobody has to think.

The goal is to create enough structure that people have room to think about the things that actually require judgment.

That is the part of the job you cannot put in an SOP

A mature operation is not one where every possible situation has been documented. That is impossible.

It is one where the routine work is clear, the knowledge is shared, and people have developed enough judgment to handle what was never written down.

Process gives people a foundation. Experience teaches them when the foundation is not the whole answer.

And that is why the best operations need both.