Why Employees Don't Follow SOPs

By Lisa González, Certified EOS Implementer® and co-author of Process! (The EOS Mastery Series). Updated August 5, 2026.

Employees skip SOPs for a handful of predictable reasons: the document doesn't match how the work really gets done, it's too long to use mid-task, they were never trained on it, they had no hand in creating it, they can't find it or it's out of date, or nothing happens when they skip it. There are usually more, but they cluster here. None is a character flaw, and every one traces back to two things: how the process was documented and whether it is held accountable.

I'm Lisa González, co-author of Process! How Discipline and Consistency Will Set You and Your Business Free, the official EOS® book on process, and a Certified EOS Implementer® who has worked this exact problem with leadership teams in hundreds of sessions. Before that, I lived it while scaling our family remodeling business. We had beautiful SOPs nobody followed. Here is what actually changes behavior.

Why employees don't follow processes

Processes and SOPs fail for the same reasons. Whether you call it a process, an SOP, or a procedure, people skip it when the document does not match the real work, when it runs too long to use mid-task, when they were never trained on it, when they had no hand in building it, when they cannot find it or it is out of date, or when nothing happens if they ignore it. The fixes below work the same way for all of them.

The two tools behind every fix

Almost every reason on this page is one of two problems. It is either a documentation problem or an accountability problem.

The documentation problems get solved by the EOS 3-Step Process Documenter: identify your core processes, document and simplify each one, then package them so they are followed by all. The accountability problem gets solved by your FBA checklist, the way you measure and review whether a process is actually Followed By All. Keep both in mind as you read the reasons.

Reason 1: The SOP doesn't match reality

When leadership writes SOPs in isolation, the documents describe how work is supposed to happen. The team knows how it really happens. Faced with a choice between the document and reality, people choose reality every time. Then they stop trusting the documents entirely.

The fix: the people who do the work help document the work. This is step two of the 3-Step Process Documenter, document and simplify. Thirty minutes with the person who runs the process daily is worth more than weeks of leadership guessing. Their fingerprints on the document also become their buy-in.

Reason 2: The SOP is too long

A 40-page SOP is not rigor. It is fear, written down. Nobody consults a 40-page document in the middle of a real task.

The fix: the 20/80 rule, which is the heart of step two. Document the 20 percent of steps that produce 80 percent of the results. One to three pages per process. Major steps, a few bullets each. Save the detailed checklists for the few steps where the cost of error truly justifies them.

Reason 3: Nobody was trained

Many companies email a PDF and expect compliance. Reading is not training. People follow what they have practiced, not what they have received.

The fix: train every employee on the processes that touch their seat. This is part of step three, package and get followed by all. Explain why each step exists. Let people ask questions and flag what's confusing. Their objections are free quality control on your documentation.

Reason 4: The team had no ownership

A process handed down feels like surveillance. A process built together feels like the team's own playbook. Same content, opposite reception.

The fix: assign each core process an owner from the team. The owner leads documentation and proposes updates. Leadership reviews and approves. Ownership turns compliance into pride.

Reason 5: They can't find it, or it's out of date

This is the quiet one, and it undoes good documentation fast. A perfect SOP buried in someone's inbox, scattered across folders, or describing last year's workflow might as well not exist. People look once, come up empty or find something stale, and stop looking for good.

The fix: this is exactly what step three of the 3-Step Process Documenter is for. Package every process in one findable place your whole team knows. Give each one an owner who keeps it current, and put a simple review cadence on it so it never drifts from reality. A document people trust to be right and easy to find is a document people use.

Reason 6: There is no accountability

If nothing happens when a process is skipped, the process is optional. Your team has correctly read the real policy.

The fix: make process followership measurable and visible. This is what the FBA checklist is for. Put a small number of compliance measures on your scorecard, and review whether each core process is Followed By All in your regular meeting rhythm. Start with curiosity: a skipped process usually means a broken process or a training gap, not a bad employee. When the document is wrong, fix it fast. A frictionless update path keeps trust alive.

Where to start

Don't fix everything at once. Pick one high-frequency process where mistakes are expensive or where every person does it differently. Rebuild it with the team using the fixes above: document it with the people who run it, cut it to the essential steps, put it where everyone can find it, and put it on your FBA checklist. Get a visible win. Momentum does the rest.

If you run on EOS, this work lives in the Process Component, and the tool is the 3-Step Process Documenter.

Frequently asked questions

Why don't employees follow processes?

The same reasons apply to processes and SOPs alike: the document does not match how the work really happens, it is too long to use during the task, employees were never trained on it, they had no role in creating it, they cannot find it or it is out of date, or there is no consequence for skipping it. Fix the document and the accountability, and followership follows.

Why do employees ignore SOPs?

The most common reasons are that the SOP doesn't match the real workflow, it's too long to use during work, employees were never trained on it, they had no role in creating it, they can't find it or it's out of date, or there are no consequences for skipping it. There are usually more, but almost all of them are either a documentation problem or an accountability problem.

Where should we keep SOPs so people actually use them?

In one findable place your whole team knows, with an owner who keeps each process current. This is step three of the 3-Step Process Documenter, package and get followed by all. A document nobody can find, or one that is out of date, gets abandoned no matter how good it is.

How long should an SOP be?

One to three pages for most processes. Document the essential steps, not every edge case. If a document runs past five pages, split it or simplify it.

How do I hold employees accountable to processes?

Make followership measurable with an FBA checklist. Track a small number of compliance indicators on your scorecard, review them in your weekly meeting rhythm, and treat skips as issues to solve rather than offenses to punish.

What is process compliance?

Process compliance is the degree to which your team consistently follows your documented processes. In EOS terms, the standard is Followed By All (FBA). It is the difference between having processes and being run by them.

Documented but not followed? That gap is exactly what I help leadership teams close. Book a discovery call.