How Clive Lloyd Thinks About Zero-Harm Goals When Trust Is Under Pressure

F8 episode companion for EHS managers, safety leaders, and operations executives

Episode 12 of the Headline Podcast, published on December 17, 2025, featured Clive Lloyd, CEO at GYST, in a conversation about zero-harm goals, trust, and the incentives that shape safety culture.

Clive Lloyd's central argument is that a well-intended target can increase risk when people believe that protecting the number matters more than exposing the conditions behind it.

Why zero-harm goals need a trust test

A zero-harm goal is useful only when it strengthens early reporting, control improvement, and honest escalation rather than rewarding silence after an event or concern.

The ambition is understandable. Leaders do not want people injured, and a target can signal that serious harm is unacceptable. The difficulty begins when the target becomes the main proof of performance. A clean result may reflect strong controls, low exposure, underreporting, or a workforce that has learned which information creates trouble.

Clive Lloyd said on Headline Podcast, “A goal of zero is well-intended, but research shows it tends to make life-changing incidents and fatalities more likely, that's ideology over evidence.” The quote does not dismiss prevention. It asks leaders to examine the behavior a target produces after a near miss, a serious concern, or a reportable event.

That question connects with James Reason's work on organizational accidents. A visible event is often the last layer in a chain of latent conditions, which means the quality of information before the event matters as much as the final count.

The number can become a loyalty test

A target becomes dangerous when employees experience it as a test of loyalty to the organization instead of a prompt to reveal and reduce serious exposure.

Imagine a supervisor whose monthly review is dominated by whether the site preserved a zero record. The supervisor may still ask for observations, but the conversation changes when an employee reports a hand injury, a failed isolation, or a repeated bypass. If the first response is “How will this affect our result?”, the organization has already taught the next person to wait.

Clive Lloyd described this dynamic through the cobra effect, in which a reward intended to solve a problem creates behavior that worsens it. The safety version is not always dramatic. It may appear as narrower reporting, delayed escalation, informal reclassification, or a preference for easy observations that cannot threaten the headline result.

Leaders should therefore separate two questions. What happened to the outcome number? What did the operating system make easier or harder to report? The second question is where trust becomes visible.

Trust is built through the response to bad news

Trust grows when people see that credible concerns receive access, listening, a reasoned response, and follow-through that remains visible after the meeting ends.

Clive Lloyd said, “Trust arrives on foot but it leaves on horseback.” For a safety leader, the phrase becomes a practical sequence. When a worker raises a difficult concern, can that person reach someone with authority? Does the manager understand the concern before judging it? Does the plan change when the evidence supports a change? Can the worker see what happened afterward?

These four moments create a measurable trust path. A site can review the time from first signal to decision, the percentage of concerns that receive a named owner, the number of work plans changed after field evidence, and whether the person who raised the concern receives a closeout explanation.

Those measures do not replace injury data. They add information about the conditions that shape future injury data. A leader who reviews only the final count sees the end of the process. A leader who reviews the response path can see whether the process still carries useful information.

On Headline Podcast, Clive Lloyd also argued that “The more organizations sought to force compliance, it can actually have the opposite impact.” That warning is especially relevant when a target is attached to discipline, recognition, or executive status.

What to measure beside the outcome

Pair harm outcomes with measures of exposure, response quality, and control change so leaders can distinguish prevention from silence.

The table is not a new scorecard to celebrate. It is a way to prevent one number from carrying a question it cannot answer. The National Safety Council's public guidance on leading indicators makes the same broad distinction between measures that describe what already happened and signals that help leaders act before harm occurs. A metric earns its place when someone can make a safer decision because of it.

How leaders can detect the cobra effect

Leaders can detect a perverse incentive by comparing what the system rewards with what workers actually discuss when a control fails or a plan changes.

Start with the last three difficult reports, not the last three successful audits. Ask who raised the concern, how quickly it reached decision authority, whether the work changed, and what the reporter learned from the response. Then compare those answers with recognition criteria, production meetings, and monthly safety dashboards.

A warning sign appears when reports are praised in principle but questioned in practice. Another appears when managers celebrate zero events while carrying open critical-control failures. A third appears when the organization counts activity but cannot show which decision changed because the activity occurred.

Clive Lloyd's argument does not require leaders to abandon ambition. It requires them to make the target subordinate to the information needed to achieve it. The stronger message is not “protect zero at all costs.” It is “surface serious exposure early, improve the control, and make the response visible.”

What leaders should do in the next review

The next review should test whether the target improved decisions, not merely whether the dashboard stayed green.

Use one recent concern as the review case. Write down the first signal, the person who received it, the decision authority, the control that was tested, and the final response. Then ask whether the record preserves the uncertainty that existed at the time. A retrospective report that makes every step look obvious may be tidy, but it can hide the moment when the organization chose speed, convenience, or optimism.

Give the person who raised the concern a formal place in the review without turning that person into the owner of the problem. The owner of the risk remains the person with authority to change the work, while the reporter provides evidence about what was visible from the operating position. This distinction protects the information path and prevents leaders from shifting accountability downward.

Review the time between signal and response in hours or days, depending on the exposure. Review whether the response changed equipment, staffing, sequencing, authorization, supervision, or the decision to proceed. If the only outcome was a reminder to be careful, the system probably answered a control problem with a behavior message.

Finally, return to the same exposure after the change. A control is not improved because a meeting agreed that it should improve. It is improved when the field condition, the decision rule, and the owner's evidence all show that the previous weakness has been addressed.

That review also gives executives a better question for the next board or leadership meeting. Instead of asking only whether the site is still at zero, ask which serious exposure was removed, which concern changed a decision, and where the organization still depends on trust that has not been tested. Those questions keep the ambition connected to operating reality.

Recommendation

Keep the zero-harm ambition, but govern it through evidence that shows whether people can report, whether leaders respond, and whether controls improve before an injury occurs.

For the next monthly review, place the outcome number beside four questions. What serious exposure was found? Who owned the response? What changed in the work? Would the person who raised the concern do it again?

If the answer to the last question is uncertain, do not solve the problem with another poster or another declaration. Ask the leader closest to the work to explain what happened after the last difficult report, then test that explanation against the field.

Andreza Araujo and Dr. Megan Tranter created Headline Podcast as a space where leadership and safety come together to shape better workplaces and better lives. That purpose is stronger when the conversation stays focused on decisions, incentives, and the conditions that let people tell the truth.

For a related perspective on safety culture and leadership, read the work of Andreza Araujo, and compare the target with the operating evidence before deciding whether the number tells the whole story.

Listen to the full conversation with Clive Lloyd on Headline Podcast.