Corrie Pitzer on Risk Competence: 6 Lenses That Reveal Danger Before Controls Create Blindness

Episode 9 of the Headline Podcast, published on November 6, 2025, brought Corrie Pitzer into a conversation about risk competence, normal-looking work, and the limits of relying on controls. On the show, Pitzer argued that safety improves when people keep discovering changing risk instead of treating a control as proof that the work is already safe.

Why risk competence is more than hazard awareness

Risk competence is the ability to recognize a changing exposure, interpret what it means, and act before the situation becomes irreversible. It is different from memorizing hazards or completing a risk assessment because it remains active after the form is signed. A competent team notices when the task, control, or context no longer matches the assumption behind the original decision.

That distinction matters because most workplaces already have procedures, permits, training records, and inspections. The gap appears when people can name the control but cannot explain what would make it unreliable. A guard, alarm, checklist, or permit may still be present while the operating conditions have moved beyond the evidence that justified it.

Corrie Pitzer described the idea in a direct sentence on Headline Podcast: “Safety is the readiness to respond to risks relentlessly, and the one word for that readiness is risk competence.” The phrase shifts the conversation from safety as an outcome to safety as a capability that must remain available during normal work, change, and pressure.

The Occupational Safety and Health Administration describes safety management as an ongoing process, and that principle is useful here. A risk review that ends at authorization misses the point. The team still needs a way to detect drift during the first hour, the next shift, and the next change in production demand.

What normal work hides from a risk review

Normal work hides risk when familiarity makes a changing condition look like a repetition of yesterday. The task may carry the same name, use the same equipment, and follow the same written method, yet a different load, weather pattern, crew, interface, or production constraint can change the exposure.

A useful review therefore asks more than whether the hazard was listed. It asks what has changed since the last comparable task, which control depends on human timing, and where the crew has had to improvise. Those questions keep a risk assessment connected to work as performed rather than work as described in a stable procedure.

The first signal is often small. A worker waits for an alarm that arrives late. A supervisor moves a person away from the planned position. A contractor uses a familiar shortcut because the approved route is blocked. None of those observations proves that a serious event will follow, but each one tells the leader that the original control logic needs another look.

The National Institute for Occupational Safety and Health links safety culture with the conditions that shape how work is carried out. For a manager, the practical question is whether the reporting channel can carry these weak signals before they become accepted features of the job.

Six lenses for discovering risk that looks ordinary

Six lenses make risk discovery more reliable because they force the team to inspect the same work from different positions. The lenses are task, time, interface, control, consequence, and recovery. They do not replace a formal assessment. They give the assessment a sharper set of questions when the work appears routine.

Task. What is the person actually doing, and where does the sequence differ from the written method? The answer should include the physical action, the decision point, and any step that depends on a person noticing a condition quickly.

Time. What changes across the first 10 minutes, the next 2 hours, or the end of the shift? Fatigue, temperature, backlog, handover quality, and time pressure can alter the control even when the equipment remains unchanged.

Interface. Which team, contractor, vehicle, system, or decision sits next to the task? Many exposures develop at boundaries because each group understands its own activity while no one owns the interaction.

Control. What must be true for the barrier to work, and who can verify that condition? A control that depends on a single alarm, one experienced operator, or an uninterrupted handoff has a narrower operating window than the procedure may suggest.

Consequence. What would the first credible loss of control look like, and how quickly could it become serious? This keeps the review focused on the path to a high-consequence event rather than on the comfort of a low incident count.

Recovery. If the control fails, what can the team still do in the next 1, 3, or 5 minutes? Recovery is not an excuse for weak prevention. It shows whether the plan has a realistic margin when the first barrier does not perform as expected.

These six lenses also create a common language for the frontline and the executive team. The supervisor can use them during a 15-minute field review, while the director can use the same questions in a monthly risk conversation without pretending that a dashboard contains the whole operating picture.

When a control creates blindness

A control creates blindness when people stop observing the hazard because the control is treated as a permanent guarantee. The danger is not that the control exists. The danger is that confidence in the control replaces attention to the conditions that allow it to work.

Pitzer gave the pattern a memorable form on the podcast: “I put a control in place, the workers stopped looking and just waited for the alarm, and I had turned them into potential victims of my own design.” That statement is not an argument against alarms or engineered protection. It is a warning against designing a system in which the user has no remaining role in detecting failure.

Leaders can test for control blindness with 3 questions. What would the worker notice before the alarm? What would the supervisor do if the alarm stayed silent? What evidence shows that the control is working under today's conditions? If the team cannot answer, the control may be carrying more confidence than proof.

The UK Health and Safety Executive treats human factors as part of how systems perform, which supports a practical reading of Pitzer's point. A barrier is not only a device. It is a relationship among design, attention, communication, maintenance, and authority.

How safety professionals translate risk for the frontline

Safety professionals create value when they translate technical risk into decisions that the frontline can recognize and challenge. Translation does not mean simplifying the risk until its consequence disappears. It means connecting the hazard, the control, the evidence limit, and the requested action in language that the person doing the work can use.

The translator role becomes important when a risk moves between engineering, operations, maintenance, and leadership. Each group sees a different portion of the problem. The engineer may see a design tolerance, the operator may see a repeated workaround, and the executive may see a performance trend. Risk competence connects those views without allowing one vocabulary to erase the others.

A short translation can follow 4 parts. Name the condition that is changing. Explain the credible consequence. State which control is expected to hold. Ask what decision or verification is needed before the work continues. This structure takes less than 2 minutes when the facts are clear, yet it prevents a vague statement such as “the risk is being managed” from closing the conversation.

Translation also requires humility. The safety professional should not assume that a person who questions the plan is resistant to change, just as the frontline should not assume that every technical warning is detached from production reality. The strongest exchange makes room for both the evidence and the experience that reveals where the plan is failing.

Risk competence versus control confidence

Control confidence asks whether a listed barrier exists. Risk competence asks whether the team can recognize when that barrier is no longer enough. Both questions matter, but they produce different management behavior. The first supports assurance of design. The second protects the decision when reality changes.

The table shows why a low number of control failures does not automatically prove that the system is learning. If the team only records whether the barrier was available, it may never see that the work has become dependent on a workaround, a late warning, or one experienced person who knows how to compensate.

Recommendation

Use risk competence as a weekly field capability, not as another annual training label. Pick one normal-looking task, apply the 6 lenses, document 3 conditions that could change the exposure, and assign 1 person to verify whether the existing control still fits. Review the evidence after 7 days, then repeat the exercise after 30 days if the task remains critical.

Start with the work that leaders believe is already under control. That choice is deliberate because a dramatic hazard usually attracts attention, while familiar work can quietly accumulate shortcuts, interface problems, and delayed warnings. Ask the crew to show where the plan becomes difficult, then compare those observations with the formal risk assessment.

Next, give the review a visible response. If the team raises a concern, record the decision, the owner, the evidence requested, and the date for checking whether the change worked. A response within 24 hours is useful, but the deeper test is whether the person who raised the concern can see what happened after the decision.

Finally, bring one example to the monthly leadership meeting. Do not present it as a story about a careless worker. Present it as evidence about how the system recognized, missed, or corrected changing risk. That is how a safety function turns a podcast insight into an operating habit that protects attention without weakening accountability.

Corrie Pitzer's message is demanding because it refuses to let a completed control stand in for continued readiness. Listen to the full conversation with Corrie Pitzer on Headline Podcast and ask which ordinary task in your operation needs a fresh look before confidence becomes blindness.