How Corrie Pitzer Thinks About Control Reliance

Episode 9 of Headline Podcast, published on November 6, 2025, featured Corrie Pitzer, CEO at Safemap, in conversation with Andreza Araujo and Dr. Megan Tranter. The central thesis he defended is that controls can reduce exposure and still weaken safe behavior when workers stop reading the risk in front of them.

Control reliance is the habit of treating a safety control as proof that risk no longer needs active attention. In high-risk work, it becomes dangerous when alarms, procedures, permits, barriers, or dashboards replace the frontline skill of noticing change, uncertainty, and weak signals.

Why does control reliance weaken safe behavior?

Control reliance weakens safe behavior because people adapt to the control after it becomes part of normal work. The first week after a new alarm, barrier, sensor, permit, or checklist is installed, attention is usually high. By week 30, the control may still exist while the mental model around it has changed.

On Headline Podcast, Corrie Pitzer said, "I put a control in place, the workers stopped looking and just waited for the alarm, I had turned them into potential victims of my own design." That observation is uncomfortable because it does not attack controls. It attacks the assumption that a control automatically preserves awareness after people learn to depend on it.

Across 25+ years of executive EHS work and more than 250 cultural transformation projects, Andreza Araujo has argued that safety culture lives in repeated decisions. A control that removes judgment from the field can create compliance while shrinking the very risk perception that keeps people alive when conditions change.

This is why the problem sits in safe behavior, not only in risk management. A supervisor should ask whether the crew can still describe the hazard, the control limit, the failure mode, and the stop condition without waiting for a device or form to tell them what to see.

What did Corrie Pitzer mean by risk competence?

Risk competence is the practical ability to recognize risk in situations that look normal. It differs from rule knowledge because a worker can know the rule and still miss the changing condition that makes the rule insufficient today.

On Headline Podcast, Corrie Pitzer said, "Safety is the readiness to respond to risks relentlessly, and the one word for that readiness is risk competence." The word readiness matters. It points to an active state, where people expect variation, read the work, and question whether the control still matches the exposure.

The Headline article on risk perception drift shows the same pattern from the supervisor side. People rarely lose risk awareness in one dramatic moment. They lose it through repeated uneventful work, weak feedback, and controls that appear reliable until the day they are not.

NIOSH describes 5 levels in the hierarchy of controls, from elimination through personal protective equipment. That model is useful, but Corrie's point adds a behavioral test: after a control is selected, can the team still notice when reality has moved outside the design assumption?

Where do controls create false confidence?

Controls create false confidence when leaders measure their presence instead of their behavior under pressure. A control can be installed, trained, inspected, and signed off while still failing to shape the decision that matters at the point of work.

The common examples are familiar: a gas detector that is treated as permission to enter, a permit that becomes a ritual before non-routine work, a machine guard that hides poor access design, or a dashboard that reassures leaders because no incident has been recorded in 90 days.

ISO positions ISO 45001:2018 around leadership, worker participation, planning, operation, performance evaluation, and improvement. Those 6 words should prevent control reliance from becoming passive. The system has to check whether the control still works in the work, not only whether it exists in the system.

Headline's guide to the field proof gap makes this practical. If a control cannot be proved in the field, with evidence another supervisor can verify later, leaders are managing a belief rather than a barrier.

Control reliance versus risk competence

Control reliance and risk competence differ in what they expect from the worker after the system is built. Control reliance asks the worker to trust the protection. Risk competence asks the worker to understand the protection well enough to notice when it no longer fits.

The table does not argue against controls. It argues against control worship. In Andreza Araujo's Safety Culture: From Theory to Practice, the useful culture question is not whether the organization can display a rule. It is whether people make safer decisions when the rule meets real work.

How should supervisors keep risk awareness alive?

Supervisors keep risk awareness alive by pairing every important control with a short recognition routine. Before high-risk work starts, the crew should name the hazard, the control, the control limit, the first sign of drift, and the condition that stops the job.

This routine can take 3 minutes, and it works because it forces people to explain the control instead of reciting it. A permit for confined space entry is not enough if the attendant cannot explain atmosphere limits, ventilation dependence, rescue trigger, communication loss, and the moment entry stops.

The same discipline applies to behavior programs. A behavioral observation loop should not only count observations. It should ask whether the observation changed a condition, clarified a control limit, or revealed a trap the crew had normalized.

OSHA organizes recommended practices around 7 core elements, including management leadership, worker participation, hazard identification, and program evaluation. Corrie's episode translates those elements into a field question: do workers still recognize risk before the system labels it for them?

What traps do leaders minimize?

Leaders often minimize 3 traps. The first is training drift, where people remember the control name but forget the harm pathway. The second is metric comfort, where leaders accept clean reports as proof. The third is automation dependence, where the crew waits for the device instead of reading the work.

On Headline Podcast, Corrie Pitzer said, "You can send a thousand people out with buckets of seawater for a thousand years and prove there are no whales in the ocean, that's how we try to measure safety by the absence of accidents." The number is memorable because it exposes the danger of absence-based proof.

That warning connects with control health, TRIR, and SIF exposure. A low injury rate can coexist with weak control knowledge, bypass habits, and poor recognition of serious exposure. Leaders need the discipline to inspect the behavior around the control, not only the record after the work.

Every month that a site celebrates quiet numbers without testing recognition, escalation, and control limits teaches people that the absence of bad news is stronger evidence than the condition in front of them.

Recommendation

The recommendation is to audit the next 30 days of high-risk work for control reliance. Pick 5 critical controls, then ask supervisors to collect 3 pieces of evidence for each one: whether the crew can name the hazard, whether they can name the control limit, and whether they know the stop condition.

Start where the organization already has strong paperwork, because that is where control reliance hides most easily. Permits, gas tests, lockout tagout, machine guarding, traffic separation, and emergency response drills can all look mature while the crew's risk recognition has gone quiet.

Review the evidence with operations, not only EHS. If workers can use the control but cannot explain its failure mode, the next action is not another poster. It is redesign, supervisor coaching, field verification, or a clearer stop rule before the next exposure repeats.

Close the review by asking whether the control changed the work or only changed the paperwork around the work. That distinction matters because safe behavior improves when the crew can see why the control exists, where it can fail, and who has authority to stop when the work no longer matches the assumption.

Final note

Corrie Pitzer's episode matters because it separates control from competence. A control can be necessary and still become dangerous when it teaches people to stop looking.

Safe behavior improves when leaders preserve the worker's ability to read risk, challenge the control, and stop work before the system has to prove failure through harm. Listen to the full conversation: Listen to the full conversation.