How Andrea Hernandez Thinks About Safety Beyond Zero Harm

Episode 8 of the Headline Podcast was published on October 23, 2025, with Andrea Hernandez, Siemens Global Health and Safety Vice President. Hernandez defended a clear thesis on the show: safety strategy must evolve beyond a zero-harm program when the organization needs a more proactive, human-centered approach.

Her argument is not permission to lower expectations. It is a demand for better questions, especially when a familiar slogan begins to substitute for evidence about risk, health, voice, and the way work is actually organized.

Why a serious safety strategy must change with the problem

A safety program is never separate from its context. A business changes its technology, workforce, markets, contractors, operating model, and production pressure, which means the conditions that once made an initiative useful may no longer be the conditions leaders need to manage.

Hernandez described Siemens' zero-harm program as something that delivered what the company needed at the time, before it evolved in 2020 into Healthy and Safe at Siemens. That distinction matters because a mature leader can respect an earlier intervention without treating it as a permanent identity.

Andreza Araujo's work across more than 250 cultural transformation projects reaches a similar practical point. Culture is visible in repeated decisions under pressure, so a strategy should be judged by the decisions it improves, not by how long the organization has displayed its name.

What zero-harm language can reveal and what it can hide

Zero-harm language can communicate that injuries and serious events are unacceptable. It can also hide weak reasoning when leaders assume that declaring an outcome proves they understand the controls, exposures, and trade-offs that shape it.

The trap appears when the target becomes more visible than the conditions behind it. A green dashboard, a completed campaign, or a public commitment may coexist with rushed maintenance, unclear escalation, or a team that has learned to keep bad news out of the meeting.

James Reason's distinction between active failures and latent conditions helps leaders examine this gap. The final action may be close to the event, while the decisions that made the action likely were taken months or years earlier in planning, design, staffing, or supervision.

The practical test is simple. Ask what evidence would show that the current strategy is working before an injury occurs, then name the person who can obtain that evidence and the decision it should change.

Start with the problem before choosing the technology

Hernandez said that leaders should first ask what problem they want to solve, because implementing technology for its own sake makes no sense. That principle protects safety teams from confusing novelty with control.

A technology catalog can be useful after the problem is precise. If the problem is that a critical isolation cannot be verified at the point of work, the team can compare a digital confirmation, a redesigned handover, a physical interlock, or a change in authorization. The tool is not the starting point.

This order also protects workers from technology-driven psychosocial risk. Monitoring that adds alerts without adding authority can increase cognitive load, while an app that collects concerns without closing the loop can teach people that reporting is another form of unpaid work.

Before approving a new system, write four lines that name the exposure, the decision the system should improve, the human action that remains necessary, and the signal that would show the tool is creating noise. If the team cannot complete those lines, the purchase decision is premature.

Why people-centered strategy is operational, not decorative

People-centered safety is sometimes treated as a softer alternative to technical control. Hernandez's position is more demanding. A workplace becomes safer when people have the knowledge, authority, and support needed to recognize a problem and change the work before the exposure becomes an event.

That requires leaders to examine the distance between policy and execution. A worker may be empowered in a presentation yet still lack time to stop a task, access to a competent decision maker, or protection from a supervisor who interprets questions as resistance.

In more than 25 years of executive EHS work, Andreza Araujo has emphasized that safe behavior is shaped by the environment in which decisions are made. The leader's responsibility is therefore larger than asking people to care. It includes making the safer decision feasible when the schedule becomes tight.

At board and executive level, this becomes a resource question. Review whether staffing, maintenance windows, contractor selection, and production incentives support the behavior the strategy claims to value.

Psychological safety begins in the small team

Hernandez said that psychological safety happens at team level. People may not speak in a group of 1,000 if they cannot speak in the small group with which they share eight hours each day.

The point changes the leadership task. A corporate message about speaking up cannot compensate for a local supervisor who interrupts uncertainty, rewards speed after a concern is raised, or closes a report without explaining the decision.

A useful review has three questions. What did a worker challenge during the last 30 days? What changed after the challenge? What did the team learn about the consequences of raising the next concern? The answers reveal more than an average culture score.

Senior leaders should sample the experience across at least three teams, because a strong local supervisor can create trust that the wider system has not yet earned. The variation is not a nuisance in the data. It is the management problem.

Well-being belongs inside business strategy

Hernandez connected health and safety with a wider concern for well-being. This is important because workload, recovery, staffing, and organizational change can alter the quality of every safety decision that follows.

Well-being should not become a referral pathway that sends a distressed worker away while the work system remains unchanged. Leaders need to ask whether work design is producing avoidable strain through chronic overtime, conflicting priorities, low control, or constant digital interruption.

That does not turn every difficult day into a clinical diagnosis. It gives management a better way to separate individual support from conditions that require an operational response.

Use a monthly review with two columns. One records the support offered to people. The other records the work conditions that made support necessary. If the second column never changes, the organization is treating the signal without addressing its source.

Strategy comparison: slogan, program, or operating system?

Hernandez's conversation helps separate three ways leaders can position safety. Each can sound positive, but they produce different decisions when the organization faces uncertainty or pressure.

The operating-system view does not discard programs or commitments. It places them inside a decision architecture that leaders can inspect. That is the difference between changing a label and changing how the organization works.

What the executive team should decide next

The senior team should not leave this discussion with a general instruction to become more human-centered. It should choose one decision where the old strategy still shapes behavior, such as approving overtime, selecting a technology, closing a concern, or funding maintenance, and make the hidden trade-off explicit.

For that decision, name the outcome the business wants, the serious exposure that could be created, the people who hold relevant field knowledge, and the authority that can pause or redesign the plan. This creates a small but visible test of whether the organization has moved from intention to operating discipline.

Review the result with the affected team after 14 days. Ask whether the decision became clearer, whether the work became easier to perform safely, and whether anyone had information that was still missing from the executive view. Those answers give the board something more useful than a renewed campaign slogan.

Recommendation

Take one safety initiative that has been running for at least 12 months and review it in four meetings. In the first, state the problem it was created to solve. In the second, compare that problem with current field evidence. In the third, ask one team what the initiative makes easier and what it makes harder. In the fourth, decide what to keep, redesign, or stop.

Ask the executive sponsor to attend the final meeting, not to defend the program, but to decide which resource, authority, or operating rule must change. Then revisit the decision after 30 days and publish the evidence to the people whose work is affected.

Conclusion

Andrea Hernandez's Episode 8 message is a challenge to static safety identity. The organization that once needed a zero-harm program may now need a strategy that connects context, worker agency, team-level voice, technology discipline, and well-being to the decisions that shape exposure.

Safety becomes more credible when leaders stop asking whether the slogan is still admired and start asking whether the current system solves the current problem. That question is demanding because it can require a respected program to evolve, yet it is also how a commitment remains useful after the conditions change.

Listen to the full conversation with Andrea Hernandez, then test one safety initiative against the four questions above. For a related Headline perspective, read how Siemens approaches safety culture beyond compliance and explore the Headline Podcast.