How Andrea Hernandez Thinks About Well-Being as a Safety Control

Episode 8 of Headline Podcast was published on October 23, 2025, and features Andrea Hernandez, Siemens Global Health and Safety Vice President, in conversation with Andreza Araujo and Dr. Megan Tranter about context-first safety strategy, people-centric leadership, psychological safety, and well-being. Hernandez's central argument is that safety improves when organizations design conditions in which people can work, speak, and recover without treating well-being as a separate initiative.

The idea matters because a polished well-being program can coexist with excessive workload, unclear priorities, poor supervision, and fear of bad news. The meaningful test is not whether the company has a campaign. It is whether the work system makes safer decisions more likely when pressure rises.

Well-being becomes a safety control when it changes work

Well-being becomes a safety control when leaders use it to change the conditions that shape attention, recovery, communication, and judgment. That can include staffing, shift design, workload, supervisor behavior, role clarity, access to help, and the time available to stop and reassess a task. A benefit that leaves those conditions untouched may still be valuable, but it has not yet become a safety control.

Hernandez described the shift in Siemens strategy through a clear distinction. "Our Zero Harm program delivered what we needed at the time", she said, before explaining that the approach evolved in 2020 toward a more proactive, human-centered model. The useful lesson is not the label. It is the willingness to change a program when the operating context changes.

Andreza Araujo makes a similar point in Safety Culture: From Theory to Practice, where culture is visible in repeated organizational choices. If leaders praise well-being while rewarding chronic overload, people learn that the stated priority is decorative and the actual priority is speed.

Strategy only works after it reaches the team

A global safety strategy becomes real only when a team knows what it can question, what support it can request, and what a supervisor will do with an early warning. People do not experience the strategy document directly. They experience a shift handover, a work allocation, a deadline, a correction, and the reaction to a concern.

Andrea Hernandez said, "Psychological safety happens at the team level". She added that people may not speak up in a group of a thousand if they cannot speak up in the small group that shares eight hours a day. That sentence gives leaders a practical boundary. Corporate messaging may set direction, yet the first control test belongs to the local team.

OSHA's worker participation guidance supports the same operating logic because workers need a credible route to identify hazards and influence prevention. Participation is not proven by a survey invitation. It is proven when a worker can raise a concern and see a useful response.

Context prevents well-being programs from becoming theater

Context-first leadership asks what is creating strain in this workforce, at this site, during this change, and for this role. A night-shift team may need recovery and handover redesign. A recently reorganized team may need role clarity and decision rights. A contractor interface may need better planning rather than another resilience workshop.

Leaders should resist copying a program because another business unit reports strong participation. Participation is only one signal, and it can rise while trust falls if people believe the activity is being used to demonstrate compliance. The first diagnostic question is therefore local: what condition makes safe work harder than it needs to be?

NIOSH research and guidance keeps the conversation connected to occupational health rather than reducing well-being to morale. Work organization, exposure, recovery, and prevention belong in the same management conversation when they influence the worker's ability to perform safely.

Compare a benefit program with a safety control

A benefit program and a safety control can use similar language, although they are evaluated differently. The benefit asks whether support is available. The safety control asks whether the work condition that creates risk has changed and whether leaders can verify that change in practice.

The distinction protects both safety and well-being. It prevents leaders from blaming workers for stress that the organization created, while also preventing a well-being label from excusing weak controls, unsafe staffing, or poor supervision.

Technology is not a substitute for human judgment

Technology can support well-being when it helps leaders see workload, improve access to support, or identify a recurring barrier before it becomes a crisis. It can also create new pressure through constant monitoring, unclear scores, and the expectation that workers remain available. The tool has to be judged by the work it changes, not by the sophistication of its interface.

Hernandez said, "When it comes to health and safety I always ask what is the problem we want to solve", adding that implementing technology for its own sake makes no sense. That question belongs at the start of every well-being technology review because the wrong tool can increase surveillance while leaving the original strain untouched.

Use ISO 45001:2018's management-system framework as a governance anchor, then test the human consequences locally. A system that changes data collection but not leadership action is not a complete control.

Leaders should measure response, not optimism

Well-being measurement becomes useful when it shows whether leaders responded to the condition workers identified. A high score can coexist with silence if people believe nothing will change. A lower score can be valuable when it reveals a constraint that leaders can remove and then verify.

Review five signals over 30 days. Track unresolved workload constraints, the time between a concern and a response, the quality of supervisor follow-through, the number of decisions changed after worker input, and whether the affected team says the intervention made safe work easier. These are management signals, not a clinical diagnosis.

The review should also protect privacy. HSE's work-related stress guidance reinforces the need to address work factors rather than placing the entire burden on individual coping. Leaders should not use a well-being measure to identify a supposedly weak worker when the real issue is an overloaded system.

Recommendation

Run a 30-day well-being control review in one team before launching a broad campaign. During days 1 to 5, ask workers which work condition most often makes safe execution harder, and document the supervisor response that currently follows. During days 6 to 10, select one change in workload, handover, role clarity, recovery, or escalation. During days 11 to 24, observe whether the change survives real operating pressure. During days 25 to 30, review worker experience and decide whether to scale, redesign, or stop.

Keep five records: the local problem statement, the worker evidence, the named owner, the changed condition, and the verification result. If the review produces only attendance figures or positive comments, the intervention has not yet demonstrated control value.

Connect the review with the work redesign versus manager support comparison, the job strain explainer, and the workload calibration meeting guide. Those resources help leaders decide whether the response belongs in work design, supervisor practice, or targeted support.

Andrea Hernandez's argument is practical because it makes well-being accountable to the same question as every other safety control: what changed in the work, and how do we know? The answer begins at team level, where people decide whether to speak, pause, ask, and trust the response.

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