How Corrie Pitzer Thinks About Risk Competence Before Controls Create Blindness

Episode 9 of the Headline Podcast, published on November 6, 2025, put a difficult question in front of safety leaders by asking what happens when a control reduces exposure but also reduces attention.

Corrie Pitzer argued that the answer begins with risk competence, the readiness to recognize and respond to risk relentlessly, because serious exposure often arrives inside work that looks ordinary, familiar, and already controlled.

Risk competence starts before the checklist

Pitzer's definition is deliberately active. He did not describe safety as the condition of having enough procedures, alarms, or training records. He described it as readiness, which means that people must keep noticing what is changing and decide what deserves a response.

On the show, Pitzer said, "Safety is the readiness to respond to risks relentlessly, and the one word for that readiness is risk competence." The phrase shifts attention from possession to performance. A site may possess a risk register, a barrier standard, and a competent-person program, yet still fail if workers cannot recognize when the assumptions behind those controls no longer hold.

This is why the first question in a field review should not be whether the team followed the expected sequence. It should be whether the team could identify the condition that made the expected sequence less reliable, and whether someone had the authority to change the plan.

The distinction is practical. A checklist records what was considered. Risk competence shows whether the consideration remained alive when the work met pressure, variation, or an unexpected interaction.

Normal work can conceal a changing risk profile

Familiarity is useful because it lets people coordinate without rebuilding the task from the beginning. Familiarity becomes dangerous when it is mistaken for evidence that the exposure is stable, especially where weather, staffing, equipment condition, workload, or simultaneous operations can shift the situation.

A routine transfer, inspection, maintenance job, or vehicle movement may look identical to yesterday's work while one assumption has quietly changed. The person who normally confirms the isolation is absent. A temporary barrier has moved. The contractor has interpreted the handover differently. A production demand has shortened the time available for verification.

None of those changes needs to produce an immediate near miss. That is what makes them difficult to manage. The absence of an event can leave the organization believing that the control worked, even when the team succeeded through improvisation or luck.

Leaders can make normal work more visible by asking workers to identify the part of today's task that is least like the last one. The question is simple, but it makes variation discussable without requiring anyone to claim that the whole procedure is defective.

Controls should support attention, not replace it

Controls are necessary, but their presence can change behavior in ways that leaders do not measure. Pitzer explained that when a control is installed, workers may stop looking and wait for the alarm. The protection then becomes a reason to suspend observation rather than a support for it.

His warning was direct: "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." The point is not that alarms or engineered safeguards are wrong. The point is that every control creates a new relationship between the person, the task, and the signal.

A leader should therefore test two separate questions. First, does the control reduce the intended exposure under its design conditions? Second, does the control preserve the team's ability to notice conditions that sit outside those design conditions?

The second question is often absent from assurance work. It can be added through field observation, short scenario tests, and handovers that ask what the control cannot detect. A control that answers one hazard should not be allowed to become an answer for every hazard.

Six lenses widen the search for risk

Pitzer brought six lenses of risk discovery into the conversation. The value of the lenses is not a memorized model. Their value is that they prevent a review from stopping at the first explanation that feels familiar.

The six lenses also give safety professionals a translation role. Frontline workers often see fragments of a risk, while managers need a decision that connects those fragments to resources, timing, and authority. Translation is not simplification. It is the disciplined act of preserving the concern while making its consequence understandable to the person who can act.

A useful meeting exercise is to give each lens to a different participant before the work begins. The maintenance lead can test the control, the supervisor can examine the change, and the operator can describe the actual task, while a manager listens for a consequence that the schedule or budget has made easy to ignore. The exercise takes less than 15 minutes when the task is familiar, but it makes the quality of the conversation visible because each person has to contribute a different kind of evidence.

That work resembles the decision trail described in our risk communication guide, where the quality of a warning depends on whether its meaning survives the route to action.

Risk competence is different from control confidence

Control confidence asks whether a barrier is present and apparently available. Risk competence asks whether people can recognize when the barrier is not enough, is being bypassed, or is operating under different conditions from the ones used in its design.

Those are related but different capabilities. A team can report high confidence in a permit system while missing a changed interface between maintenance and operations. A site can complete a verification form while failing to challenge the assumption that the equipment will remain isolated throughout the job.

The distinction can be made visible in a short review. Ask the team to name the primary control, the condition it depends on, the signal that would show degradation, and the decision that follows. If people can name only the control, the organization has a confidence statement, not yet a risk-response capability.

Our companion article on control confidence develops that separation further. The practical benefit is that leaders stop treating a signed assurance as proof that the exposure has disappeared.

Absence of accidents is a weak measure of readiness

Pitzer used an image that challenges the way many organizations interpret quiet performance. He said that sending 1,000 people out with buckets of seawater for 1,000 years would prove there are no whales in the ocean, which is how organizations can try to measure safety by the absence of accidents.

The comparison does not dismiss outcome data. Injuries, releases, and damage still matter, and leaders must respond to them. The problem appears when a favorable outcome is treated as evidence that the system recognized every important risk along the way.

A better question is whether the organization can show the decisions that produced the favorable outcome. Did workers identify a weak signal? Did a supervisor alter the work plan? Did a control owner verify the condition at the point of use? Did the team escalate uncertainty before the schedule made escalation expensive?

This shifts measurement toward readiness. It also aligns with the logic behind an indicator-drift review, which asks whether a reassuring number still represents the work that leaders think it represents.

This review also creates a record of how the team recognizes uncertainty, which gives leaders a stronger basis for future coaching than a simple pass or fail. It shows whether readiness is distributed across the work or concentrated in one experienced person.

Recommendation

Choose one routine task that your operation considers well controlled and run a 30-minute risk-competence review with the people who perform it. Ask them to describe today's task through the six lenses, name the control they trust most, and explain what would make that control less reliable before an alarm or incident provides the answer.

Then observe one execution without turning the exercise into an audit. Look for the moment when a worker notices variation, the moment when a supervisor decides whether to pause, and the moment when the organization either preserves or loses the original concern.

Corrie Pitzer's central challenge is not to remove controls. It is to prevent controls from becoming substitutes for attention. If safety is readiness to respond, the strongest system is the one in which people can still see, question, and act when familiar work stops being predictable.

Listen to the full conversation with Corrie Pitzer on the Headline Podcast and continue the discussion with your team.