8 tests from Episode 9 with Corrie Pitzer

In Episode 9 of Headline Podcast, published on November 6, 2025, Corrie Pitzer joined Andreza Araujo and Dr. Megan Tranter to discuss risk competence, control dependence, and why ordinary work can hide serious exposure. His central thesis was that people lose risk awareness when controls, metrics, and routines make a dangerous situation look normal.

This article turns that conversation into 8 field tests EHS managers and supervisors can use to find normal-work risk before the next event proves the pattern was never normal.

Why normal work is the hardest risk to see

Normal work is hard to see because repetition turns exposure into background noise. A task that has been completed 300 times without injury may still depend on a thin control, a careful operator, a favorable sequence, or a lucky absence of simultaneous work. The absence of harm proves less than leaders want it to prove.

Corrie Pitzer captured the discipline in one sentence on Headline Podcast: "Safety is the readiness to respond to risks relentlessly." The value of that sentence is that readiness can be tested before an incident, while luck can only be recognized afterward.

OSHA's recommended practices for safety and health programs organize prevention around management leadership, worker participation, hazard identification, hazard prevention and control, education, evaluation, and communication. Those elements only work if the organization still sees hazards after the work has become familiar.

Andreza Araujo's work across 250+ cultural transformation projects points to the same problem from the leadership side. Culture is not revealed by what people say about risk in a workshop. It is revealed by what supervisors ask when the field appears quiet, which is exactly where normal-work risk hides.

Test 1: Ask what would fail if the alarm stayed silent

The first test asks whether the crew can explain what would happen if the expected warning failed, because over-reliance on alarms and devices can weaken direct risk perception. If the only answer is that the alarm would tell us, the team may be depending on a control without understanding the exposure it monitors.

This matters in gas detection, proximity warning, interlock monitoring, fatigue systems, permit software, vehicle telematics, and machine guarding. Technology can strengthen control, although it can also move attention away from the work face when leaders treat alerts as the primary source of truth.

The supervisor should ask three field questions before work starts. What tells us this condition is becoming unsafe before the alarm activates? What action do we take if the alarm is unavailable? Who has authority to stop the task if the digital signal and the worker's judgment disagree?

That test connects directly with Headline's article on control automation and risk awareness. The issue is not whether automation is good or bad. The issue is whether automation has made the human system sharper or more passive.

Test 2: Look for the task everyone calls routine

The second test starts with language, because the word routine often means the risk has stopped receiving attention. Routine chemical transfers, routine lifting, routine confined-space checks, routine maintenance starts, and routine line breaks all deserve suspicion when the consequence is severe.

A supervisor can run this test in 10 minutes. Ask workers which task they no longer discuss because everyone knows how it is done. Then ask which part of that task would injure someone if timing, weather, staffing, isolation, traffic, visibility, or equipment condition changed. The answer usually reveals the real risk conversation.

ISO 31000:2018 describes risk management as guidance that can be customized to organizations and their decisions. In field safety, that customization has to reach the repeated job, because the generic risk register often stays too far away from the moment where exposure changes.

Andreza Araujo's book Safety Culture: From Theory to Practice is useful here because culture is not a slogan around values. It is the repeated operating choice. If a serious hazard is labeled routine, the culture has probably accepted familiarity as evidence.

Test 3: Walk the recovery path, not only the control path

The third test asks whether the team knows how to recover when a control weakens. A permit, barrier, lock, detector, guard, procedure, spotter, or exclusion zone may be present at the start of the task, but serious events often develop when one layer degrades and nobody knows the recovery rule.

Ask the crew to walk the recovery path out loud. If the barricade is moved, who stops the job? If the isolation point cannot be verified, who reauthorizes work? If the spotter leaves for 5 minutes, what happens to the task? If the worker sees a condition outside the permit, who owns the decision?

This is where risk competence becomes visible. A team that can name the recovery path understands the control's purpose. A team that only says we call EHS may understand the procedure but not the operating boundary, which is a weaker form of safety.

Use the Headline guide on critical control verification as the management layer, then add this recovery test at the task layer. Verification should prove not only that controls exist, but that people know what to do when controls stop behaving as expected.

Test 4: Check whether metrics have trained people to relax

The fourth test asks whether good numbers have reduced concern faster than exposure has reduced. Low injury rates, long no-lost-time streaks, and clean audit scores can make leaders confident while serious controls are aging, bypassed, misunderstood, or untested.

Episode 9 is especially useful because Corrie Pitzer challenged the habit of proving safety through the absence of accidents. Absence data can be comforting, but it is thin evidence when the organization has not tested whether high-consequence controls are healthy today.

The field test is practical. Pick one site with strong injury numbers and ask for evidence on 5 controls tied to serious exposure. Look for verification quality, closeout age, worker understanding, failure response, and supervisor authority. If the numbers look better than the controls, the dashboard is late.

Headline has already developed this issue in control health versus TRIR and SIF exposure. Corrie's episode adds the behavioral layer, because workers also learn from metrics. When leaders celebrate quiet numbers too loudly, people may stop looking for the weak signal.

Test 5: Ask workers where the rule and the work disagree

The fifth test asks workers to identify the place where the procedure and actual work no longer match. This question is not an invitation to ignore rules. It is a way to find design, planning, resource, and sequencing problems before the gap becomes an incident narrative.

James Reason's work on latent failures helps explain why this test matters. The visible act near the hazard is often shaped by older decisions about equipment, staffing, maintenance, supervision, layout, training, or production pressure. When the procedure does not fit the job, workers either adapt silently or stop the work, and culture decides which one feels safer.

The supervisor should ask the question without threat. Where do we have to adjust the method to get the job done? Which step is hardest to follow when production is behind? Which control looks good in the document but weak in the field? The answer should trigger correction, not punishment.

Andreza Araujo often frames this as the difference between compliance appearance and operational truth. In The Illusion of Compliance, the central warning is that documented control can look complete while work still depends on informal adaptation that nobody has authorized or improved.

Test 6: Separate confidence from competence

The sixth test asks whether the most confident person in the task is also the most competent person to judge risk. Familiarity creates useful pattern recognition, but it can also create overconfidence, especially when a worker has repeated the same exposure for years without visible consequence.

The field conversation should avoid insulting experience. Ask experienced workers what would make this job different today. Ask newer workers what does not make sense yet. Ask contractors what they see here that differs from other sites. Risk competence improves when different forms of knowledge are allowed to challenge each other.

NIOSH's hierarchy applied to Total Worker Health emphasizes organizational-level interventions to protect safety, health, and well-being. That principle matters here because competence is not only an individual trait. The work system must give people time, authority, and psychological safety to use what they know.

The Headline article on a 10-minute pre-task risk check gives supervisors a simple structure for this conversation. The point is not to make the briefing longer. The point is to make confidence earn its place through evidence.

Test 7: Review the moment after a small deviation

The seventh test studies what happens after a small deviation, because the organization's response teaches the next crew what kind of truth is welcome. If a minor bypass, late stop, missing barricade, weak handover, or incomplete isolation is treated as paperwork, the next deviation may travel farther.

This test should be run within 24 hours of the deviation. Ask what changed, who noticed, who acted, how quickly the condition was corrected, and whether the same weakness exists elsewhere. The review should be short enough to happen while memory is fresh and serious enough to change a control.

The trap is to wait for a recordable injury before learning. Small deviations are often the only affordable warnings the organization receives. They deserve better treatment than an email reminder or a toolbox talk that repeats the rule without changing the condition.

For adjacent practice, use the Headline article on safety margin and operating boundaries. A deviation matters because it shows the margin moving, even when nobody has been hurt yet.

Test 8: Make the stop-work decision nameable

The eighth test asks whether everyone can name who stops the work, who supports the stop, and who resolves the conflict when risk and production disagree. Stop-work authority is often declared broadly, but normal-work risk survives when the social cost of using that authority is too high.

Ask the crew to answer one concrete scenario. If the work package says proceed, the supervisor wants the job finished, and the worker sees a changed condition, what happens next? If the answer depends on personality, the control is weak. If the answer names a person, time limit, escalation route, and restart rule, the system is stronger.

This is where Corrie Pitzer's risk-competence lens meets Andreza Araujo's leadership work. Leaders cannot outsource risk awareness to frontline courage. They have to build the decision path that makes a truthful stop possible before the situation asks one worker to carry the entire burden.

Connect this test with risk matrix distortions, because matrix scores often feel objective while the real field decision remains unresolved. The question is not only how the risk was rated. The question is who acts when the rating no longer matches the work.

FAQ

What is the main lesson from Episode 9 with Corrie Pitzer?

The main lesson is that risk competence means seeing danger inside familiar work. Episode 9 warns leaders not to confuse repeated success, quiet metrics, or installed controls with real readiness to recognize and respond to changing exposure.

How can supervisors test risk awareness before work starts?

Supervisors can ask what would fail if a control disappeared, which part of the job is called routine, what recovery path exists when a control weakens, and who can stop the task when conditions change.

Why are good safety metrics sometimes misleading?

Good safety metrics can be misleading when they describe injury absence rather than control quality. A site can have low recordable rates while serious controls are unverified, misunderstood, bypassed, or dependent on informal adaptation.

What is normal-work risk?

Normal-work risk is exposure hidden inside familiar tasks. It appears when crews, supervisors, and leaders stop questioning a job because it has been completed many times without harm, even though the control path remains fragile.

How does this article differ from a risk assessment checklist?

A checklist verifies whether planned items are present. These 8 tests examine whether people still understand the exposure, recovery path, decision rights, and weak signals behind those items.

EHS managers should use Episode 9 as a field-audit prompt for one high-consequence routine task this week. Pick a task that looks stable, has repeated exposure, and depends on at least one critical control. Then run the 8 tests with the supervisor and crew before the next work cycle.

The strongest finding will probably not be a missing document. It will be a place where people trust a control without knowing its failure mode, call a task routine despite severe consequence, or rely on personal courage where the organization should have built a decision path.

Listen to the full conversation with Corrie Pitzer on Episode 9 of Headline Podcast, then compare the discussion with Headline's earlier companion on how Corrie Pitzer thinks about fatal risk. Together, the two pieces show why mature risk management has to protect both governance decisions and the field's ability to see normal work clearly.