6 Blind Spots Corrie Pitzer Exposes in Risk Competence

Episode 9 of Headline Podcast, published on November 6, 2025, features Corrie Pitzer, CEO at Safemap.

His central argument is that risk competence depends on keeping people alert to changing exposure, because a control can reduce danger while also making the situation look safer than it is.

What does risk competence mean when work looks normal?

Risk competence is the readiness to recognize and respond to risk before an event makes the danger obvious. Corrie Pitzer describes it as a practical capability rather than a personality trait or a slogan for a safety campaign. The capability belongs to the people who plan the work, supervise it, perform it, and decide whether the conditions are acceptable.

That distinction matters because normal work rarely announces its most important changes. A familiar task can involve a different contractor, a tighter production window, a degraded barrier, or a new interaction between teams. The work still looks routine, so the organization relies on yesterday's judgment even though today's exposure has moved.

On the conversation, Pitzer defines the idea directly. “Safety is the readiness to respond to risks relentlessly,” he says, adding that the one word for that readiness is risk competence. The phrase is useful because it moves the discussion away from the absence of harm and toward the quality of recognition before harm occurs.

This is consistent with OSHA's recommended practices for safety and health programs, which place worker participation, hazard identification, and hazard prevention inside the operating system rather than treating them as separate paperwork activities.

Why can a well-designed control weaken attention?

A control can lower exposure and still create a new management problem when people stop looking for conditions that fall outside the control's design assumptions. The alarm, checklist, interlock, permit, or procedure becomes a signal that the risk has already been handled, even when the control is unavailable, bypassed, poorly understood, or mismatched to the task.

Pitzer offers a sharp warning from the frontline. “I put a control in place, the workers stopped looking and just waited for the alarm,” he explains. “I had turned them into potential victims of my own design.” The point is not that controls are harmful. The point is that a control must not replace attention to exposure.

Leaders should therefore ask two separate questions. Does the control work as designed? What conditions could make the design assumption false today? The first question tests reliability. The second tests whether people still notice the situation around the control.

NIOSH's hierarchy of controls helps frame the distinction because stronger controls change the exposure itself, while administrative measures and personal protective equipment depend more heavily on human recognition and execution. Even a strong control needs verification when the work changes.

Which six blind spots make normal work look safer?

Pitzer's conversation can be translated into six recurring blind spots that make risk competence harder to practice. They are not six steps in a checklist. They are six questions that expose where a team may be relying on appearance instead of current evidence.

The value of this table is diagnostic. It gives a supervisor a way to interrupt automatic reassurance without pretending that every uncertainty requires a shutdown. The answer may be a pause, a narrower work boundary, a second verification, or a decision to continue with an explicit reason.

Why is the absence of accidents a weak safety measure?

Organizations often use a clean incident record as evidence that their controls are effective. Pitzer challenges that logic with an image that is difficult to forget. “You can send a thousand people out with buckets of seawater for a thousand years and prove there are no whales in the ocean,” he says. “That's how we try to measure safety by the absence of accidents.”

The analogy does not dismiss incident data. It shows why the outcome alone cannot explain the exposure that produced it. A quiet period may reflect effective barriers, favorable conditions, limited reporting, or simple randomness. Those explanations require different leadership responses, which is why the same number can support both confidence and concern.

The practical alternative is to examine the readiness that exists before the outcome. Are critical controls available? Can people describe the exposure in plain language? Do supervisors know which conditions require escalation? Does the decision record preserve uncertainty instead of editing it into certainty?

The ISO 45001 framework also points organizations toward processes for hazard identification, operational planning, worker participation, and continual improvement. Those processes are more informative when leaders use them to test changing conditions, not simply to confirm that a system has produced no recordable event.

How should a safety professional translate risk for the frontline?

Pitzer describes the safety professional as a translator. That role is not about replacing the worker's judgment with technical language. It is about making the exposure visible to the people who control the work and converting operational detail into a decision that can be understood, challenged, and acted upon.

Translation starts with the situation rather than the rule. Instead of asking whether the team followed the procedure, ask what the team was trying to accomplish, what made the task harder, which assumption no longer held, and what consequence would follow if the condition continued. Those questions create a more accurate bridge between work as planned and work as performed.

It also requires a response path that keeps technical concerns visible. The frictions that keep expert warnings out of decisions show why a useful observation can lose force before it reaches the person who can change the work.

A useful translation has four parts. It names the exposure, identifies the people or assets that could be affected, describes the control that is expected to work, and states the condition that would require a change in the plan. When any of these parts is missing, a risk discussion can sound precise while leaving the decision unresolved.

This is where the risk-criteria decisions that keep board thresholds from hiding exposure become relevant. The same language that helps a board understand residual exposure must also remain usable at the workface, or risk competence will stop at the meeting room.

What should leaders compare before trusting a control?

Leaders can compare a control-centered review with a risk-competence review before approving work. The difference is not the presence of a control. It is the breadth of the questions that surround it.

The comparison also clarifies accountability. A supervisor owns the immediate decision, but the organization owns the conditions that make recognition possible, including staffing, maintenance, competence, time pressure, and escalation access. When leaders review only whether a control was listed, they place the burden on the person closest to the hazard while leaving the design of the work unquestioned. Risk competence gives the organization a fairer test because it asks whether the system made the safer decision visible and practicable before continuation was approved.

The control-centered review is not wrong. It is incomplete when it treats evidence of deployment as evidence of protection. A risk-competence review asks whether the people closest to the work can detect when the barrier no longer fits the situation.

That same distinction appears in barrier health testing, where the question is not simply whether a control exists but whether it remains capable of preventing the consequence under current conditions.

Recommendation

Use risk competence as a readiness test before relying on a familiar control. Ask the team what changed, which assumption is weakest, who is exposed, how the control could fail, and what evidence would justify continuing. Record the answer in language that the frontline, the supervisor, and the executive can all understand.

Do not turn the six blind spots into another form that people complete without thinking. Use them to create a conversation in which uncertainty can be named early, the decision owner is visible, and a control is treated as a working barrier rather than a reason to stop looking.

Headline Podcast exists for these real conversations between leadership and safety. Corrie Pitzer's episode is especially useful for teams that have strong procedures but still struggle to recognize changing exposure. Listen to the full conversation with Corrie Pitzer.