Adoption

The Three Traits of SOPs People Actually Follow

Writing a good SOP is the easy part. Writing one people actually follow is a change-management problem first and a documentation problem second.

By Charley Bixby · 5 min read

I have watched a lot of new SOPs go live.

The ones that get followed share three traits. The ones that get ignored share the opposite three. After enough engagements, the pattern is impossible to miss.

Trait 1

The team understood why before the document landed

The single biggest predictor of SOP adoption is whether the people affected understood the reason for the change before the document showed up. Not "communication." Not "we sent an email two weeks ago." Actual understanding — at the level of being able to explain to a colleague why this process is changing and what it is supposed to fix.

Fix: Treat the rollout as a change-management event, not a documentation event. A brief from the owner, in plain language, before the document goes live. What is changing. Why. What it solves. What the team should do differently. Five minutes of context, every time.

Trait 2

One named person owned the rollout

Not a team. Not a Slack channel. A person. The rollouts that fail at adoption almost always have distributed ownership. "The QA team is rolling it out." "Operations is leading on this one." That means nobody is on the hook for the moment the SOP becomes effective. Nobody is checking whether people read it. Nobody is fielding the questions that come up in week one.

Fix: Single-name ownership of the rollout, distinct from single-name ownership of the SOP. The SOP owner keeps the document current. The rollout owner makes sure the team adopts it. Often the same person. Sometimes not. Always one name.

Trait 3

Acknowledgment was captured at go-live, not chased at audit

When acknowledgment is captured at the moment a SOP becomes effective, it functions as a behavior signal. The person checking the box is reading the document — at least skimming it — because the moment they check is the moment they need to know what is in it. When acknowledgment is collected three months later in a sweep, it is paperwork.

Fix: Capture acknowledgment at go-live. It is the cheapest behavior intervention in the rollout. Skip it and you are accepting that adoption is whatever happens by accident.

Ignored: the opposite three

Same patterns, inverted.

  • The document showed up in an email and that was the rollout. No why. No context. No live brief. Just a PDF and a link.
  • Ownership was distributed across three people, which means nobody. No single name on the rollout. The team is "leading on this one."
  • Acknowledgment was a spreadsheet someone said they would get to. Three months later, the spreadsheet has 40% completion. The audit is in two months.

These are not random failures. They are predictable, repeatable failures that follow the same pattern in every industry I have worked in.

The point

Writing a good SOP is the easy part. The drafting tools have gotten good enough that any team with five hours and a clear process can produce a competent document.

Writing one people actually follow is a change-management problem first and a documentation problem second.

The fix is rarely a better document. It is a tighter rollout.

Charley Bixby is co-founder and VP of Operations at SOP Studio. 10+ years of change management and adoption work inside healthcare contact center operations.