Lexicon › Governance and Accountability › Normalisation of Deviance

Governance and Accountability

Normalisation of Deviance

Theoretical Origin Vaughan, 1996 | The Challenger Launch Decision

Small departures from governance standards stop feeling like departures when nothing bad happens immediately. Over time, the exception becomes the practice and the original standard is quietly forgotten.

Definition


What is Normalisation of Deviance AI Governance Risk?

Normalisation of deviance is the gradual process by which departures from established standards come to be seen as acceptable. Each small deviation that passes without visible consequence makes the next deviation easier to accept. Standards drift without anyone deciding to lower them. The process is invisible from inside it precisely because it happens incrementally.

The mechanism is not negligence. Organisations normalise deviance because their experience genuinely shows that the deviation is safe, at least in the short term. Each instance of skipping a step, accepting a risk, or approving an exception without incident provides real evidence that the deviation is tolerable. That evidence accumulates and reshapes the organisation’s sense of normal.

The Gap Between Standards and Practice

What makes normalisation of deviance particularly difficult to govern is that it produces a gap between formal standards and actual practice that is invisible in documentation. Policies and procedures describe what should happen. Normalised deviance describes what does happen. The gap between them is real but unrecorded, and the people operating inside it often cannot see it clearly because their reference point for normal has shifted with the practice.

Research Origin


Vaughan (1996) developed the concept through her detailed sociological analysis of the Challenger Space Shuttle disaster. Engineers at NASA had known for years that O-ring seals performed poorly in cold temperatures. Each previous launch that did not fail despite this known risk had been treated as evidence that the risk was acceptable. Deviance from safe practice had normalised across a technically sophisticated organisation with strong safety culture and formal oversight processes. The disaster was the result not of ignorance but of accumulated tolerance.

Vaughan (1999) extended the analysis to organisations more broadly, arguing that the dark side of organisational life, including disasters, misconduct, and systematic failure, regularly emerges not from rogue actors but from the ordinary processes by which organisations adapt to their environments. Normalisation of deviance is a structural feature of complex organisations under pressure, not an exception.

Reason (1990) contributed the concept of latent failures: conditions that exist within a system long before they produce visible harm. Normalised deviations are latent failures. They accumulate silently until a triggering condition converts them into an active failure. By that point, the organisation has no reliable memory of the original standard.


In AI Contexts


How Normalisation of Deviance Shows Up With AI

AI tools enter organisations with governance intentions that are rarely fully implemented from the start. A review step gets skipped once because of a deadline. An approval process is bypassed because the AI output looks fine. A staff member uses a personal AI account because the organisational one is slow. Each of these is a small deviation. Each passes without visible consequence. Each makes the next deviation easier.

Speed as the Normalising Force

AI tools are fast. That speed creates constant pressure against governance steps that slow things down. Review processes, approval chains, and documentation requirements all compete with the immediate productivity benefit of using AI output directly. In that competition, governance loses incrementally. Each loss is small. Cumulatively, they produce an organisation whose actual AI practice bears little resemblance to its stated policy.

Why It Matters for Nonprofits


The Specific Risk for Community Organisations

Community organisations operate under sustained resource and time pressure. That pressure is the primary driver of normalisation of deviance in AI governance: not bad intent, but the entirely reasonable adaptation of stretched teams to competing demands. The governance step that gets skipped is the one that feels least urgent compared to the direct service need it competes with.

When the Standard Disappears

The Challenger parallel is worth holding directly: NASA had strong safety culture, technical expertise, formal oversight, and genuine commitment to safe practice. None of that prevented normalisation of deviance from producing catastrophic failure. Community organisations with less formal governance infrastructure and greater operational pressure face the same dynamic at smaller scale but with equivalent consequences for the communities they serve.

Governance reviews and audits that compare current practice to policy documentation will not detect normalisation of deviance. The policy is unchanged. Only practice has drifted. Detecting this requires asking what actually happens, not what the policy says should happen, and being prepared for a significant gap between the two answers.

Observable Signals


What to Watch For

These patterns suggest normalisation of deviance may be reshaping AI governance practice in your organisation. They are signals worth naming and discussing, not a definitive checklist.

  • Staff describe current AI practice using phrases like “we used to” or “technically we should” when referring to governance steps, indicating awareness that practice has drifted from policy without a formal decision to change it.
  • Exceptions to AI governance procedures are granted regularly and without formal review, suggesting exception has become the operating norm rather than a genuine departure from it.
  • New staff learn AI practice from observing colleagues rather than from policy documentation, meaning they are learning the normalised version rather than the intended standard.

External References


  • Vaughan, D. (1996). The Challenger Launch Decision: Risky Technology, Culture, and Deviance at NASA. University of Chicago Press.
  • Vaughan, D. (1999). The dark side of organisations: Mistake, misconduct and disaster. Annual Review of Sociology, 25, 271-305.
  • Reason, J. (1990). Human Error. Cambridge University Press.

From theory to practice


Understanding the risk is the first step.

The NFH Toolkit gives your organisation practical tools to detect the gap between stated AI policy and actual practice, before that gap becomes a governance failure. The Behaviour Risk Cards name this pattern in language your whole team can use.

Not For Humans: Because AI’s greatest risk isn’t technical, it’s Human.