Most teams that lose the plot did write the standard down. It exists. It is well written. Someone spent a weekend on it, and it is pinned in three places. The work still drifts, and everyone concludes the standard was too vague. The standard was fine. It was in the wrong part of the system.
Here is the mechanism. A standard only does work at the moment it is read, and a system has exactly three places it can put one. In a head, where it is a preference: it applies when that person is looking and vanishes when they are not. In a document, where it is a reference: it applies only to whoever remembers to go get it, which is the people who already agreed with it. Or in the path, where the work cannot continue until the standard has been applied. Only the third one is load-bearing. The first two depend on somebody choosing to consult them, and that choice is the thing volume destroys first.
Watch the arithmetic. At ten pieces a week, the document gets read, because there is slack and the work feels individually consequential. At two hundred, nobody opens it, and not out of laziness — the read is now the slowest step in the line, so the line routes around it. The standard did not get weaker. Its position did. A rule whose enforcement rate falls as throughput rises is not a rule. It is a hope with good typography.
So where in the path. Two coordinates, and both matter. It sits at a handoff — the seam where work changes hands, because that is where assumptions get dropped and where a check has something concrete to inspect. And it sits upstream of the irreversible step — before the send, the publish, the payment, the merge. Downstream of that, the same check is an audit: a careful account of something you already did to somebody. Audits are worth having. They are not standards. They cannot stop anything.
There is a third property, and it is the one most teams skip. The check has to stop the work, not annotate it. A gate that raises a flag and lets the piece pass has converted your standard into a notification, and notifications accumulate in a place nobody owns. If nothing halts, nothing is being held.
Which changes the shape of the artifact. Prose is the wrong form for a thing that has to run two hundred times a week — it needs judgment to interpret, and judgment is the scarce input. What survives is a short list of conditions a piece must satisfy to pass, plain enough that someone other than the author can apply them, and specific enough that the answer is yes or no. That is a small, unglamorous document. It is also the only version of your taste that exists when you are not in the room.
The ten-minute move. Take the standard you already wrote. Find the last moment before something becomes irreversible, and go look at what actually happens there today. If the answer is a person remembering, you do not have a standard in your system. You have one in a person, and you are one busy week from finding out.
Takeaway: A standard is not what you wrote. It is where in the system it sits, and whether it can say stop. ✱
