Adoption
Five Reasons Your Team Is Not Following the New SOP, Ranked
All five are change problems. Not one is a writing problem.
By Charley Bixby · 6 min read
From inside the last several engagements, here are the five most common reasons a new or rewritten SOP fails to get followed. Ranked by frequency.
That distinction matters. If you are trying to fix adoption by editing the document, you are working on the wrong thing.
They do not know it changed
The most common failure mode. The new version went live. Nobody got the memo.
What this looks like: the SOP team finalizes the new version, uploads it to the document system, marks it published. The people who actually do the work never receive a notification. Or they receive a notification that gets buried in 40 other emails that day. Or they receive one that says "Policy update: SOP-014 v3.2" with no human-readable context, which they archive without reading.
The system technically published the SOP. The communication never reached the people who needed it.
Fix: A brief, in plain language, from a named owner, sent through a channel the affected team actually reads, with the why up top. Five sentences. Not a 40-page change log. Not an automated email from the document system.
They cannot find the current version
Two versions exist in three places. They default to the one on their desktop.
Most organizations accumulate parallel copies of SOPs over time. The official version lives in the document management system. A copy lives on the team's shared drive. Someone printed it out and laminated it for the break room. A field manager has a PDF on their phone. A trainer has a Word document they use for new-hire orientation. The intranet has a copy from 2022.
When a new version is published, the official version updates. The other six copies do not.
Fix: Eliminate parallel copies systematically. Either remove them entirely or set up an automatic refresh when the canonical version changes. One canonical "this is current" location, with everything else either non-existent or auto-updated.
They do not believe the new version is final
Last time leadership announced a process change, it was reversed in two months. They are waiting it out.
In organizations with a history of half-implemented changes, the team learns to ignore new SOPs until they have proof the change will stick. The signal they are watching for is enforcement. Does leadership actually use the new SOP in their own decisions? Does the manager refer to it in 1:1s? Does it show up in the way work gets reviewed?
If not, the team assumes this one is going to fade like the last one.
Fix: Demonstrate enforcement early. The owner of the SOP, and their manager, should be visibly using the new version in the first 30 days — in meetings, in decisions, in reviews. If leadership cannot do this, the SOP will not stick.
The new way is harder than the old way and nobody explained why
Sometimes the new SOP introduces friction. A new approval step. A new documentation requirement. A new check that adds 3 minutes to a process. From the team's perspective, the new way is objectively worse than the old way.
If the why is not explained — if the additional friction is not connected to a real risk it is mitigating — the team's pattern-match is "leadership is making us do extra work for no reason." They will do the new way when supervised and the old way when not.
Fix: When the new SOP is harder, lead with the harder part and explain it. "We are adding a peer-review step before invoices go out. The reason is that we found three errors last quarter that cost us $X each, and a quick second set of eyes would have caught all three." That is the rollout.
Acknowledgment was treated as an audit checkbox, not a moment of actual reading
When acknowledgment is collected as a quarterly sweep — 30 SOPs, batch email, click through to clear — nobody is reading anything. The acknowledgment record exists. The reading did not happen. The adoption did not happen.
When acknowledgment is captured at the moment the SOP becomes effective — version-specific, time-stamped, in context — the person checking the box has a real reason to actually look at the document.
Fix: Trigger acknowledgment at effective date for each individual SOP, not in a quarterly sweep. New version, new acknowledgment. The acknowledgment becomes a moment, not a chore.
The summary
All five are change problems. Not one is a writing problem.
The fix is rarely a better SOP. It is a tighter rollout — visible owner, real reason, real acknowledgment, easy way to find the current version, demonstrated enforcement.
That is the part the document tool does not handle. That is where SOP Studio lives.
Charley Bixby is co-founder and VP of Operations at SOP Studio.