Why don't employees follow written processes?

Something is already written

From Luba Inz's work with ~100 business owners: about 80% of companies have something written down when the work starts. A checklist, an onboarding document or a folder of SOPs someone wrote two managers ago.

The writing exists. Nobody follows it. Nobody tracks whether anyone does. So the team learns the work from the person next to them, and every exception still goes to the owner.

The three missing pieces

1. An owner. One role that answers for the process and fixes it when it breaks. A document everyone owns is a document nobody owns.
2. A limit on each decision. Most SOPs list the steps and skip the judgment calls. When the document doesn't say who decides and up to what amount, people ask. The process routes around itself.
3. Tracking. One number that shows each week whether the process worked, and a place where someone looks at it. Otherwise, nobody knows the process stopped being followed until a customer says so.

A process with all three gets followed, because someone is watching it and the people doing it know where their authority ends.

Write the decisions, not only the steps

The steps aren't why people stop following a process. The decision points are. When the work can go two ways and the document doesn't say which, the person doing it guesses or asks.

An SOP that holds up has seven parts: trigger, inputs, decision points, authority limit, escalation, owner and measure. How to write an SOP an AI agent can follow has all seven, with a filled example. If a person can follow it without asking, an agent can too.

You don't have to start from a blank page. We start from a library of pre-built SOPs and fit them to how your company actually works.

Where it gets checked every week

A process gets followed when someone checks it on a set day. Put each process's measure on the page that goes out before the weekly operations meeting. The owner of each number brings it only if it crossed its trigger.

If the same process shows up three weeks in a row, the document or the limit is wrong. Change it. Keep the owner where they are.

Codify vs Pulse in SCOPE™

SCOPE™ by Efficiency Sprint places a company in one of five states: Stabilize, Codify, Ownership, Pulse and Engine.

Writing a process down is Codify: make the recipe clear. A folder of SOPs is a start on Codify, not the end. The recipe needs Ownership, where people run it reliably, and then Pulse, where AI watches and reports. At Pulse, a process that stops being followed shows up as an exception in a weekly report instead of as a surprise.

Skipping to AI doesn't fix it. AI scales whatever's already there. Every agent runs until it hits a gate a person still owns.

Find out where your company stands

Efficiency Sprint makes companies operationally ready for AI. The operational AI readiness check takes about two minutes and shows where your company stands. The full set of numbers is in our report on how owner-led companies run.