← University
Process Failure and Control Breakdowns
0 of 6

A regional food processing company in southwestern Ontario had operated for more than 15 years with a reputation for reliable production and steady growth. The company employed approximately 120 workers across 2 facilities, processing locally sourced agricultural products for distribution to grocery chains and food service operators throughout central Canada. Its operations depended on a series of interconnected processes: receiving raw materials from suppliers, inspecting inputs for quality and safety, processing and packaging products according to food safety protocols, and coordinating logistics for time-sensitive deliveries.

The company maintained a documented food safety management system, including hazard analysis and critical control point protocols, sanitation schedules, temperature monitoring procedures, and equipment maintenance checklists. Supervisors were responsible for verifying that workers followed established procedures, and the quality assurance manager conducted periodic internal audits. On paper, the control framework appeared comprehensive. In practice, the gap between documented procedures and daily operations had widened over several years without anyone formally acknowledging the drift.

A series of events over an 8-month period brought these gaps into sharp focus. Production line workers had developed informal shortcuts to meet throughput targets during peak seasons, including bypassing certain sanitation steps when equipment appeared visually clean and deferring temperature log entries until the end of shifts rather than recording them at prescribed intervals. Supervisors, facing pressure to maintain output volumes, had tacitly accepted these deviations. When a new quality assurance coordinator raised concerns about inconsistencies between documented procedures and observed practices, the production manager dismissed the concerns as academic, noting that the company had never experienced a serious incident.

The situation changed when a routine inspection by a provincial food safety authority identified multiple non-conformities, including incomplete sanitation records, temperature logs with retroactive entries, and equipment maintenance deferrals that exceeded manufacturer specifications. The inspector issued a compliance order requiring corrective action within 45 days and indicated that further violations could result in licence suspension. Within weeks, the company also received notification from a major grocery chain customer that it was conducting its own supplier audit in response to the regulatory findings.

Senior management now faces urgent questions about how the company's control framework eroded, why deviations became normalized across multiple production teams, whether existing controls were ever validated for effectiveness, and how to rebuild both the operational risk record and the credibility of the company's food safety assurance to regulators and customers. The executive team includes the founder serving as chief executive, a chief operating officer responsible for both facilities, and a recently hired risk and compliance director whose mandate suddenly expanded from policy development to crisis response.

The Normalization of Deviance: How Unsafe Practices Become Standard

Every organization develops routines. Over time, workers discover shortcuts that save effort, supervisors accept minor deviations that appear harmless, and entire teams drift away from written procedures without anyone making a conscious decision to abandon the rules. This gradual process, through which risky practices become accepted as normal, represents one of the most insidious threats to operational integrity. The phenomenon has been studied extensively in high-consequence industries such as aviation and aerospace, but it operates with equal force in Canadian small businesses, non-profit organizations, healthcare facilities, construction firms, and professional service practices. Understanding how deviation becomes normalized is essential for any leader who wants to maintain effective controls and prevent the kind of catastrophic failures that seem inexplicable in hindsight but are entirely predictable when examined through the lens of organizational drift.

The concept of normalization of deviance was first articulated by sociologist Diane Vaughan in her analysis of the Space Shuttle Challenger disaster, but the underlying dynamic predates that terminology by decades. In essence, normalization of deviance describes a situation where individuals or groups repeatedly engage in practices that depart from established standards, and because no immediate negative consequences occur, the deviation comes to be seen as acceptable. The absence of visible harm creates a false sense of security. Each successful deviation reinforces the belief that the deviation is not actually risky. Over time, the deviant practice becomes the new baseline, and what was once recognized as a departure from the rules is now simply how things are done. This process is not driven by malice or deliberate risk-taking. It emerges from ordinary human psychology operating within organizational structures that fail to maintain vigilance against incremental erosion of standards.

Canadian workplace safety legislation across all jurisdictions imposes duties on employers and supervisors to ensure that work is performed in accordance with established safety procedures. The Canada Labour Code, which governs federally regulated industries, requires employers to ensure that the health and safety of every person employed is protected while they work. Provincial statutes such as the Occupational Health and Safety Act in Ontario, the Occupational Health and Safety Act in Alberta, the Workers Compensation Act in British Columbia, and the Act respecting occupational health and safety in Quebec all contain similar general duty provisions. As of the date of authorship, these statutes uniformly contemplate that employers will establish safe work procedures and ensure compliance with those procedures. The existence of documented procedures that are not actually followed creates a particular kind of legal exposure because it demonstrates both that the organization knew what safe practice required and that it failed to ensure that safe practice was maintained.

Beyond statutory obligations, Canadian organizations are subject to various industry-specific standards and frameworks that address the need for consistent adherence to established controls. ISO 31000, the international standard for risk management that has been adopted across Canadian industries, emphasizes the importance of maintaining controls and monitoring their effectiveness over time. The CSA Group publishes standards applicable to numerous Canadian sectors, and compliance with these standards often requires not just the existence of documented procedures but evidence of ongoing adherence. Professional regulatory bodies in fields such as accounting, engineering, medicine, and law impose similar expectations on their members. The consistent theme across all these frameworks is that the integrity of any control system depends on actual performance matching documented requirements. When a gap develops between what the procedures say and what people actually do, the control system has failed even if no harmful incident has yet occurred.

The practical mechanics of how deviation becomes normalized follow a predictable pattern that Canadian risk managers should learn to recognize. It typically begins with a single instance of departure from standard procedure. Perhaps a required step is skipped because of time pressure, or a piece of safety equipment is not used because it is uncomfortable, or a required review is bypassed because the usual reviewer is unavailable. If this initial deviation does not result in any visible harm, the individual who deviated learns that the procedure may not be as essential as the rulebook suggests. The next time similar circumstances arise, the threshold for deviation is lower. As more instances of deviation occur without consequence, the practice spreads to other workers who observe their colleagues taking shortcuts without suffering any negative outcomes. Supervisors who are aware of the deviations may choose not to intervene because they too have internalized the belief that the practice is not actually dangerous. Eventually, the deviation becomes so routine that new employees are trained informally to follow the deviant practice rather than the written procedure. At this point, the normalization is complete. The organization maintains documentation describing one set of practices while actually engaging in an entirely different set of practices.

Several organizational factors accelerate the normalization of deviance. Production pressure is perhaps the most significant contributor. When organizations face deadlines, financial constraints, or competitive pressures, there is a natural tendency to prioritize output over compliance with procedures that may slow production. Workers learn that management rewards results and tolerates minor procedural violations as long as work gets done. Another contributing factor is the invisibility of risk. Many procedural controls are designed to prevent low-probability but high-consequence events. Because the catastrophic outcome occurs infrequently, workers never experience the connection between the deviation and the harm it is meant to prevent. Instead, they experience only the immediate benefit of the shortcut and the absence of any immediate negative consequence. Social conformity also plays a role. Workers who observe their colleagues and supervisors engaging in deviant practices face pressure to conform to group norms rather than adhering to written procedures that the group has implicitly rejected. Speaking up about safety concerns in such an environment can feel uncomfortable or even career-limiting.

The phenomenon is particularly challenging to address because the very success of the deviation reinforces its continuation. Organizations that experience incidents or near-misses have an opportunity to recognize that their practices have drifted from safe standards. But organizations where normalized deviance has not yet resulted in a visible failure lack this feedback. They may believe their operations are functioning effectively precisely because no incidents have occurred, remaining unaware that they are accumulating latent risk that will eventually manifest in a failure. This creates a dangerous paradox where the appearance of safety coexists with the reality of degraded controls.

Consider the situation that developed at a mid-sized manufacturing operation in Hamilton. The company, which we will call Lakeside Fabrication, employed approximately seventy workers and produced metal components for the construction industry. When Lakeside first opened its facility in 2018, the company developed comprehensive lockout and tagout procedures for its machinery in accordance with Ontario's requirements for controlling hazardous energy. These procedures specified a detailed sequence of steps that workers were required to follow before performing any maintenance or repair work on equipment. The procedures required specific locks and tags to be applied to energy isolation points, verification that energy had been effectively isolated, and authorization from a qualified supervisor before work could commence. New employees received training on these procedures, and documentation was maintained showing that training had occurred.

Within the first year of operation, the procedures were followed carefully. Workers recognized the importance of lockout and tagout because the procedures were new and the training was fresh in their minds. Supervisors actively monitored compliance, and several workers were corrected when they attempted to take shortcuts. Over time, however, subtle drift began to occur. One experienced maintenance worker discovered that certain pieces of equipment could be put into a semi-dormant state using the control panel rather than going through the full isolation procedure at the electrical panel. This approach saved approximately fifteen minutes per intervention and did not require the worker to walk to a different part of the facility. The worker used this approach on several occasions without incident and mentioned it to colleagues. Within a few months, the informal practice had spread to most of the maintenance team. Supervisors were aware that workers were not always following the full lockout procedure but did not intervene because production targets were being met and no one had been injured.

By 2022, the deviation had become completely normalized. New workers joining the maintenance team were shown the abbreviated procedure by their experienced colleagues and were not corrected when they failed to follow the documented lockout protocol. The formal training program still covered the correct procedure, but workers quickly learned that actual practice differed from what they had been taught in training. Some workers had never performed a complete lockout following the documented steps. The original written procedures remained in the safety binder in the supervisor's office, but these documents bore little relationship to daily operations.

In October 2023, a maintenance technician was performing routine adjustments on a forming press. Following the usual informal practice, the technician had used the control panel to stop the machine but had not applied physical locks to the energy isolation points. Unbeknownst to the technician, another worker on the production floor accidentally activated the machine while the technician's arm was positioned within the operational envelope. The technician suffered severe crush injuries requiring multiple surgeries and resulting in permanent partial disability. The subsequent investigation by the provincial Ministry of Labour revealed the systematic gap between Lakeside's documented procedures and actual practice. The company faced prosecution for failing to ensure that workers complied with established safety procedures. Several supervisors faced personal liability as well because they had known about the deviant practices and had failed to correct them.

What the Lakeside situation reveals is how organizational obligations persist regardless of whether anyone has consciously decided to abandon them. The company had never made a deliberate choice to stop following lockout procedures. No manager had issued an instruction to skip required steps. The drift occurred gradually, invisibly, and without any single decision point that could later be identified as the moment when things went wrong. Yet the legal and practical obligations remained in place throughout this process. The existence of documented procedures that workers were not following actually worsened the organization's legal exposure because it demonstrated awareness of what safe practice required. The normalization of the deviation did not normalize the risk or the liability that came with it.

Several important implications follow from understanding how deviance becomes normalized. First, the mere existence of written procedures provides no protection if those procedures are not actually followed. Organizations cannot defend against regulatory action or civil liability by pointing to documentation if the documentation does not reflect reality. This means that compliance programs must include ongoing verification that practices match procedures, not merely confirmation that procedures exist. Second, the absence of incidents does not indicate the absence of risk. Organizations that have gone years without a serious failure may be running on luck rather than effective controls. Historical success provides no guarantee of future safety when that success has been achieved through practices that deviate from established standards. Third, production pressure and other organizational forces will naturally tend to erode procedural compliance over time unless active countermeasures are in place. Drift is the default condition. Maintaining alignment between practice and procedure requires continuous effort, not merely the initial establishment of appropriate controls.

For leaders seeking to prevent the normalization of deviance in their own organizations, several practical approaches are available. Regular verification of compliance is essential, but this verification must be designed to detect actual practices rather than merely collecting signatures on compliance checklists. Workers who have been engaging in deviant practices for months or years will readily sign attestations that they are following procedures because they no longer perceive their actual practices as deviations. Effective verification requires direct observation of work being performed, review of documentation created during the work process, and conversations with workers about how they actually complete their tasks. These observations should be conducted by individuals who understand the documented procedures and can recognize departures from them.

Creating an environment where workers feel safe reporting deviations without fear of punishment is equally important. Many workers are aware that actual practices differ from documented procedures, but they do not report these discrepancies because they fear discipline or believe that management implicitly approves of the shortcuts. When organizations respond to reports of deviation with punishment for the individuals involved rather than systemic analysis of why the deviation occurred, they drive the problem underground. Workers learn to hide deviations rather than surfacing them. A more effective approach involves treating reports of procedural gaps as valuable information about organizational vulnerabilities and responding with investigation and correction rather than blame.

Leaders should also examine their own behavior for signals that may inadvertently encourage deviation. If supervisors and managers praise workers for meeting production targets without asking how those targets were achieved, they communicate that results matter more than process. If leaders tolerate minor deviations because enforcing compliance seems petty or bureaucratic, they set a precedent that procedures are optional when circumstances seem to warrant flexibility. The organizational culture around procedural compliance is established through countless small interactions in which leaders either reinforce the importance of following established controls or signal that compliance is negotiable.

Documentation practices deserve particular attention. Organizations should ensure that their written procedures accurately reflect what good practice actually requires and that procedures are updated when legitimate improvements to work methods are identified. If workers have discovered a genuinely better way of accomplishing a task, the appropriate response is to evaluate that method, confirm that it meets safety and quality requirements, and update the documented procedure accordingly. This prevents the accumulation of gaps between formal procedures and actual practice while allowing the organization to benefit from worker innovation. What must be avoided is a situation where documented procedures become aspirational statements disconnected from operational reality.

Periodic review of procedures by individuals who were not involved in developing them can help identify requirements that may have become obsolete or impractical. Sometimes procedures are not followed because they are genuinely flawed, requiring steps that add no value or imposing requirements that cannot be met given available resources. Workers facing such procedures face a choice between violating the rules and failing to accomplish their assigned work. This creates conditions conducive to normalized deviance. Procedures should be designed with input from the workers who will be expected to follow them, should be tested to confirm they are practical, and should be revised when legitimate problems are identified.

Canadian organizations subject to internal audit requirements have an opportunity to use audit functions to detect normalized deviance before it results in failure. Auditors should be trained to look beyond documentary compliance to examine whether documented controls are actually functioning. This may require auditors to conduct interviews, observe operations directly, or perform testing that reveals actual practices rather than merely confirming that documents exist. The value of audit in detecting drift depends on auditors maintaining a skeptical perspective and not accepting surface-level compliance as evidence of effective controls.

The regulatory environment in Quebec warrants specific consideration given the civil law framework that governs obligations in that province. Under the Civil Code of Quebec, the general duty of care owed by employers includes an obligation to ensure the safety of persons in their employ through reasonable measures. This civil law standard applies alongside the province's occupational health and safety legislation and creates exposure for organizations whose actual practices diverge from reasonable safety standards, even if specific statutory requirements have not been violated. The extracontractual liability regime in Quebec means that injured parties may pursue claims against organizations based on general fault principles, and evidence that an organization tolerated normalized deviance in safety-critical areas would be highly relevant to establishing fault.

In federally regulated industries subject to the Canada Labour Code, internal responsibility system requirements expect employers and employees to work together to identify and resolve health and safety concerns. This collaborative model depends on accurate information about actual workplace practices being available to joint health and safety committees. When normalized deviance has created a gap between documented procedures and real practices, the information available to these committees may not reflect operational reality. Organizations should consider whether their internal responsibility system structures have access to accurate information about how work is actually performed, not merely how procedures say it should be performed.

The path forward for any organization concerned about normalized deviance begins with honest assessment. Leaders must be willing to ask whether their documented procedures accurately describe actual practice and to receive truthful answers to that question. This requires creating conditions where candor is rewarded rather than punished. It requires looking beyond compliance documentation to examine operational reality. It requires accepting that drift is a natural tendency requiring active countermeasures rather than something that happens only in negligent organizations. Most fundamentally, it requires understanding that the normalization of deviance is a process failure, not a personnel failure. Workers who have adapted to deviant practices are responding rationally to organizational incentives and constraints. Correcting normalized deviance requires changing those incentives and constraints, not merely disciplining the individuals whose behavior reflects them.

The consequences of allowing deviance to become normalized extend beyond regulatory penalties and civil liability, although those consequences alone should command attention. Organizations that tolerate degraded controls are accumulating risk that will eventually manifest in ways that may be difficult to predict or control. The specific incident that occurs may appear to be the result of bad luck or individual error, but the underlying conditions that made the incident possible will be traceable to the long process of drift that preceded it. Understanding normalization of deviance allows leaders to recognize this pattern and to intervene before accumulated risk converts to realized harm. The investment required to maintain alignment between documented procedures and actual practice is far smaller than the cost of responding to the failures that occur when this alignment is lost.

Continue with University access

This lesson is part of a $149 course. Purchase the course or sign in with an active membership to keep reading.

See purchase options