Why People Skip Standard Work (and What to Fix Instead)

You documented the process. You trained the team. You laminated the one-pager and pinned it to the board. Three weeks later, nobody is following it.

This is one of the most common frustrations in continuous improvement work. You invest time building standard work, and then watch people quietly revert to the old way. The instinct is to treat it as a discipline problem. Retrain. Remind. Escalate.

That instinct is usually wrong.

The Deviation Is Telling You Something

When someone skips a documented standard, the first question worth asking is not "why won't they follow it?" but "what is stopping them?"

There is a difference between a motivation problem and a barrier problem. Motivation problems are rare. Most people do not wake up wanting to ignore a process that makes their job safer or easier. Barrier problems, on the other hand, are everywhere: the tool is in the wrong location, the step takes longer than the window allows, the standard assumes two people when only one is available.

If you treat a barrier problem like a motivation problem, you get posters, reminders, and stern conversations. None of these remove the barrier. They just add guilt on top of it.

A Useful Test: Could They Follow It If They Wanted To?

Before escalating a deviation, walk the process yourself. Not on paper. Physically. At the time of day when the work happens, with the staffing level that actually exists, using the equipment that is actually available.

You will often find that the standard works perfectly in a training room and falls apart on the floor. A step that takes forty-five seconds with full staffing takes three minutes when someone is covering two stations. A form that makes sense at a desk is unworkable when you are standing at a machine with gloves on.

This is not a failure of the people. It is a failure of the standard to account for the real conditions of work. And that is a design problem, which means it is your problem.

Three Common Barriers Worth Checking

1. Physical distance from the work. Tools, forms, or equipment stored away from where the task happens will get skipped. If someone has to leave their workstation, walk to another area, and come back, the standard competes with every other demand on their time. Moving materials closer to the point of use is often enough to change the behaviour entirely.

2. Time pressure that the standard ignores. Standards built during a calm observation period often assume a pace that does not exist during peak demand. If the standard takes four minutes and the takt time is three, people will find shortcuts. The answer is not "work faster." It is redesigning the sequence so it fits inside the real time constraint.

3. Ambiguity in the method itself. A standard that says "check quality" without specifying what to look for, how, and what counts as a pass or fail leaves room for interpretation. Every person interprets differently. That is not non-compliance. That is a vague instruction producing variable output, exactly as you would expect.

How You React Matters More Than What You Write

Your response to a deviation teaches the team more than the standard operating procedure ever will.

If you respond with blame, the team learns to hide problems. If you respond with enforcement alone, the team learns to comply when observed and revert when not. Neither outcome gives you the information you need to improve.

Mark Graban illustrates this clearly in a post on leader reactions when standard work breaks down. He describes a hospital where staff repositioned patients by hand instead of using a lift assist, because the equipment was stored on a different floor. Management hung a sign berating staff for the deviation. The sign did nothing. What finally worked was using 5S to free up storage space and move the lift assist onto the unit where the work happened. Once the barrier was gone, the deviation disappeared with it.

The sign was the cheapest response. It was also the least effective. Removing the barrier cost more effort upfront but actually solved the problem.

Practical Steps When You Spot a Deviation

1. Go to the gemba. Watch the process happen in real conditions, not in a conference room.
2. Ask "what makes this hard?" before "why didn't you follow it?" The phrasing matters. One invites a barrier. The other invites a defence.
3. Check the three barriers above. Distance, time, ambiguity. Most deviations trace back to one of these.
4. Revise the standard, then re-observe. A standard is a hypothesis about the best current method. When reality disproves it, update the hypothesis.
5. Close the loop visibly. When you change the process based on what someone told you, tell them you did it and why. That teaches the team that speaking up leads to improvement, not punishment.

Standards Are Living Documents

Standard work is not a contract employees sign. It is a snapshot of the best-known method at a point in time. When people deviate, the snapshot may be out of date. Treating every deviation as defiance is how organisations end up with binders full of standards that nobody uses and nobody updates.

The goal is not perfect compliance. The goal is a reliable process that people can actually follow, and a culture where they tell you when they cannot.