The Person Who Grants the Exception
When a rule gets too expensive, people don't repeal it — they route around it one waiver at a time. The person who approves the waivers becomes the real policy, and nobody wrote that one down either.
Blog
The Rule Nobody Can Retell
Every process rule started as an incident. The rule outlives the story, and once the story is gone the rule can only be obeyed or resented — never evaluated.
Your Policy Is the Diff
The written ruleset only grows. The waiver path is the only place it shrinks. Neither one records why — so what your organization actually does lives in the difference between them, and nobody owns that difference.
The Bugs You Hear About
A defect list looks like an inventory of what's broken. It's actually an inventory of the overlap between what's broken and who still believed telling you would help.
The Count Is a Relationship
Users who give up stop filing. Teams who get ignored stop filing. Both make the same number fall, and neither required anyone to decide anything.
The Team That Answers
The same filter that shapes what users report also runs inside the building. The team that responds fastest ends up looking like the one that ships the most defects.
The Cost Nobody Meters
Every other expense in a system gets a number attached to it. The cost of understanding the system is paid privately, once per person, and never recorded — which explains both why you can't see it and why nobody fixes it.
The Perishable Instrument
A new engineer's confusion is the only direct measurement you'll ever get of how legible your system actually is. It's also a reading that expires in about three weeks, and most teams spend those weeks destroying it.
The Toll You Already Paid
The window where a new engineer can see your system clearly doesn't just close. It reverses — and the person who found the setup baffling in week one becomes, by month six, one of the reasons it never gets fixed.
The Name Gets Out
A name coined in a schema column doesn't stay there. It spreads into API fields, docs, dashboards, and eventually the customer's own sentences — and by the time it's wrong, fixing it is a negotiation, not a refactor.