How Corrie Pitzer Thinks About Risk Competence When Controls Become Comfortable

Episode 9 of Headline Podcast was published on November 6, 2025, and features Corrie Pitzer, CEO at Safemap. Pitzer’s central thesis is that risk competence must keep people ready to recognize changing conditions, because a control can reduce exposure while also making the surrounding risk easier to overlook.

That argument changes the question leaders ask about safety technology and procedures. Instead of asking only whether a control exists, they need to ask whether people still notice the conditions that the control cannot cover, explain, or predict.

Risk competence is readiness, not confidence

Risk competence is the ability to recognize meaningful exposure in ordinary situations and respond before the situation becomes an incident. It combines observation, interpretation, questioning, and action. A competent team does not assume that a familiar task is safe because the procedure is familiar. It stays alert to changes in energy, people, timing, equipment, and work conditions, then converts that observation into a decision that the operation can verify.

On the episode, Corrie Pitzer described risk competence as readiness to respond to risks relentlessly. The word readiness matters because risk recognition is not a one-time qualification. It is a condition that can weaken when routine, production pressure, or an apparently reliable control narrows attention.

Confidence can be useful when it comes from verified capability. It becomes dangerous when it is produced by repetition alone. A team that has completed the same task one hundred times may know the normal sequence well, while knowing less about the abnormal condition that appears on the one hundred and first attempt.

The practical distinction is visible in the questions people ask. A confident team may say that the alarm works. A risk-competent team also asks what the alarm cannot detect, who will respond, what happens during a delayed response, and how the condition will be recognized if the alarm is unavailable.

Controls can protect people and narrow attention

A control becomes an attention risk when people treat its presence as proof that the hazard is handled. The control may still reduce exposure, but the team stops looking for changes outside its design assumptions. Leaders should therefore verify both control performance and human awareness, especially when the control is automated, invisible, or rarely challenged during normal work.

Pitzer gave a sharp example on Headline Podcast. He said, “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 quote does not reject controls. It identifies a design failure that appears when the control becomes the only source of permission to act.

This pattern can occur with alarms, interlocks, checklists, permits, dashboards, or digital prompts. Each tool can support a good decision, although each tool also has a boundary. When the boundary is not discussed, the organization gradually transfers judgment from people to the system without confirming that the system can carry that responsibility.

A control review should therefore include three questions. What condition does the control detect? What condition does it leave outside its design? What should a worker do when the signal is absent, late, contradictory, or clearly inconsistent with the work in front of them?

Normal work is where attention becomes expensive

Normal work deserves active risk review because familiarity lowers the perceived need to look again. The job may be physically unchanged while the exposure shifts through staffing, weather, maintenance status, workload, contractor interfaces, or schedule compression. Risk competence keeps the team interested in those changes instead of treating normality as a permanent condition.

Organizations often invest their strongest challenge in unusual jobs. That is sensible, but it can leave routine production with weaker observation. People know the route, the equipment, the handoff, and the expected output, so a small deviation can be absorbed without a deliberate pause.

Corrie Pitzer’s six-lens idea provides a useful way to widen that review. The episode connects risk discovery with the situation, the task, the equipment, the environment, the people involved, and the way the work is managed. The lenses are not a scoring exercise. They are prompts that prevent a single familiar explanation from closing the review too early.

For example, a conveyor transfer may look unchanged while a new operator is learning the route, a guard has been removed for maintenance, a delivery is late, and a supervisor is covering two areas. The procedure may be identical, but the risk picture is not. A risk-competent leader notices the combined condition before asking why someone did not follow the usual sequence.

Measurement should not confuse silence with safety

The absence of incidents does not prove that risk recognition is strong. Leaders need measures that show whether people notice, discuss, escalate, and resolve changing conditions. A quiet operation can be safe, underexposed, or simply unable to see and report its weak signals, so performance interpretation must include the quality of attention rather than only the number of recorded events.

Pitzer compared accident-free reasoning with sending a thousand people out with buckets of seawater for a thousand years and using the result to prove that there are no whales in the ocean. The comparison is memorable because it exposes the difference between an absence of evidence and evidence that the risk is absent.

A more useful dashboard can pair outcome measures with evidence of risk competence. Leaders can review how many concerns were raised, how many were specific enough to trigger a decision, how long unresolved exceptions remained open, and whether the same condition returned after closure.

Technology should solve a named problem

Technology supports risk competence when the organization can name the problem, the decision it must improve, and the human judgment that must remain active. A catalog of sensors, apps, cameras, and analytics is not a risk strategy. The right tool is the one that improves recognition or response without hiding the assumptions that still require professional attention.

This principle connects with the wider Headline conversation about technology adoption. A digital control can make weak signals easier to see, but it can also create a new dependency if the team no longer knows how to work when the data is missing or ambiguous.

Before buying a tool, an operations leader should describe the current failure in observable terms. Is the problem that workers cannot see a change in pressure? Is the problem that supervisors receive information too late? Is the problem that a known concern has no owner? Each answer leads to a different intervention, and a technology purchase may not be the best one.

That problem-first discipline also protects psychological safety. When people can say that the tool is wrong, incomplete, or poorly fitted to the work, leaders receive better information. When disagreement is treated as resistance to innovation, the organization gets polished data with less trust behind it.

Risk professionals translate conditions into decisions

The safety professional adds value by translating frontline conditions into decisions that operations, engineering, maintenance, and executives can act on. Translation means preserving the uncertainty and consequence in the message, not reducing every concern to a compliance label. The strongest translation makes the exposure, the missing control, the decision owner, and the required verification easy to understand.

Pitzer described the safety professional as a translator for the frontline. That role is more demanding than distributing rules because the translator must preserve meaning across different professional languages. A technician may describe vibration, an operator may describe hesitation, and a manager may describe delay. The risk professional connects those observations without flattening them into a generic finding.

Translation should move in both directions. Leaders need the field reality, while the field needs to know what decision was made and why. When the message only travels upward, workers may report conditions without seeing a response. When it only travels downward, instructions may arrive without the context that makes them credible.

One useful test is to ask a worker and a senior leader the same question after a risk review. What changed, who owns the next decision, and what would cause the team to stop or escalate? If their answers differ materially, the operation has an information problem even if its paperwork is complete.

Recommendation

Use one routine task to test risk competence this week. Select a control that people trust, ask what it can and cannot detect, observe how the team responds when the expected signal is absent, and record the decision route for an uncertain condition. The goal is not to remove the control. The goal is to confirm that people remain capable of seeing beyond it.

Start with a task that appears stable rather than spectacular. A normal transfer, inspection, delivery, or maintenance handoff will reveal more about attention than a workshop designed to produce dramatic hazards. Ask the people who perform the work where the normal pattern changes, what the control does not show, and which warning is hardest to escalate.

Then compare the answers with the formal risk assessment. Record the gaps without blaming the person who noticed them. Assign one owner to decide what changes, one person to verify the change in the field, and one date for checking whether the condition returned.

That small review puts Corrie Pitzer’s argument into practice. Risk competence grows when people remain ready to recognize what the system cannot guarantee, and when leaders make that recognition useful in a real decision.

Headline Podcast is the space where leadership and safety come together to shape better workplaces and better lives. Listen to the full conversation with Corrie Pitzer.

For a related field application, read Task Criticality Explained, compare warning follow-up in Near-Miss Reviews, and review how records shape decisions in Risk Register vs Exception Register vs Safety Decision Log.