Standards are relaxed in a series of small steps, each described as an administrative update, so nobody ever faces the decision to lower the standard as a whole.
An example
When the quality assurance manager at a frozen-meals manufacturer joined, the plant held suppliers to a 48-hour window for lab results on incoming poultry. Over three years a series of procedure updates came through the document system. One aligned the window with industry practice at 72 hours. Another let shipments be used on a supplier's own certificate when the lab was backed up. A third reclassified a set of temperature deviations as minor. Operations signed off each change as housekeeping, and none reached the food safety committee. When the manager raised the third change, the plant director said it was hardly worth a fight over routine paperwork. The manager pulled the procedure's version history and laid the original beside the current text, and the food safety committee saw the two together for the first time.
Why it works
Technical language on every step makes accepting it look easier: there is no moral anchor to object to. Objecting looks worse, because the standard being defended has been redescribed as the way things used to be done, and costlier, because anyone who raises ethics over a minor procedural change looks rigid or alarmist. It needs time between steps for people to adjust, administrative vocabulary for every change, no compliance function or counsel with a long memory, and a sponsor willing to give up the lift of arguing openly for the change.
The thinking behind it
Leon Festinger Festinger's A Theory of Cognitive Dissonance (1957) holds that a belief at odds with one's own action is uncomfortable, and that people often resolve it by changing the belief. Staff who carry out each relaxed standard adjust their sense of what the standard should be, and by the third step the original looks like the outlier. A custodian who keeps the original text in view keeps the discomfort alive, which is what lets objection happen.
Amos Tversky Kahneman and Tversky's Prospect Theory: An Analysis of Decision under Risk (1979) holds that people judge outcomes relative to a reference point, usually the current position, a part of the theory less disputed than its claims about loss aversion. Each relaxed procedure is judged against the version just before it, so moving from 48 to 72 hours feels small. Setting the original standard beside the current text restores the original reference point.
Warning signs
Policy exceptions accumulate steadily, each described in technical or procedural terms. No single change reaches a board or audit threshold. Changes are justified by alignment with peer practice or by convenience. Each step is compared with the previous version and never with the original. People who object are told they are making too much of routine paperwork.
How to defend yourself
Compare with the original every time. The tactic works only while each change is judged against the last one. Use ethical language sparingly and concrete consequences freely: what the old standard prevented and what could now happen. An outside regulator or auditor with a long memory is a strong ally.
- Pull the policy's version history and set the original beside the current text.
- Describe the cumulative change in plain words, as the decision it is.
- Bring it to the body that owns the standard, such as compliance, audit, the board, or counsel, as one decision.
How a leader shuts it down
Appoint a custodian, in compliance, audit, or counsel, whose job is to compare every proposed change with the original standard. Keep policies under version control, with reports of cumulative change. Give audit committees long-serving seats, and treat a run of small exceptions to one policy as a signal to review the whole.