top of page

Normalization of Deviance: When “Normal” Becomes the Risk

2 hours ago
5 min read

Last week, I was watching a YouTube video on skydiving. It discussed how we can overlook small process deviations when there is no consequence and how they can become the new normal- this is something that we always talked about in aviation that translates surprisingly well into HR: Normalization of deviance.


Unlike the examples we tend to hear about in aviation (or skydiving), it doesn't have to end in catastrophe to matter.


Normalization of deviance

What Is Normalization of Deviance?

Safety conversations frequently focus on the small decisions that gradually move us away from an established standard. Someone takes a shortcut and othing bad happens. They take the shortcut again, still nothing happens. Eventually, the shortcut doesn't even feel like a shortcut anymore- it simply becomes the way we do things.


That's normalization of deviance.


The danger isn't necessarily one person intentionally deciding to ignore a rule, it's that repeated success despite ignoring the rule begins to convince us that the rule wasn't really necessary in the first place. We confuse the absence of a bad outcome with evidence that the practice is safe and that distinction matters tremendously.


It Happens in HR, Too

When we talk about normalization of deviance, our minds often go to industries where deviations can have catastrophic consequences: aviation, healthcare, nuclear power, manufacturing or workplace safety. However, I've spent enough time in HR to recognize the same pattern- it just sounds a little different.

"We don't really document those conversations."
"They usually work through lunch. They don't mind."
"Technically managers are supposed to approve that first."
"We've always classified that position as exempt."
"Everyone shares that login."
"We haven't updated the handbook in years, but we've never had a problem."
"That's not exactly what the policy says, but this is how we've always done it."

None of those statements necessarily signals an impending catastrophe but they should make us curious. Somewhere along the way, there may have been a gap between the established standard and the actual practice and over time, everyone stopped seeing the gap.


“Nothing Happened” Is Powerful Reinforcement

This is where normalization of deviance gets interesting from a human behavior perspective.

Imagine an organization requires managers to document employee coaching conversations.

A supervisor gets busy and doesn't document one, nothing happens, then another, nothing happens. Eventually the supervisor stops documenting most informal coaching conversations. Other supervisors see the same thing and since leadership hasn't raised concerns, six months later, not documenting isn't perceived as breaking procedure- It has become the procedure.


Then an employee relations issue occurs. Suddenly everyone is asking:"Where is the documentation?" The organization may view that moment as an individual supervisor failure.

But that's probably the wrong question, a better question is: How did our system allow this practice to become normal? That is where I think normalization of deviance and Just Culture belong in the same conversation.


Before You Blame the Employee, Look at the System

One of the things I appreciate about a Just Culture approach is that it asks us to look beyond the outcome. Suppose an employee skips a required step, our instinct might be:

They didn't follow procedure. True, but I'd want to know more.

  • Did other employees skip it too?

  • Did the supervisor know?

  • Has leadership observed the practice?

  • Did someone train the employee to do it this way?

  • Does following the official procedure actually make the job unnecessarily difficult?

  • Has the organization routinely rewarded speed or productivity while quietly tolerating shortcuts necessary to achieve those expectations?

  • And perhaps most importantly: When people deviated from the process previously, what happened?

If the answer is nothing, we've learned something important. The organization may have unintentionally taught employees that the deviation is acceptable. That's very different from an employee knowingly disregarding a well-understood, consistently enforced expectation.


HR Has Its Own Version of Safety Drift

Think about how easily these things can develop.

  • A company requires employees to record all hours worked, but managers routinely answer emails after hours.

  • A meal-period procedure exists, but everyone knows staffing rarely allows employees to take uninterrupted breaks.

  • Performance conversations are supposed to be documented, but supervisors are uncomfortable doing it and HR hasn't pushed the issue.

  • Job descriptions haven't been reviewed in years, even though positions have evolved dramatically.

  • A temporary workaround introduced during a staffing shortage quietly becomes permanent.

  • An employee has access to something they technically shouldn't, but removing access would make someone's job more difficult.


Individually, these can seem small, collectively, they tell you something about the organization: The written system and the operating system are no longer the same and that gap is where risk grows.


The Most Dangerous Phrase Might Be “We've Never Had a Problem”

When I hear:

"We've done it this way for years and we've never had a problem."

my aviation brain wakes up because years without an incident don't necessarily prove that something is working. Sometimes they simply mean the conditions haven't lined up yet for the weakness to matter. HR has plenty of examples:

  • An improperly classified employee doesn't make the classification correct because nobody has filed a wage claim.

  • An inconsistently applied policy isn't suddenly consistent because nobody has challenged it.

  • Poor documentation doesn't become good practice because you've never been sued.

  • And relying entirely on one person, one vendor, one software system or one undocumented process doesn't become a continuity plan because it has always worked before.


Sometimes"we've never had a problem" is reassurance, sometimes it's a warning sign. Good leadership knows enough to ask which one it is.


So How Do You Spot Normalization of Deviance?

I think leaders and HR professionals can start with five questions:


1. What does the policy or procedure say?


2. What do people actually do?

If those answers are different, don't immediately assume employees are the problem.

Keep going.


3. How long have we been doing it this way?

You're trying to determine whether you're looking at an isolated decision or an organizational norm.


4. Why does the deviation exist?

Maybe someone took an inappropriate shortcut, but perhaps the official procedure is confusing, outdated, inefficient or impossible given current staffing and resources.

That's important information, too.


5. What have we unintentionally reinforced?

Organizations teach through more than policies. We teach through what supervisors tolerate. We teach through what leaders model. We teach through what we reward. We teach through what we repeatedly see and choose not to address.


The Goal Isn't Zero Deviation

This is another lesson I carry with me from aviation into HR. The answer isn't necessarily writing more policies or punishing every person who deviates from a process. Organizations change, jobs evolve, technology changes. Sometimes employees develop a better way of doing something. The goal should be to understand why actual practice has drifted from expected practice. Maybe employees need retraining, maybe managers need better accountability, maybe staffing needs to change, maybe a control truly is necessary and needs to be reinforced, or maybe everyone is circumventing a five-year-old procedure because the procedure itself needs to change.


Deviation is information, good organizations investigate it before deciding what it means.


Pay Attention to the Little Things

Last week, thousands of organizations had to think about Microsoft infrastructure because suddenly they couldn't take it for granted. The outage disrupted essential workplace functions such as email, calendars and virtual meetings.


Most days, we don't question the systems that appear to be working and that's exactly why normalization of deviance is worth talking about outside aviation. The biggest organizational risks don't always announce themselves dramatically.


Sometimes they sound like:

"Just this once."


Then:

"We've done it before."


Then:

"Everybody does it."


And eventually:

"That's just how we do things here."


Maybe one of the best things HR and leadership can do is occasionally stop and ask:

Is this actually how we should be doing it, or have we simply gotten comfortable because nothing bad has happened yet?


That is a question worth asking before something gives you a reason to.


Comments


bottom of page