How Andrea Hernandez Thinks About Psychological Safety Before Global Strategy

Episode 8 of the Headline Podcast was published on October 23, 2025, with Andrea Hernandez, Siemens Global Health and Safety Vice President. On the show, she defended a context-first, people-centred approach in which psychological safety begins inside the small team rather than in a global declaration.

Her argument changes the leadership sequence. Instead of announcing a universal safety ambition and waiting for local adoption, leaders should understand the work, give people influence over its design, and examine whether the immediate team makes honest information easier or harder to share.

Why does psychological safety begin with context?

Context determines what a concern means and what response it needs. A worker who questions a maintenance isolation, a production target, or a new digital tool is not speaking into an abstract culture. That person is speaking during a shift, with a supervisor nearby, while a delivery promise or staffing constraint is active.

Andrea Hernandez's approach starts by asking what problem the organization is trying to solve. The question sounds simple, but it prevents leaders from importing a fashionable intervention before they understand the exposure. It also keeps psychological safety connected to work design, because people need permission to describe the actual problem before they can help solve it.

The Occupational Safety and Health Administration's Recommended Practices describe seven core elements for a safety and health program, including management leadership, worker participation, and hazard identification. That structure supports the episode's central point. Worker participation is not a communications exercise. It is part of how the organization identifies and controls risk.

What changes when the team becomes the unit of trust?

Large organizations often measure culture at the level at which they manage it. They compare business units, publish a group score, and ask leaders to improve the average. Teams experience culture differently. They notice who gets interrupted, who receives a follow-up, whose concern becomes a work change, and whether the person who raised a problem is blamed for slowing production.

On Headline Podcast, Andrea Hernandez said that “psychological safety happens at the team level.” She also described the need to ask “what is the problem we want to solve” before selecting an intervention. The wording is precise. The team is where risk information either gains permission to travel or loses energy before it reaches the wider system.

A supervisor can make that unit safer by closing the loop within 24 hours when a serious concern is raised, explaining what is known, naming what is still uncertain, and stating who owns the next decision. The response does not need to be immediate agreement. It needs to be visible, proportionate, and free from retaliation.

How does people-centred strategy affect safety decisions?

People-centred safety does not mean replacing technical controls with goodwill. It means treating workers as participants in control design, because the people who perform the task can identify constraints that a policy review misses. Their knowledge becomes useful when leaders give it a route into the decision.

In the episode, Andrea Hernandez described how Siemens evolved its Zero Harm program in 2020 by merging it into Healthy and Safe at Siemens, a more proactive, human-centric approach. The important lesson is not the label of the program. It is the willingness to change a strategy when its original framing no longer helps the organization address its current problems.

That change also creates an accountability test. If a people-centred strategy exists only in leadership language, the workforce will still encounter the old barriers in permits, staffing, escalation, and production planning. Leaders should therefore identify one decision each week in which worker input changed the control, the sequence, the staffing plan, or the authorization to proceed.

What does well-being add to a safety strategy?

Well-being becomes relevant to safety when human capacity is treated as a condition of reliable work. Fatigue, workload, isolation, poor handover, and constant digital interruption can affect whether a person notices a change, challenges an assumption, or asks for help. The issue is not that every difficult day is a safety event. The issue is whether the organization recognizes conditions that make error and silence more likely.

The National Institute for Occupational Safety and Health frames workplace health through the interaction between work conditions and worker well-being. That is a useful anchor for EHS managers who want to move beyond a narrow injury count. A team review can examine four conditions, namely workload, recovery, relationship quality, and decision latitude, while still keeping critical physical hazards visible.

Use a 30-day review rather than a one-off campaign. Ask the team to identify two conditions that make speaking up harder, then examine the response at week 1, week 2, week 3, and week 4. If nothing changes after four checkpoints, the barrier is probably structural rather than motivational.

How does Andrea Hernandez's view compare with the usual approach?

The comparison below separates a declaration-led model from the team-level approach discussed in Episode 8. Neither model removes the need for formal standards. The difference is where leaders look for evidence that the standard is working.

This distinction matters because a team can report high confidence in a survey while still withholding the one concern that would challenge a senior decision. Evidence of trust therefore needs a chain, from the first question through the response and the resulting work change.

What should leaders measure after the conversation?

Measure the quality of the response, not only the quantity of voice. A practical dashboard can contain five indicators: the number of concerns raised, the percentage receiving an owner within 24 hours, the number that changed a control, the time until feedback was given, and the percentage of team members who can describe what happened after a concern was escalated.

These indicators should be reviewed with the team that generated them. If leaders count 12 reports but cannot explain the decision path for any of them, the metric is measuring administrative motion rather than psychological safety. If a team raises 2 concerns and both lead to visible protection, the smaller number may represent a healthier reporting environment than a larger count with no response.

Connect the review to ISO 45003 guidance on psychological health and safety at work, while keeping the local evidence concrete. The standard can support a management system, but the team still has to show whether people can question the plan during the next shift, handover, or production change.

Keep the dashboard small enough to discuss. Five indicators are sufficient for a first cycle because the purpose is to expose the response path, not to create another reporting burden. Ask the team to explain one case in plain language, then compare that account with the supervisor's record and the final control decision. Any gap between those three versions deserves attention.

Recommendation

Start with one team that performs work where silence could hide a serious exposure. Do not begin by asking for a culture score. Ask the supervisor and workers to identify three recent moments in which someone had to decide whether to speak, wait, or stay quiet.

Review each moment in a 45-minute conversation. What was the concern? Who heard it? What happened within 24 hours? Did the control or work sequence change? What did the person who raised it learn about the consequences of speaking? Record the answer without naming blame, then select one barrier that the leader can remove in the next 7 days.

Repeat the review after 2 weeks and again after 30 days. If the team can point to a changed decision, a clearer escalation route, and a respectful response to uncertainty, the organization has created evidence that a global strategy is reaching the work. If it cannot, the next investment should address the barrier rather than promote another slogan.

Conclusion

Andrea Hernandez's contribution to the Headline Podcast is a useful correction to strategy-first safety leadership. Psychological safety is not established when a company names it, measures it, or places it in a global presentation. It becomes credible when the team that shares eight hours of work can raise the next concern and see what follows.

That is why context comes before technology, empowerment comes before confirmation, and well-being belongs in the safety conversation. The leader's task is to make the route from voice to decision visible enough that people can trust it, then disciplined enough that the organization learns from what they say.

Listen to the full conversation with Andrea Hernandez, then test the recommendation with one team before expanding it across the organization.