5 questions from Episode 9 with Corrie Pitzer

Episode 9 of Headline Podcast, published on November 6, 2025, brought Corrie Pitzer of Safemap into conversation with Andreza Araujo and Dr. Megan Tranter. The central thesis is that risk competence fails when controls make dangerous work feel ordinary and leaders stop testing whether people still recognize exposure.

Risk competence is the ability to recognize, interpret and respond to changing exposure before a serious event proves the system was weaker than assumed. In Episode 9, Corrie Pitzer frames it as a leadership problem because risk can become invisible after procedures, alarms and dashboards make work feel controlled.

1. What does risk competence ask leaders to see?

Risk competence asks leaders to see whether people can still recognize exposure when work looks normal, especially in high-risk tasks where one missed weak signal can defeat several layers of control. Episode 9 matters because Pitzer does not treat risk as a paperwork category. He treats it as a live capacity that must be tested in the field.

As Pitzer put it on Headline Podcast, "Safety is the readiness to respond to risks relentlessly." That sentence is useful because it moves the discussion away from injury absence and toward readiness. A plant can complete 90 days without a recordable injury and still lose the practical ability to notice drift in a lifting plan, energy isolation, pedestrian route or pressure-test boundary.

OSHA describes safety and health programs through management leadership, worker participation, hazard identification, prevention, training, evaluation and coordination. Those 7 program elements only work when leaders ask whether workers can describe the risk in front of them, not only whether they can recite the rule.

This is why the episode belongs in risk management rather than motivational safety leadership. The leadership test is concrete: can a supervisor, technician and EHS manager explain what would make today's task unsafe enough to pause?

2. When do controls make people stop looking?

Controls make people stop looking when the organization treats the control as proof of safety instead of one barrier whose condition can decay. In Episode 9, Pitzer's warning is sharp because many mature organizations have the opposite problem from immature ones: they have more systems, more alarms and more metrics, yet less human curiosity around the work.

One quote from the episode captures the trap: "I put a control in place, the workers stopped looking and just waited for the alarm." That is not an argument against controls. It is an argument against control worship, where the presence of a tool quietly replaces the discipline of observation.

NIOSH explains the hierarchy of controls as 5 levels, from elimination and substitution through engineering controls, administrative controls and PPE. The hierarchy matters here because lower-level controls often demand more human attention, while leaders may behave as if installing any control has finished the risk conversation.

For related field practice, connect this episode with Headline's article on critical control verification. Verification is the antidote to false comfort because it asks whether the control is present, effective, understood and still matched to the exposure.

3. Why is absence of accidents a weak proof of safety?

Absence of accidents is weak proof of safety because rare catastrophic events can hide behind long quiet periods, especially when exposure is frequent but failure probability is low. Pitzer's whale analogy in Episode 9 attacks a common executive mistake: treating clean lagging indicators as evidence that the organization understands its serious-risk profile.

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." The point is methodological. A small sample of ordinary days cannot prove that a low-frequency, high-consequence event is impossible, which is why serious-risk governance needs exposure evidence, control evidence and dissent evidence.

ISO 31000 defines risk around the effect of uncertainty on objectives, and that emphasis on uncertainty is more useful than a narrow count of harm after the fact. If leaders wait for harm to validate uncertainty, they have already chosen a late indicator as their teacher.

Headline has already explored this in safety margin and operating boundaries. A healthy margin is not visible only after an event. It is visible when teams can say which assumptions would make today's work unsafe.

4. What should safety professionals translate for executives?

Safety professionals should translate the gap between executive control confidence and frontline risk recognition, because senior leaders often see dashboards while workers see tradeoffs, shortcuts and weak signals. Episode 9 is valuable for EHS managers because it makes translation a strategic role, not an administrative one.

Across 25+ years leading EHS in multinationals, co-host Andreza Araujo has repeatedly argued that safety culture appears in repeated decisions. In her book Safety Culture: From Theory to Practice, the useful question is not whether leaders value safety in speeches, but whether the daily decision system makes risk visible before the incident.

That translation should include 3 questions in every serious-risk review. What does the frontline believe can hurt someone today? Which critical control would fail first under pressure? Who has authority to stop the task if the answer is uncertain? If executives cannot hear those answers without defensiveness, the organization has a governance problem disguised as a communication issue.

The same logic connects to Headline's article on risk matrix distortions. A matrix can rank a hazard, but it cannot replace the field conversation where people test whether the ranking still matches the work.

5. How can leaders test risk competence in 30 days?

Leaders can test risk competence in 30 days by selecting 5 high-risk tasks and asking workers, supervisors and EHS staff the same exposure questions before, during and after the job. The purpose is not to quiz people. The purpose is to find where risk language, control evidence and decision authority stop lining up.

A practical 30-day review should include pre-job interviews, field observation, control verification, pause-point testing and an executive debrief. The strongest evidence is not a perfect answer in a meeting. It is the moment where a worker notices a weak signal and the supervisor treats that signal as useful information rather than delay.

5 tasks, 3 roles and 30 days are enough to expose whether risk competence is real or cosmetic. Start with non-routine work, stored energy, lifting, mobile equipment, confined spaces or contractor interfaces, because those settings often combine changing conditions with schedule pressure.

If the review reveals weak escalation, use Headline's guide on SIMOPS risk before shutdown work as a companion. Simultaneous operations expose whether people can see interface risk before the schedule turns it into conflict.

Comparison

Episode 9 creates a useful distinction between safety systems that document risk and safety systems that keep people competent to recognize risk. The difference becomes visible when leaders compare what the organization says it controls with what the field can still see, question and stop.

The table matters because it changes the proof leaders ask for. Documentation may show that a process exists, although risk competence shows whether people can still think inside that process when the work changes.

Each month without this test allows controls to become more familiar and less questioned, while leaders may confuse routine success with durable safety capacity.

Recommendation

Senior EHS leaders should treat Episode 9 as a prompt to audit whether controls are strengthening or replacing human risk recognition. Choose 5 high-risk tasks, run a 30-day review, and report 3 findings to the leadership team: where exposure was misunderstood, where controls created false confidence and where escalation rights were unclear.

BLS records fatal occupational injury data, and that public record should remind executives that serious outcomes rarely announce themselves through neat early metrics. OSHA forms, ISO 31000 language and control charts can all help, although none of them can substitute for leaders who ask better field questions.

Episode 9 with Corrie Pitzer gives risk managers a sharper way to discuss serious-risk prevention. Listen to the full conversation: Listen to the full conversation.