When Your Compass Is Off: Recognizing Drift in Your Child Protection Program
On July 17, 1938, pilot Douglas Corrigan took off from Brooklyn with a flight plan filed for California. He landed in Dublin, Ireland twenty-eight hours later and blamed a faulty compass. History remembers him fondly as “Wrong Way” Corrigan. Your organization’s child protection program will not earn that same fond memory if it drifts off course. Small, well-intentioned exceptions to your own child protection rules can accumulate quietly until the program you are actually running looks nothing like the policy you wrote. Researchers call this pattern normalization of deviance, and every youth-serving organization should learn to recognize it before it produces a preventable tragedy.
The Problem: Drift Doesn’t Announce Itself
Sociologist Diane Vaughan coined the term normalization of deviance studying the 1986 Space Shuttle Challenger disaster. NASA engineers watched the O-rings on the solid rocket boosters show damage on multiple flights before the disaster. Because the shuttle kept flying safely anyway, each instance of damage looked a little less alarming than the last. Engineers gradually redefined a known design flaw as an acceptable risk. A 2015 nursing journal article found the identical pattern in hospitals, where clinicians stop treating skipped safety checks as violations once nothing goes wrong for long enough. A 2022 review of research across aviation, manufacturing, and other high-risk fields confirmed that the pattern is consistent. A rule bends, nothing bad happens, and the bent rule becomes the new normal.
This is the uncomfortable part for organizational leaders. Nobody sits down and decides to lower a safety standard. The standard just moves, one small accommodation at a time, and the people making each individual accommodation usually believe they are being reasonable. Vaughan called the force behind that movement “production pressure.” At NASA it was launch schedules and funding. In a youth-serving organization it is a program that has to run tonight with the staff who actually showed up, not the staff the schedule called for.
Why This Risk Concentrates in Mission-Driven Organizations
Youth-serving organizations carry a specific version of this risk. Staff and volunteers join these programs because they care about the kids. That commitment is a genuine strength, and it is also exactly what makes drift harder to spot. A staff member who has given years of unpaid weekends to a program does not experience a shortcut as a shortcut. She experiences it as a caring person making a reasonable call in a hard moment. The identity of “someone who would never put a child at risk” makes it psychologically difficult to recognize a personal or organizational drift, because noticing the drift means questioning that identity.
This is not a character flaw specific to any one organization. It is a predictable feature of any group of well-intentioned people operating under real constraints. The organizations that manage the risk well are not the ones with the most sincere staff. They are the ones that built a system for catching drift instead of relying on staff members to catch it in themselves.
What Drift Looks Like in a Youth-Serving Organization
You will not find drift by rereading your policy manual. You find it by comparing your policy to what actually happens on a Tuesday afternoon when you are short-staffed. A background screening deadline set for a new volunteer’s first shift slides to “sometime in the first month.” A supervision ratio for a specific activity loosens because two staff members called in sick. A staff member’s habit of driving one child home alone, which started as a one-time favor, becomes a regular practice because nothing bad has happened yet.
None of these moments feels like a decision to put a child at risk. Each one feels like a reasonable response to a real scheduling problem. That is exactly why the pattern is dangerous. Deviance from your own rules normalizes precisely because it never announces itself as deviance.
The Penn State case remains the starkest documented example of what happens when this pattern runs for years without correction. A 2012 investigative report found that a 1998 report of a concerning incident involving a staff member and a child produced internal discussion but no referral to child welfare authorities. A witness saw a similar incident in 2000 and did not report it. A 2001 report of another incident led to a restriction on the staff member’s access to children, but not to a report to law enforcement or child welfare authorities. Fourteen years passed between the first documented warning sign and an arrest. Each individual decision along the way looked to the people making it like a judgment call. Viewed together, they show exactly how normalization of deviance operates over time.
The size of a program does not protect it from this pattern. Drift does not require a large bureaucracy or a chain of executives making calculated decisions. It requires only a rule, a shortcut, and enough time passing without consequence for the shortcut to start feeling normal. A camp with three staff members and a youth sports league with one coach are just as capable of drifting from a background check policy or a supervision rule as a large university athletic department. The scale of the organization changes how many people witness the drift. It does not change whether the drift happens.
How to Recognize and Correct Drift in Your Program
You do not need a scandal to find out whether your program has drifted. You need an honest audit and a habit of treating small exceptions as information rather than noise.
• Compare your written child protection policy against actual current practice at least once a year, not just the policy document against itself. Plan a day to walk your program and watch what staff actually do, not what the handbook says they do.
• Require a documented decision, made by a named person, any time a child protection rule gets an exception. An undocumented exception is far more dangerous than a documented one, because nobody has actually weighed the risk.
• Stop treating “nothing bad happened” as evidence that a practice is safe. It is exactly the absence of consequences that lets a bad practice feel normal. Ask staff directly what rules they have quietly stopped following and why, rather than waiting for an incident to surface the answer.
• Build a reporting path for small concerns that does not require staff to be certain something is wrong before they raise it. Most people will not report a hunch. They will report a documented near-miss if you give them an easy way to log one.
• When you find a drift pattern, fix it and write down what you fixed and when. A caught and corrected drift is a very different story than a drift nobody noticed, both for the children in your program and for how your organization can later demonstrate that it was paying attention.
Corrigan’s compass may or may not have actually failed. Historians still argue about it. Your organization will not get that same benefit of the doubt. If your program has drifted from your own written policy, the question that matters is not whether anyone meant for it to happen. The question is whether your organization was paying enough attention to notice, and whether it built a system that would have caught the drift before a child paid the price for it.
Want to go deeper? Creating a Just Safety Culture walks through how to build a culture where staff report small deviations before they become patterns, instead of normalizing them.
