Norm Drift Review¶
Periodic review — instantiates Norm Shaping
A recurring backward look that re-diagnoses what the group now treats as normal and flags where tolerated exceptions have quietly hardened into the new default.
Norms erode slowly and without announcement. Each individual shortcut, waiver, or looked-past exception seems reasonable in the moment; only in aggregate, and only in hindsight, do they add up to a changed baseline. Norm Drift Review is the scheduled, backward-looking check that catches this. Its defining move is comparison across time: it re-diagnoses what the group currently treats as normal and holds that reading against the intended norm and against the group's own earlier behavior, specifically to find where the tolerated exception has become the unspoken rule. It does not reward, correct, model, or define anything — it detects and diagnoses. Its output is a finding: here is where we have drifted, and here is the exception that quietly became the default.
Example¶
An airline's maintenance organization holds a quarterly Norm Drift Review. The intended norm is unambiguous: every deferred defect is logged, categorized, and cleared within its allowed interval. The review does not watch any single mechanic; it re-reads the aggregate. Pulling the last quarter's deferral records, it finds that a particular non-critical sensor fault is now deferred by default — mechanics have learned it "always comes back clean," so a step that was meant to be an exception has become the routine first move. No policy changed and no one decided this; the baseline drifted one reasonable-seeming waiver at a time. The review names it precisely: the sensor-deferral exception has become the norm, and the interval discipline around it has softened by an average of nine days. That finding is handed to the people who can re-tighten the default and re-model the standard — the review's job is to have seen the drift before it became an incident, not to fix it.
How it works¶
The distinguishing work is periodic re-diagnosis and trend comparison, not real-time correction:
- Re-read the current norm from the record. Reconstruct what the group actually treats as normal now — from logs, exceptions, and behavior under pressure — rather than from what people say they do.
- Compare against two baselines. Hold today's lived norm against the intended norm and against the group's own earlier practice, so both gaps and trends are visible.
- Hunt the hardened exception. Look specifically for waivers, shortcuts, and tolerated deviations whose frequency has crept up — the signature of drift.
- Report, don't remediate. Produce a dated finding and hand it to the mechanisms that reinforce, model, or re-default the norm.
Tuning parameters¶
- Cadence — monthly versus annual. Frequent reviews catch drift early but cost attention and can over-read noise; rare ones are cheap but let erosion run.
- Evidence base — behavioral records versus perception surveys. Records show what people did under pressure; surveys show what they believe, and the two diverge exactly where drift hides.
- Drift threshold — how large a shift counts as reportable. A low threshold catches erosion early at the cost of false alarms.
- Lookback window — how far back the comparison reaches. A long window reveals slow trends but can flag drift the environment has legitimately outgrown.
When it helps, and when it misleads¶
Its strength is temporal: it makes visible the one thing no in-the-moment mechanism can see — the slow slope where nothing is obviously wrong on any given day but the baseline has moved. It is the specific counter to normalization of deviance, in which a repeatedly-tolerated departure from standard becomes the accepted standard until an accident reveals it.[n1]
It misleads when it is mistaken for enough. A review only detects; if nothing downstream re-tightens the norm, it becomes an elegant record of decline. A subtler error is treating any change in the baseline as drift-to-be-corrected — sometimes the lived norm has adapted correctly to a changed environment and the documented norm is the stale one. The guarding discipline is to pair each finding with a decision about which way the correction should run — restore the old norm, or update the intended one — and to route findings to a mechanism that can actually act, since the review itself changes nothing.
How it implements the components¶
norm_drift_monitor— its core function: the periodic detector that surfaces where a norm is eroding before the erosion becomes a failure.current_norm_diagnosis— each review re-reads what the group now treats as normal, producing a fresh diagnosis of the lived norm rather than relying on the original one.
It sees slowly and after the fact, which separates it from its nearest twin, Peer Reinforcement Protocol, whose corrective loop (behavior_feedback_loop) fires in the moment. And it only diagnoses — it neither defines the standard it measures against (target_norm) nor re-tightens it (reinforcement_channel); those belong to Values-to-Behavior Translation and the reinforcement mechanisms.
Related¶
- Instantiates: Norm Shaping — supplies the drift-detection layer that keeps a shaped norm from quietly rotting after it is established.
- Sibling mechanisms: Values-to-Behavior Translation · Behavior Default Design · Leadership Modeling · Peer Reinforcement Protocol · Recognition System · Stories and Symbols · Culture Ritual · Norm Audit · Onboarding Norm Translation
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Norm Drift Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it a recurring backward look that re-diagnoses what the group now treats as normal and flags where tolerated exceptions have quietly hardened into the new default.
Independent corroboration: The frozen evidence defines Norm Drift Review as 'A recurring backward look that re-diagnoses what the group now treats as normal and flags where tolerated exceptions have quietly hardened into the new default', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Sociology & Anthropology
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Sociology of organizations explains how repeated tolerated exceptions become normalized and redefine what members perceive as ordinary.
Related originating lineages:
- Engineering & Design — Safety engineering turned normalization of deviance into a recurring comparison against an explicit baseline.
- Organizational & Management Science — Governance practice contributed scheduled review, ownership, and corrective revision of working norms.
Review resolution: Both independent reviews agree on primary origin sociology_anthropology; reconciliation resolves alternate_origin_disagreement. Formative alternate lineages retained: engineering_design, organizational_management. The broader reach of later applications is kept separate as domain_reach=multi_domain; origin_mode=cross_disciplinary_synthesis describes the historical relationship among lineages. Confidence is conservatively reconciled to high, and encyclopedia_synthesis=true preserves the reviewers' boundary judgment.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
Norm Audit and this mechanism both diagnose the lived norm, but on different clocks: an audit is the baseline read that establishes where things stand at a point in time, while Norm Drift Review is the recurring re-read whose whole value is the comparison to prior baselines. Use the audit to start; use the review to keep watch.
[n1] Normalization of deviance — Diane Vaughan's term (from her study of the Challenger launch decision) for the process by which a group repeatedly accepts a departure from a safety standard until the departure itself becomes the accepted standard. A periodic drift review is a deliberate counter: it re-reads the baseline precisely because participants inside the drift cannot feel it moving. ↩