How Andrea Hernandez thinks about psychological safety in teams

Episode 8 of Headline Podcast, published on October 23, 2025, brought Andrea Hernandez of Siemens into conversation with Andreza Araujo and Dr. Megan Tranter about global safety strategy, well-being, technology and psychological safety. Hernandez's central thesis is that psychological safety becomes operational at team level, where people decide whether it is safe enough to speak before risk becomes formal.

That matters because many companies discuss psychological safety as a broad cultural aspiration while workers experience it in a much smaller place: the shift, crew, project room, maintenance team or supervisor relationship that shapes the next 8 hours of work.

Key Takeaways

• Episode 8 frames psychological safety as a team-level condition, not only a company-level value.
• Team voice is tested when workers challenge a plan, a technology rollout, a workload decision or a weak control.
• Leaders should measure response quality within 24 hours, not only annual perception scores.
• Technology can support safety only when people can question the tool without being labeled resistant.
• The practical output is a 30-day team voice review with named owners and visible follow-through.

Why does Andrea Hernandez place psychological safety inside the team?

Andrea Hernandez places psychological safety inside the team because the team is where voice becomes costly or useful. A worker may trust the corporate message and still stay silent if the immediate supervisor mocks concerns, if the crew punishes delay, or if prior reports disappeared without a visible answer.

On Headline Podcast, Hernandez said, "Psychological safety happens at the team level, people won't speak up in a group of a thousand if they can't speak up in the small group they share eight hours a day with." The line is useful because it moves leaders away from abstract culture language and toward the social unit where safety information either travels or dies.

OSHA describes worker participation as a core element of safety and health programs, including involvement in hazard identification, evaluation and improvement. Participation becomes real only when a person believes the local team will not punish the concern before management has a chance to act.

This is why Headline's article on psychological safety audits should be read through a team lens. The audit does not ask whether the company says the right words. It asks whether the crew can name the unsafe assumption while work is still changeable.

What changes when leaders stop treating voice as a campaign?

When leaders stop treating voice as a campaign, they begin testing the response system that workers actually experience. Posters, town halls and annual surveys can invite speaking up, although the local response after the first uncomfortable concern decides whether the second concern will ever be raised.

Episode 8 matters here because Hernandez does not separate people-centric leadership from operational discipline. A team that can challenge a plan can also protect the standard more effectively, because weak signals arrive before the procedure fails, the alarm sounds or the incident report is opened.

ISO identifies ISO 45001:2018 as the occupational health and safety management-system standard, and its leadership, consultation and participation requirements give EHS leaders a useful anchor. A management system cannot depend only on documents if workers do not feel able to challenge the work conditions those documents are supposed to control.

Across 25+ years leading EHS in multinational environments, Andreza Araujo has seen that culture appears in repeated decisions under pressure. In practical terms, the team learns from what happens after a concern interrupts the job, not from the sentence printed in the leadership deck.

How does technology test team psychological safety?

Technology tests team psychological safety because it changes pace, visibility, autonomy and trust. A wearable, camera system, dashboard, scheduling tool or digital permit may reduce one exposure while creating another if workers believe the tool cannot be questioned.

Hernandez gave a clear technology rule in the episode: "When it comes to health and safety I always ask what is the problem we want to solve, implementing technology just for the sake of technology makes no sense." That rule protects psychological safety because it invites the team to discuss the work problem before the organization falls in love with the solution.

For Headline readers, this connects directly with psychosocial risk from technology. A technology rollout can produce 3 voice risks at once: workers may fear surveillance, supervisors may defer judgment to the tool, and the team may stop reporting exceptions because the dashboard looks authoritative.

NIOSH explains that psychosocial hazards should be addressed through prevention approaches that include organizational-level interventions. That matters because a team cannot speak freely about technology if the rollout gives them no route to alter pace, data use, privacy boundaries or human override.

Comparison: corporate psychological safety vs team psychological safety

The comparison below helps leaders separate a broad aspiration from evidence that can be checked during one month of work. Both levels matter, but only the team-level view shows whether a worker can use voice at the exact moment when risk is still preventable.

The table prevents a common trap. Psychological safety is not measured by how warmly the company talks about people. It is measured by whether a person can raise bad news in the small group that controls the next decision.

Where does well-being connect with voice?

Well-being connects with voice because psychological strain often changes what people are willing or able to say. A tired, overloaded or uncertain team may still complete forms and attend meetings while withholding doubts, objections and early warnings that could have changed the work.

Episode 8 is useful because Hernandez links safety, well-being and company strategy rather than treating them as separate programs. That connection matters in high-pressure operations where role ambiguity, technology change and workload can silence people before a formal mental-health case appears.

The existing Headline article on Siemens well-being strategy explores the 4-question score as a leadership signal. This episode companion adds the team-level question: does the score lead supervisors to change work conditions, or does it become another number that people cannot safely explain?

BLS records occupational injury and fatality data each year, which should remind leaders that late harm indicators cannot be the first proof that voice was weak. Psychological safety matters before injury data moves, because it decides whether weak signals reach a person with authority.

What should EHS managers test in the first 30 days?

EHS managers should test whether one exposed team has 3 practical voice routes, a supervisor response standard, and visible follow-through. The review should be small enough to run in 30 days and specific enough to expose the gap between the declared culture and the team experience.

Start with one team facing real tradeoffs, such as maintenance under shutdown pressure, logistics under time pressure, a technology pilot, a contractor interface or a high-energy task group. Review 10 recent concerns, interview 6 workers across 2 shifts, and ask whether the original concern changed as it moved upward.

The review should connect to safety reporting channels, but it should not stop at channel availability. A hotline, open door or safety representative is only useful when the team sees that the message produced action, explanation or a protected decision.

The strongest evidence is visible in return answers. Did the supervisor respond within 24 hours? Did the manager preserve uncomfortable language instead of softening it? Did the team see one control, schedule, staffing, privacy or escalation change within the month? If not, the company may have a voice process without voice confidence.

Recommendation

Senior EHS leaders should use Episode 8 to move psychological safety from corporate language into a 30-day team voice review. Pick one team, map the work pressure, review the last 10 concerns, test the response path, and ask whether workers can challenge technology, pace, staffing and control quality without being treated as negative.

The review should end with 4 decisions: which concern route will be protected, which supervisor response will be standardized, which technology or workload issue needs redesign, and which leader will return to the team with the answer. If the output is only communication, the review has missed Hernandez's point.

Every month that psychological safety stays at slogan level allows small teams to keep filtering risk in private, while leaders believe the organization is more open than the work actually feels.

Andrea Hernandez's Episode 8 gives safety leaders a practical way to discuss voice, technology and well-being where they are tested first: inside the team. Listen to the full conversation.

Team-level psychological safety also needs a practical route for concerns that workers cannot yet raise openly. The companion workflow for anonymous safety reports turns that team-level voice problem into triage, verification and closure steps.