How Corrie Pitzer Thinks About Risk Competence Before Metrics Can Be Trusted

Episode 9 with Corrie Pitzer was published on November 6, 2025, and examined risk competence as a practical capability rather than a score on a dashboard. The guest's central argument was that leaders cannot treat a quiet record as proof of readiness when people stop noticing risk for themselves.

Why do familiar tasks escape attention?

Risk competence is the ability to recognize changing exposure, question whether a control still works, and respond before the situation becomes consequential. In Episode 9, Corrie Pitzer connected that capability to everyday work, where repetition can make a hazardous condition look ordinary after only a few cycles.

That distinction matters because a familiar task often receives less scrutiny than a new task, even when the surrounding conditions have changed. A different crew, a delayed maintenance action, a new production target, or a temporary workaround can alter the exposure without changing the task name.

Pitzer's point also challenges a common measurement habit. A site may record zero injuries for 30 days while its people become less able to recognize weak controls. Andreza Araujo makes a related argument in Sorte ou Capacidade, where the absence of an event is not treated as proof of capability because luck and underreporting can produce the same number.

OSHA describes worker participation as a core element of a safety and health program, which means the organization needs usable routes for workers to identify conditions that a dashboard cannot see.

What does risk competence add to a safety metric?

Risk competence adds evidence about whether people can interpret exposure before harm occurs, while a lagging metric records what happened after a barrier failed. ISO 45001, published in 2018, supports this distinction by requiring organizations to manage operational risks rather than relying only on injury outcomes.

The practical question is not whether a metric should exist. Leaders need measures that reveal whether workers can identify a changed condition, explain the control that should hold, and escalate when the work no longer matches the plan.

Consider a critical-control verification that records “checked” without recording what the worker observed. The activity may look complete, yet it does not show whether the person understood the exposure or merely followed a prompt. Safety metrics that separate activity from control assurance make this difference visible in management meetings.

Corrie Pitzer's warning is useful here because it moves the discussion from counting actions to testing attention. If a metric can be improved without improving the decision made in the field, it is measuring administrative motion rather than risk competence.

Which six lenses help leaders find hidden risk?

Pitzer described six lenses for discovering risk in situations that look normal. Used together, the lenses ask leaders to examine the task, the conditions around it, the assumptions behind the plan, the controls in use, the signals that precede failure, and the consequences that would follow if the control did not hold.

The first lens is task familiarity. Ask what has become invisible because the job is repeated. The second is context change. Check what moved since the last cycle, including staffing, weather, equipment condition, interfaces, and time pressure.

The third lens is control dependence. A protective device can reduce exposure while also reducing attention if workers no longer understand what the device can and cannot do. The fourth lens is assumption quality. A plan may assume that a permit, alarm, isolation, or rescue resource will be available when the work begins, although the field condition may contradict that assumption.

The fifth lens is weak-signal visibility. Look for delayed reports, unexplained workarounds, repeated questions, and changes in handover language. The sixth lens is consequence recognition, which asks whether the team understands what could happen before the event becomes obvious.

These lenses create a different conversation from a general safety observation. They connect perception to decision quality, which is why risk-perception distortions that hide familiar hazards belong in a metrics discussion rather than only in behavioral training.

Can a control reduce safety when attention disappears?

A control can reduce safety when it removes the worker's ability or incentive to notice changing exposure without providing another reliable detection route. Pitzer illustrated this risk by describing how a control can create passive dependence, especially when the warning arrives after the person has lost the chance to act.

On Headline Podcast, Corrie Pitzer said: 'I put a control in place, the workers stopped looking and just waited for the alarm.'

The quote is not an argument against engineering controls. It is an argument against treating a control as self-validating. A sensor, interlock, alarm, or automatic shutdown needs a defined proof test, a clear response, and a workforce that understands the remaining exposure.

NIOSH explains the hierarchy of controls by placing elimination and substitution above administrative controls and personal protective equipment, but the hierarchy does not remove the need to verify that a selected control is available, effective, and understood.

A useful review therefore asks three questions. What does the control prevent? What does it leave exposed? Which human observation or technical test should reveal deterioration before the consequence occurs?

How should leaders compare activity with readiness?

Leaders should compare what the organization records with what people can demonstrate under realistic conditions. Activity measures show that a meeting happened, a checklist was completed, or a training module was assigned. Readiness evidence shows whether a worker can identify the critical exposure, explain the barrier, and take the correct action when the situation changes.

The comparison does not make activity useless. It gives activity a test. A record becomes more valuable when it is connected to an observable change in the work method, the control, the escalation path, or the decision owner. Leading indicators that change decisions provide a useful bridge between the record and the management response.

Why is the absence of accidents weak evidence?

The absence of accidents is weak evidence because a consequence is only one possible output of a risk system. In Episode 9, Pitzer used a memorable analogy to show why leaders should not infer safety from a quiet record without testing the conditions that produced it.

On Headline Podcast, Corrie Pitzer said: 'You can send a thousand people out with buckets of seawater for a thousand years.'

The analogy matters for executives because injury counts are easy to compare, while capability is harder to see. A low rate may reflect sound controls, limited exposure, favorable conditions, incomplete reporting, or a combination of all four.

Andreza Araujo's Muito Além do Zero develops the same caution around zero targets. When the number becomes the purpose, people can protect the number instead of improving the system that the number was meant to represent.

BLS publishes occupational injury and illness data, but a national outcome dataset cannot tell a site whether its own workers can recognize a deteriorating control today. Site leaders still need leading evidence tied to real decisions.

Recommendation

Build risk competence into the monthly safety review by selecting one critical task, asking workers to identify its six risk lenses, and testing one control under changed conditions. Record the decision that follows, not only the attendance, inspection, or checklist activity.

Within 7 days, choose a familiar task that has produced reassuring metrics and interview the people who perform it. Within 14 days, compare their answers with the written control assumptions. Within 30 days, close one gap through a design change, a clearer escalation route, or a verified work-method update.

This sequence gives the C-suite and EHS leader a better question than “How many incidents did we have?” It asks whether people can still see the risk when the task looks ordinary, the control appears available, and the dashboard remains quiet. Control assurance outside the audit helps turn that question into evidence.

The review should also record disagreement. If every participant gives the same answer immediately, ask what assumption has not been tested and who would challenge the plan if the task became harder. That question is especially important when the work has been repeated without an injury, because the team may have learned that raising uncertainty slows production without changing the decision. Risk competence grows when questioning leads to a visible response, even when the response is to retain the plan and explain why.

Conclusion

Risk competence is the readiness to recognize changing exposure and act before a consequence, so leaders should measure field judgment and control reliability alongside injury outcomes.

Listen to the full conversation with Corrie Pitzer and use the six lenses in your next operational review.