How to Build SOPs That People Actually Follow

Disclosure: We may earn a commission when you purchase through links on this site, at no extra cost to you. How we make money.

Most standard operating procedures fail the moment they are written. They sit in a shared folder, unopened, until someone makes a mistake that the SOP was supposed to prevent. If you want to build standard operating procedures that people actually use, the writing itself has to change — shorter, cleaner, and structured around what the person doing the task actually needs in the moment.

The goal is not a comprehensive policy document. It is a reference that works in real time, when someone is mid-task and needs to know what comes next.

The Real Reason People Ignore SOPs

When an SOP does not get followed, the instinct is to blame the team. They are cutting corners, skipping steps, not taking it seriously. That is almost never the right diagnosis.

The more common problem is that the SOP is harder to use than just figuring it out from memory or asking a colleague. If reading the document takes longer than doing the task, people skip the document. If the language is vague or assumes background knowledge, people give up and improvise. If the SOP is buried three folders deep in a drive nobody opens, it might as well not exist.

An SOP that does not get used is not a people problem. It is a design problem.

Write for the Person Doing the Task, Not the Person Approving It

This is the single most important shift when you build standard operating procedures. Most SOPs are written in a voice that sounds like a policy manual — passive, formal, written as if for an audit. That voice is wrong for the purpose.

Write in second person, active voice, present tense. “Open the client folder” instead of “The client folder should be opened.” “If the invoice is missing a PO number, email the client before processing” instead of “Invoices without PO numbers require client communication prior to processing.”

The person following the SOP should feel like someone is walking next to them, telling them exactly what to do. Not like they are reading a legal document that was translated from another language.

Keep It Short Enough to Read in One Minute

There is no award for length. A one-page SOP that gets followed beats a ten-page SOP that never gets opened.

A practical target: if someone cannot read the SOP in under 90 seconds, it is probably too long. That translates to roughly 200 to 400 words for most common tasks. You can cover a lot of ground in 300 words when you cut everything that is not directly actionable.

Things to cut:

• Background context about why the process exists (put this in a separate document if it truly matters)
• Statements about what the process is meant to achieve (the task itself communicates this)
• Redundant reminders to check things you already listed as steps
• Caveats and exceptions that apply to less than 5% of cases (handle these separately)

If something genuinely cannot be shortened without losing critical information, consider whether it should be split into two SOPs instead of one long one.

Structure It Around Steps, Not Paragraphs

Prose is hard to follow when you are mid-task. Numbered steps are not. This is not a stylistic preference — it is cognitive load. A person doing a task needs to track where they are and what comes next. A numbered list makes that effortless. A paragraph requires re-reading to figure out what you have already done.

Structure every SOP the same way:

• Trigger: What starts this process? (“When a new client signs the contract…” or “Every Friday at 4pm…”)
• Steps: Numbered, one action per step, written in plain language
• Decision branches: Inline, as short as possible (“If X, do Y. If not, continue to step 5.”)
• End state: What does done look like? What gets marked complete, filed, or sent?

Consistent structure means people know where to look and what to expect. That alone reduces friction dramatically.

Test It Before You Publish It

The best way to know if an SOP works is to hand it to someone who has never done the task before and watch them try to follow it. Do not help. Just observe.

Anywhere they pause and look confused is a gap. Anywhere they ask a question is something you forgot to write down. Anywhere they complete a step incorrectly despite following your instructions is a clarity problem.

This test takes 15 to 20 minutes and saves enormous amounts of time later. Most SOPs fail this test on the first try, which is exactly the point. Better to find out now than after someone follows it wrong in a real client situation.

After the test, update the document based on what you observed. Do not ask the tester what was confusing — you already saw it. Fix the specific places where they stumbled.

Make Them Easy to Find at the Moment of Need

Even a perfect SOP fails if nobody can find it when they need it. Think about where the person doing the task actually is when they need to refer to it. Are they in Gmail? In your project management tool? In a client portal?

Put the link to the SOP as close to the task as possible. A link in the relevant Asana task template, a bookmark in the browser profile, a pinned message in the relevant Slack channel — all of these work better than a master folder called “Procedures” that requires three clicks and a search.

If your team uses a specific tool for task management, embed SOP links directly in task templates so the reference appears automatically when the task is created. That is the lowest-friction approach: the document arrives when the person needs it, without them having to look for it.

The SOP that gets followed is not necessarily the most thorough one. It is the one that is short enough to read, clear enough to follow, and close enough to the task that pulling it up requires no effort. Build for those three things first. Everything else is refinement.

Pick one process your team handles this week that produces inconsistent results. Write an SOP for it using the structure above, test it with someone unfamiliar with the task, and put the link somewhere they will actually see it. That is enough to make a measurable difference before the week is out.