Gatekeepers grant the exceptions to a new standard that they judge justified, case by case and on the record, and over time those exceptions decide how much of the standard survives.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
Eight months after a specialty chemicals company signed a single global contract for packaging drums, a plant controller in Louisiana had approved six exceptions to it. Each went into the procurement system with a reason code and a note: a customer who specified a drum the global supplier did not make, a quality failure in the first two deliveries, a local supplier whose price beat the contract by 11 percent at that plant's volume. She sent the chief procurement officer a quarterly summary of every exception she had granted. By year end, controllers at nine plants had approved thirty-four exceptions, and the summaries showed that a third traced to the same quality problem. Procurement renegotiated the specification with the global supplier, and the controllers withdrew eleven exceptions within a month.
Why it works
Each exception makes the old workflow easy and official for the plant that needs it, and enough of them change what the standard is worth: pricing power and comparability drain away as volume moves outside it. Granted on the record, the exceptions also become information, since a pattern in the reasons tells the policy owner where the standard is wrong. The gatekeeper's delegated authority is the condition, along with reasons that hold up case by case and a central owner who reads the totals.
The thinking behind it
Thomas C. Schelling In Arms and Influence (1966), Schelling describes salami tactics: a line can be defeated by crossing it in slices, each too small to justify a response. An exception cascade crosses a standard the same way, one reasonable case at a time, until little of it remains. Granting exceptions on the record, with a running total sent to the policy owner, turns the slices back into a visible whole and lets the owner decide whether to fix the standard or reassert it.
When it fits
Gatekeepers with delegated exception authority, such as plant controllers, regional finance leads, or architecture reviewers, are the people this fits. It suits a standard that is right in general and wrong in specific places, where local knowledge sees costs the center cannot. You need reasons you can defend one case at a time.
How to use it well
Judge each case on its own merits and write the reason down where the policy owner can see it.
- Use a consistent reason code, so exceptions can be counted and compared.
- Send the policy owner a regular summary of everything you granted, with the total.
- Put an end date or review point on each exception.
- When the same reason keeps recurring, take it to the owner as a problem with the standard.
Exceptions on the record give the owner a choice: fix the standard or accept the variance. Either is a better outcome than a rule that erodes unseen.
What it costs and where it backfires
Every exception weakens the standard's benefits for everyone, and a policy owner who sees the total rising may take back your authority. Peers who were refused will compare cases. Granting exceptions without a record, or with reasons you know are pretexts, to sink a policy you opposed is concealment from an owner who is entitled to know, and once the totals surface the cascade will be traced to you.
When it is used on you
Owning a standard that is eroding, pull every exception granted, with requester, approver, and reason, and report the total monthly to the sponsor. Bring authority back to the center or cap it, add sunset dates, and read the reasons for the problems with the standard they reveal.