You On AI Field Guide · The Reasonable Exception The You On AI Field Guide Home
Txt Low Med High
CONCEPT

The Reasonable Exception

The atomic unit of normalized deviance — the individually defensible judgment, supported by evidence and precedent, that is rational in isolation and catastrophic in aggregate because each exception is evaluated against the standard the previous exception has already revised.
Vaughan's framework identifies the reasonable exception as the mechanism by which normalized deviance is actually constructed at the level of individual decisions. Each exception is bounded, justified by specific circumstances, and supported by a growing evidence base. The person making the exception can point to data, to precedent, to a rational cost-benefit analysis. The exception is not a failure of judgment; it is an exercise of judgment within an institutional environment where the burden of proof falls asymmetrically on those who wish to stop rather than those who wish to proceed. The AI transition has generated reasonable exceptions at unprecedented pace and scale, each defensible in isolation, cumulatively reshaping what institutions consider adequate oversight.
The Reasonable Exception
The Reasonable Exception

In The You On AI Field Guide

The concept's power derives from its resistance to prevention through conventional means. Telling a competent professional that her reasonable judgment is wrong, when the accumulated evidence supports her position and the immediate cost of the alternative is visible while the risk of proceeding is speculative, is an act of organizational heroism that institutional structures rarely reward.

In the AI context, the reasonable exception appears in several distinct categories. The review exception emerges when AI-generated output is produced faster than it can be reviewed at the original depth, creating structural incentives to reduce review scope. The comprehension exception arises when practitioners evaluate AI output functionally rather than structurally, because evaluating the logic requires expertise they do not possess. The team-size exception follows when productivity multipliers shift the economic calculus of team composition. The expertise exception enables practitioners to operate in adjacent domains with AI assistance, trading domain judgment for tool competence.

Normalization of Deviance
Normalization of Deviance

Each exception rests on the previous ones. The manager who reduces team size has already inherited the reduced review depth and the comprehension gap. The smaller team reviews less carefully the code it already understands less deeply. The exceptions compound, and the accumulated weight produces a system functioning normally by standards the system has taught itself to apply.

The concept connects directly to production pressure: the reasonable exception is rational precisely because the institutional environment rewards proceeding and penalizes stopping, and the rationality is structural rather than personal. The individual making the exception is not miscalibrating; the institution has calibrated her.

Origin

The concept is implicit throughout Vaughan's Challenger research and was formalized in her subsequent theoretical work on organizational deviance. The precision of the concept — the exception as atomic unit, the chain as accumulated structure — derives from Vaughan's reconstruction of the twenty-four pre-Challenger flights and the specific engineering decisions made at each.

Key Ideas

Defensibility as the danger. The reasonable exception is dangerous precisely because it is defensible; exceptions that are indefensible can be addressed through conventional accountability mechanisms.

Production Pressure
Production Pressure

Asymmetric burden of proof. The party that wishes to proceed needs only to point to precedent; the party that wishes to stop must produce novel justifying evidence.

Compounding structure. Each exception rests on previous exceptions, producing a chain that no single correction can reverse.

Four categories in AI work. Review, comprehension, team size, and expertise — each generating exceptions that compound with the others.

Evidence grows with each iteration. The track record of successful exceptions provides empirical support for the next exception, making resistance progressively harder.

Further Reading

  1. Diane Vaughan, The Challenger Launch Decision (1996)
  2. Diane Vaughan, "The Dark Side of Organizations" (Annual Review of Sociology, 1999)
  3. Karl Weick and Kathleen Sutcliffe, Managing the Unexpected (2001)

Three Positions on The Reasonable Exception

From Chapter 15 — how the Boulder, the Believer, and the Beaver each read this concept
Boulder · Refusal
Han's diagnosis
The Boulder sees in The Reasonable Exception evidence of the pathology — that refusal, not adaptation, is the correct posture. The garden, the analog life, the smartphone that is not bought.
Believer · Flow
Riding the current
The Believer sees The Reasonable Exception as the river's direction — lean in. Trust that the technium, as Kevin Kelly argues, wants what life wants. Resistance is fear, not wisdom.
Beaver · Stewardship
Building dams
The Beaver sees The Reasonable Exception as an opportunity for construction. Neither refuse nor surrender — build the institutional, attentional, and craft governors that shape the river around the things worth preserving.

Read Chapter 15 in the book →

Explore more
Browse the full You On AI Field Guide — over 8,500 entries
← Home 0%
CONCEPT Book →