Adoption

The Document Was Published. The Change Was Not.

Those are different events. Most teams confuse them.

By Charley Bixby · 5 min read

“We rolled out a new intake SOP six months ago. I genuinely thought we had nailed it. Last month I sat in three different clinics and watched three different versions of the workflow happening. Two of them were the old way. One was a hybrid the front-desk team invented. The new SOP exists in the system. It is not what people are doing.”

— VP of Operations, 180-person multi-site clinic

She is not unusual. She is the median.

Two events, often confused

There are two distinct events in any process change:

  1. The document was published. The SOP is current, approved, sitting in the document system, with a version number and an effective date.
  2. The change happened. The people whose behavior the SOP describes are now doing the work the new way. Reliably. Without supervision. As their default.

Most teams treat these as the same event. They are not. They are weeks or months apart in the best case. They are years apart or never converge in the worst case.

The VP above thought she had landed event two. She had landed event one. Event two was happening for some of her staff in some of her clinics some of the time.

Why this confusion is so common

The metrics are vanity metrics

"100% of staff acknowledged the new SOP." "The new version has been live for 6 months." "Document management system shows compliance at 98%." None of those measure whether the work is being done the new way. They measure whether the paperwork is in order.

Leadership rarely watches the work

The people who own the SOP usually do not sit in the clinics, on the production line, in the call center. They see the dashboard. The dashboard shows publication. The actual workflow is in a room they do not visit.

The team does not flag the gap

When the new SOP introduces friction or conflicts with how the work has always been done, the team adapts quietly. They keep doing some version of the old way. They do not file a complaint. They just keep working in a way that lets them get the day done.

The audit window covers it up

When the audit is six months out, leadership is focused on having the documents in order. Acknowledgments collected. Approvals recorded. The audit story looks fine on paper. The fact that the work is not actually being done the documented way only surfaces if someone goes and watches.

What the VP did next

After she sat in three clinics and watched three different workflows, she did not blame the staff. She did three things.

  1. She asked the front-desk team why they had invented a hybrid. The answer was that the new SOP added a step that did not work in clinics with limited check-in space. The hybrid was a sensible adaptation. The team had not flagged it because nobody had asked.
  2. She asked the staff still doing the old way why. The answer was that the new SOP had been emailed out with a link to the document system. They had not opened it. They were not sure it had replaced the old one. Their manager had not mentioned it.
  3. She did not re-publish the SOP. She published a one-page memo with the why, had the SOP owner walk through it in each clinic's morning huddle for a week, fixed the version that did not work in small clinics, and put one named person in each clinic on the hook for adoption in that location.

Six weeks later she sat in the same three clinics. All three were doing the new workflow. With local adjustments to the small-clinic version that she had now made canonical.

That sequence is what “the change happened” looks like in practice. It is not magic. It is a different kind of work from publishing a document.

The point

The document was published. The change did not happen. Those are different events. Most teams confuse them.

If your team has a brand-new SOP that nobody is following, the fix is not another document. The fix is going to where the work actually happens, watching, asking, and treating the rollout as ongoing — not as a date that already passed.

Publication is the start of the change effort. Most teams treat it as the end. That is the gap.

Charley Bixby is co-founder and VP of Operations at SOP Studio.