How an SOP quietly stops being followed

Not through one big break. Through six small ones nobody wrote down.
An SOP rarely fails all at once. It fails through a series of small, individually reasonable exceptions: a supervisor lets one associate skip a scan step because the scanner is charging, a new hire is shown the "quick way" by a colleague instead of the training material, a seasonal peak makes double-checks feel like a luxury.
Six months later, what the floor actually does bears little resemblance to what is written down — and nobody decided that on purpose. It drifted, one shortcut at a time.
The fix is not a stricter document. It is a short, scheduled re-audit — walking the floor with the written SOP in hand and noting every place reality has quietly diverged — followed by a decision: either retrain back to the standard, or update the standard because the floor found a genuinely better way.
We run this check quarterly at every facility. Most quarters it finds two or three small drifts. Catching them at that size is the entire point.
