8 checks from Episode 8 with Andrea Hernandez

Episode 8 of Headline Podcast featured Andrea Hernandez, Siemens Global Health and Safety VP, published on October 23, 2025. Her central argument was that psychological safety becomes operational only when it reaches the small team where people spend their shift, not when it stays in a corporate value statement.

Team-level safety voice is the everyday ability of workers to raise risk, doubt, bad news, and weak signals inside the crew where work is planned and executed. It matters because most hazards are first noticed by the people closest to the task, before they appear in dashboards, audits, or injury statistics.

1. Why does psychological safety have to reach the team?

Psychological safety has to reach the team because the crew is the first place where a hazard is noticed, tested, normalized, or challenged. In Episode 8, Andrea Hernandez described psychological safety as something that happens at team level, which matters because a worker who cannot speak up among 8 or 12 familiar colleagues will not suddenly become candid in a town hall of 1,000 people.

On Headline Podcast, Andrea Hernandez said, "Psychological safety happens at the team level." That line changes the managerial question. Instead of asking whether the company has a speak-up policy, the EHS leader should ask whether a maintenance crew, a night-shift team, or a contractor interface meeting can absorb inconvenient information without humiliating the person who raised it.

OSHA explains in its worker participation guidance that effective safety and health programs depend on workers feeling comfortable reporting concerns and participating without retaliation. That is not a soft aspiration. It is the practical condition under which the organization receives information early enough to act.

Andreza Araujo's work in more than 250 cultural transformation projects points to the same operational truth: culture is not what leaders announce, but what supervisors tolerate, reward, and interrupt in the moments when production pressure makes silence convenient.

2. What changed when Siemens moved beyond Zero Harm language?

Andrea Hernandez explained that Siemens moved its former Zero Harm program into Healthy and Safe at Siemens in 2020, with a more proactive and human-centered approach. The important lesson is not the program name, because names change; the lesson is that a safety strategy has to mature when the risk profile changes, especially when mental health, work design, and technology reshape how people experience risk.

On Headline Podcast, Andrea said, "Our Zero Harm program delivered what we needed at the time." She then described the evolution toward a broader model. That distinction is useful for C-level leaders who still defend old safety language because it once worked. A slogan can age even when the original intent was sincere.

This is where safety silence motives become a strategic issue rather than a communications issue. If the old language tells people to bring every concern but the local reaction punishes friction, employees learn that the real standard is not honesty. It is harmony.

As Andreza argues in A Ilusao da Conformidade (The Illusion of Compliance), conformity can look like control while quietly hiding the workarounds that make the operation fragile. The trap for leaders is believing that a mature brand vocabulary means mature field behavior.

3. The first check is whether workers can disagree before the job starts

The first check is the quality of pre-job dissent. A psychologically safer team can challenge a permit, a method statement, a lift plan, or a maintenance sequence before work starts, while a weaker team waits until the hazard has already become expensive. In high-risk work, the difference between those 2 moments can decide whether the organization learns from a weak signal or from an incident.

A practical EHS manager should listen for 3 kinds of disagreement during the pre-task briefing: doubt about the plan, doubt about the conditions, and doubt about the crew's readiness. If the only voices heard are the supervisor and the most experienced technician, the meeting is not a risk review. It is a ritual.

This article's angle is deliberately narrow. It does not treat psychological safety as a company mood. It treats it as an information system that either moves field knowledge upward or traps it inside the crew until a near miss, quality failure, or injury exposes what people already suspected.

4. The second check is whether reporting channels fit real fear

Reporting channels only work when they match the fear level of the workforce. OSHA was created through the Occupational Safety and Health Act of 1970, and its current guidance still emphasizes worker participation, anti-retaliation protection, and access to information. A hotline, an open door, and a worker representative do not solve the same problem.

The recent Headline article on safety reporting channels makes this distinction explicit. Anonymous channels help when fear is high, open-door routes help when trust already exists, and representative systems help when the workforce needs structured voice in decisions that affect work design.

The common mistake is adding channels without asking why people are silent. If workers fear retaliation, public praise for speaking up may not be enough. If workers believe nothing changes, anonymity will not fix the credibility gap. If contractors feel disposable, the client must change how contractor input enters planning.

2,488,400 private-industry injury and illness cases were reported in 2024, according to the U.S. Bureau of Labor Statistics. That number is not only a recordkeeping fact. It is a reminder that large systems still depend on people deciding whether to report what happened, what almost happened, and what may happen next.

5. The third check is whether technology increases voice or reduces it

Technology should increase the quality, speed, and reach of worker voice, not replace the human judgment that notices risk. Andrea Hernandez was clear in Episode 8 that technology for its own sake makes no sense; the starting point is the problem the organization wants to solve, not the novelty of the tool. This matters more in 2026 because EHS systems now collect more data than many teams can interpret.

On Headline Podcast, Andrea said, "What is the problem we want to solve?" That is a hard question for any leadership team that has bought platforms before defining the decision those platforms should improve. A reporting app, AI prompt, or dashboard can widen participation, although it can also make people feel watched if the local culture is punitive.

That is why psychosocial risk from technology belongs in the same conversation as safety voice. New tools change workload, surveillance pressure, role clarity, and the perceived cost of saying something unpopular. In a team with low trust, even a well-designed tool can be read as another way to monitor compliance.

NIOSH describes the Worker Well-Being Questionnaire as an integrated assessment of worker well-being across multiple spheres, including quality of working life and health status. The 2026 update reinforces the same logic Andrea used: if the system only measures physical exposure, it misses a significant part of how work affects people.

6. How should ISO 45003 shape the discussion?

ISO 45003:2021 should shape the discussion by treating psychological health and psychosocial risk as part of the occupational health and safety management system, not as a side program owned by HR. The standard has 23 pages and connects directly to ISO 45001, which means psychological safety, work design, role clarity, workload, and participation belong inside governance, audit, and continual improvement routines.

ISO states that ISO 45003:2021 gives guidelines for managing psychosocial risk and promoting well-being at work within an OH&S management system. That matters because team-level voice is not only a cultural preference. It is evidence about whether psychosocial hazards can be detected where they arise.

The practical move is to connect the episode's message to an existing risk process. When a team reports role ambiguity, constant rework, intimidation, impossible deadlines, or fatigue, the EHS function should not file the concern as attitude. It should classify the condition, assign ownership, and verify whether controls changed the work.

The comparison in ISO 45003 vs HSE vs TWH is useful here because each model answers a different leadership question. ISO 45003 gives the management-system lane, HSE stress standards give a diagnostic lens, and NIOSH Total Worker Health adds work design and well-being integration.

7. The fourth check is whether leaders can hear bad news without defending themselves

The fourth check is leader response. A team becomes safer to speak in when the first reaction to bad news is curiosity, not self-protection. In a 15-minute field conversation, the supervisor can either lower the cost of truth or teach everyone that future concerns should be edited before they travel upward.

Andrea's episode sits close to a broader Headline theme: silence is rarely empty. It often contains unshared risk, unspoken doubt, and social calculations about what happens to the person who interrupts momentum. James Reason's work on latent conditions helps frame this without blaming the operator, because many unsafe choices make sense inside systems that reward speed, certainty, and obedience.

Andreza's book Safety Culture: From Theory to Practice argues that leadership credibility is built in repeated observable decisions. In practical terms, a leader who asks for candor and then explains why the concern is inconvenient has just made a cultural decision, even if no one records it.

A useful rule for senior managers is to audit 5 recent moments when bad news reached the line. Ask who raised it, how fast it was acknowledged, what changed, and whether the person would raise it again. If that fourth answer is uncertain, the system has not earned the information it needs.

8. Comparison: status quo versus team-level safety voice

The status quo treats psychological safety as a climate score, while team-level safety voice treats it as a control pathway. This difference matters because a favorable survey can coexist with a crew that edits bad news in front of a powerful supervisor, especially when local incentives reward speed and month-end performance more visibly than interruption.

This is also why safety culture dashboard design has to include evidence of voice quality, not only lagging outcomes. A dashboard that rewards low complaint volume can make silence look like maturity.

Recommendation

The recommendation from Episode 8 is to audit psychological safety at the team level before buying another tool, launching another campaign, or asking workers to be more courageous. Start with 3 crews, review 10 recent concerns, check whether each concern had an owner and a closeout date, and ask whether the person who raised it would do so again.

Senior EHS leaders should then connect those findings to ISO 45003:2021, worker participation practices, and the safety dashboard. 30 days is enough to see whether concerns are being converted into controls, although it is not enough to declare a culture transformed.

Conclusion

Andrea Hernandez's episode matters because it moves psychological safety from a corporate statement to the exact room where risk is named, negotiated, and sometimes buried. If team-level voice is weak, the organization is not short of communication channels; it is short of trustworthy local reactions.

Listen to the full conversation: Episode 8 with Andrea Hernandez on Headline Podcast.