The Procedure on Paper Is Not the Procedure on the Floor

At one organization where I worked, SOPs came up constantly. They were mentioned in meetings, referenced in performance conversations, and pointed to whenever something went wrong. “Follow the SOP” was part of the everyday vocabulary.

But when I asked people where the SOPs actually were, most could not tell me. Front-line employees did not know. Supervisors gave different answers. Even executives were not sure where the procedures were kept, or whether some of them existed at all.

That experience taught me something. Organizations often value SOPs as an idea. They see them as the standard for how business should be done, and as a way to cut costs and improve quality. Leaders are right about that. But valuing the idea is not the same as doing the work: writing the procedures, keeping them current, putting them where people can find them, and building them into training. When that work is skipped, the SOP becomes something everyone talks about and almost no one uses. The procedure on paper says one thing, if anyone can find the paper. The work on the floor does another.

I think about that company often, because it was not unusual. I have seen versions of the same thing since. When people stop following a procedure, or cannot even find it, leaders tend to look at the employees first. I have learned to look at the procedure first. It usually has something to tell us.

Why procedures fall behind

An SOP describes the work on the day it was written. The work keeps changing after that. A software update moves a screen. A new product line adds a step. A customer complaint leads to a new check that someone explains in a team huddle and never writes down. Within a year or two, the document describes a job that no longer exists.

Who writes the procedure matters too. Many SOPs are written by managers or consultants who have never done the job themselves. They capture the ideal version. What they miss are the exceptions and judgment calls that fill a real shift, and those are exactly the things employees need help with.

Then there is length. Some procedure documents run forty pages. Every detail may be correct, but nobody can find an answer in forty pages while a customer waits on the line. So people ask the person next to them, and the document sits.

And sometimes the people on the floor have simply found a better way. That is not rule-breaking. It is process improvement that nobody captured.

Where it really breaks down: training

This is the part I think gets overlooked most. Even a good, current SOP does very little if it stays a document.

In many organizations, the training team builds its own materials. They write slides and role-plays, often without opening the SOP. A new hire learns one version of the job in the classroom and a different version on the floor. When the procedure gets revised, the training usually does not, so it is common to find trainers still teaching steps the company changed months ago.

The other missing piece is the work guide. An SOP explains what has to happen and why. A person in the middle of a task needs something different: a checklist, a quick reference card, a screen-by-screen walkthrough, or a simple chart for the common exceptions. When nobody creates those, employees make their own. You see it in sticky notes on monitors and in notebooks that new hires guard like treasure.

Supervisors end up coaching from their own experience, since that is all they have. Put it all together and you get a strange result. The official standard is the one thing nobody is trained on, coached on, or measured against.

What it costs

None of this stops the work from getting done, which is why it is easy to ignore. The cost shows up elsewhere. Two shifts handle the same customer issue two different ways. Training takes longer because every new hire learns from whoever happens to sit beside them. A veteran employee retires, and the real process retires with them.

It also makes accountability unfair. If an employee makes a mistake, was it their error or the procedure’s? A leader cannot answer that honestly when the document and the work disagree. In regulated work there is a legal side as well. An auditor reads the written procedure, not the habits on the floor.

That brings me back to the argument leaders make for SOPs: they cut cost and improve quality. That is true. Standard work does both. But only the standard work people actually do.

A simple test

If you want to know where your organization stands, try this. Pick one important task. Ask a new hire, a veteran, and a manager where the procedure for it lives. Then sit with someone doing that task for an hour, with the SOP open beside you, and note what they skip, add, or do in a different order.

You will learn more from that hour than from most procedure audits. If you hear the phrase “the way we really do it,” you already have your answer.

Making procedures real

The fix is less about writing better documents and more about how they get made and kept up.

Write them with the people who do the job. They know the exceptions. When you find a workaround, ask why before you correct it. If it is better, adopt it. If it is risky, explain the reason behind the official step, because people follow rules they understand.

Then treat every SOP as the start of a set, not a finished product:

• the procedure itself, kept short and in plain language
• a training module built from it
• a work guide employees keep at their desk or station
• a named owner and a review date, with any system change triggering an update

Keep all of it in one place people can search, such as an intranet. If an employee, or an executive, cannot find a procedure in under a minute, then for practical purposes it does not exist.

Organizations are right to value SOPs. The real question is whether they value them enough to do the work that makes them real.