By Mike Bandar, Co-founder of Waybook.
You get a team to follow SOPs by making each one short, assigning it to the people who do the task, answering questions with a link to it instead of an explanation, and asking for a read confirmation so you know who has seen it. Teams ignore SOPs that are long, buried in a folder, written by someone who does not do the work, or out of date. This post covers why SOPs get ignored, the habits that fix it, how long it takes, the mistakes to avoid, and how to tell it is working. The tool it runs on is Waybook: SOPs assigned by role, read confirmation and a short test on each, an owner and a review date on every document, published pricing at $99 a month billed annually for 20 members, and a 7-day free trial you start yourself.
Last updated: October 2026
Why teams do not follow SOPs
Almost never because they disagree with them. Teams skip SOPs for four reasons: they cannot find the right one when they need it; it is too long to follow while doing the task; it was written by someone who does not do the work, so it is wrong in small ways; or it is out of date and everyone knows it. Each of the four is a design problem, not a discipline problem.
How do I get my team to actually follow our SOPs and use them?
Assign, do not publish. Send each SOP to the roles that use it with a read confirmation, instead of announcing a library. People follow what they were asked to read.
One task per SOP, short enough to follow while doing it. If it needs scrolling on a phone, split it.
Write it with the person who does the task. Capture it while they work, or have them describe it and let an AI draft do the writing, then let them correct it. In Waybook, Shots captures the steps and the AI SOP creator drafts from a description.
Answer questions with a link. When someone asks how something is done, send the SOP. Within a month the team checks first.
Put it where people already work. On the phone for staff who are not at a desk; in Slack or Microsoft Teams for everyone else. Waybook sends assignments and updates to both and has a mobile app.
Give every SOP an owner and a review date. An SOP that is visibly current gets trusted. See how to keep SOPs up to date.
How much time does it take to set up?
Less than most teams expect. The first SOPs can exist the same day, and a 20-person team on Waybook is typically assigned and read-confirmed inside a week. Start with the five tasks people ask about most; those five do more for adoption than fifty nobody needed.
What are the most common mistakes to avoid?
Writing every SOP before assigning any; one person writing all of them; long documents that cover a whole department; publishing to a folder instead of assigning to people; no owner, so nothing gets updated; and never checking who read them. More in the five SOP mistakes to avoid.
How do I know the team is following them?
Track three things: the share of assigned SOPs read and confirmed, the pass rate on a short test attached to the critical ones, and how often the same questions still reach managers. Waybook's progress tracking shows the first two by person or by document, and confirmation steps make someone confirm a step was done, not just read.
Frequently asked questions
How do I get my team to actually follow our SOPs and use them every day?
Assign each SOP to the people who do the task, keep it to one task, answer questions with a link to it, and ask for a read confirmation. Teams use what they are assigned and can find in seconds.
How much time does it usually take to get a team following SOPs?
A few weeks for the habit, a week for the tool. On Waybook a 20-person team is typically assigned and read-confirmed inside a week; the habit of checking first forms once managers answer questions with links.
What are the most common mistakes to avoid?
Writing everything before assigning anything, documents that are too long, publishing to a folder, no owner, and never checking who read them.
Why do employees ignore SOPs?
Because they cannot find them, they are too long, they are wrong in small ways, or they are out of date. Fix the design and adoption follows.
How do I get buy-in from the team for SOPs?
Have the people who do the work write or correct their own SOPs, start with the tasks they ask about most, and show them the questions they no longer have to answer.
How do I prove the team has read an SOP?
Ask for a read confirmation on it and check the record. Waybook records who read and confirmed each SOP, by name and date, and who passed any test attached.
