Written down is not wired in
Having a rule and actually running one are separated by a distance most businesses never measure.
I caught it before it went out. A filter was there - written into the build, agreed on in the brief, nodded at by everyone involved. But nothing was actually reading it. The audience count was seven times what it should have been.
Seven times. Not a rounding error.
The thing about a rule that exists but is not enforced is that it gives you false confidence. You wrote it down. You told someone. You built the field for it. You checked the mental box that says we have a policy for this. And then the policy sits in a corner that nothing ever reads, and the system does exactly what systems do when left alone: whatever it was doing before you had the policy.
I have watched this pattern cost founders more than any single bad decision. Not because the rules were wrong. Because the rules were right - and never wired into anything that actually runs.
The distance between intent and behavior
This is not a technology problem. It is a business-design problem that shows up in every kind of operation. You say the team handles refunds within 48 hours. Does anything enforce that, or is it just known? You say you do not take clients below a certain size. Is that written somewhere someone checks when a small inquiry comes in, or is it a principle that bends when revenue is thin?
The rules a business actually runs on are not the ones in the handbook. They are the ones the system follows when nobody is watching.
Wiring is slower than writing. That is the honest reason so many rules live in notes fields. Writing a rule takes ten minutes. Building it into the thing that runs when you are not looking takes longer and feels less like progress. So we write the rule and call it done. But a policy that is not enforced anywhere is just a wish with good formatting.
I found the seven-times count and fixed it before anything went out. But I had to ask how many other things in my businesses are running on rules I wrote and never checked were being read.
That audit - not financial, not operational, just does this system know what I think it knows - is the one most of us avoid the longest.
One honest sweep of that question is worth more than a month of writing new rules.