How Andrea Hernandez Thinks About Context Before Compliance in Safety

Episode 8 of the Headline Podcast, published on October 23, 2025, features Andrea Hernandez, Siemens Global Health & Safety Vice President, discussing why safety leadership must begin with context instead of compliance alone.

Her central argument is that a global safety strategy becomes credible when leaders define the problem, involve the people closest to the work, and test whether the team can speak before a corporate metric changes.

Why context must come before the safety program

Context-first safety leadership means identifying the actual exposure, decision, and work condition before selecting a program, technology, or message. Compliance can establish a floor, but context determines whether that floor protects anyone during the task.

Andrea Hernandez described the evolution of Siemens' approach after the company's Zero Harm program served its purpose and merged into Healthy and Safe at Siemens in 2020. The point is not that a previous program was worthless. The point is that a strategy can become less useful when the organization keeps applying yesterday's language after the work, expectations, and risks have changed.

That distinction matters for leaders who inherit a mature management system. A policy may be current, the training record may be complete, and the audit score may be green, while the team still lacks the time, authority, or equipment needed to control the exposure. The program is present, yet the decision remains unsupported.

The OSHA safety and health management guidance places management leadership, worker participation, hazard identification, and continuous improvement in the same system. That arrangement supports Hernandez's practical question, because a leader cannot evaluate a safety program by its label while ignoring the conditions in which people use it.

1. Start with the problem, not the solution catalogue

Before approving a new app, sensor, campaign, or training package, name the problem in operational terms. A clear problem statement identifies who faces the exposure, when it appears, what decision is difficult, and what evidence would show that the response worked.

In the episode, Hernandez asks what problem the organization wants to solve before it implements technology. That question interrupts a common leadership shortcut. Leaders see a product demonstration, recognize a familiar risk label, and assume that adoption is progress. The work then changes only on paper.

A useful problem statement has at least four parts. It describes the work condition, the consequence that matters, the decision that currently fails, and the control that should become more reliable. If a team reports repeated uncertainty during a handover, the problem is not simply “communication.” It may be an unclear release authority, missing information, incompatible schedules, or a supervisor who cannot stop the work.

Use evidence from the field before choosing the intervention. The NIOSH hierarchy of controls reminds leaders to examine elimination, substitution, engineering, administrative, and personal protective measures in order. That sequence prevents a technology purchase or awareness campaign from becoming the first answer to a design problem.

2. Translate global principles into local decisions

A global safety principle becomes useful only after a local team can explain how it changes a real task. Translation is not dilution. It is the work of matching the principle to exposure, language, authority, resources, and the pace of the operation.

Global organizations need common expectations, but common wording does not create common conditions. A distribution center, engineering office, laboratory, and production line may all use the word “engagement” while facing different interruptions, controls, and opportunities to pause.

Leaders should therefore ask each team to convert the principle into one visible decision. What can a worker stop? Which supervisor must respond? What information must cross the boundary? When does a local exception require escalation? The answers reveal whether the global strategy has reached the work or remains at headquarters.

That translation also belongs in the decision rights that keep critical risk owned, because a principle without an accountable role becomes a request that everyone supports and nobody can execute.

This is where a standard such as ISO 45001 can help without becoming a substitute for judgment. Its management-system structure creates expectations for leadership, participation, planning, and improvement, yet the organization still has to decide how those expectations work in a particular process.

3. Test psychological safety in the eight-hour team

Psychological safety is not proven by a company-wide statement or a single survey score. It is tested when a person can question a decision, admit uncertainty, or raise a weak signal with the small group that shares the work for eight hours.

Hernandez makes the team-level point directly. People will not automatically speak in a group of 1,000 if they cannot speak in the smaller group they work with every day. Scale can distribute a message, but it cannot manufacture trust at the point where a concern first becomes socially risky.

The supervisor is therefore a critical measurement point. Ask whether the team can name a recent concern that changed the plan, whether the person who raised it was treated with respect, and whether the response was visible. Those questions reveal more than asking whether leaders “support speaking up” in general.

A practical two-week test is small enough to run and specific enough to learn from. During the first week, collect concerns from shift meetings and one-to-one conversations. During the second, review which concerns received an owner, a decision, and a return message. The count is less important than the quality of the response.

For a broader measurement lens, compare this team-level test with six tests that separate participation from permission-seeking. The aim is not to reward more comments. It is to make the response to a comment safer and more useful.

4. Make well-being part of the operating system

Well-being becomes a safety control when leaders change the conditions that shape attention, recovery, dignity, and decision quality. It remains a campaign when the organization asks people to cope while leaving workload, staffing, authority, and schedule pressure untouched.

Hernandez connects well-being with company strategy rather than treating it as a separate benefit. That move changes the executive question. Instead of asking whether employees attended a session, leaders ask whether the work allows people to recover, request help, and make a safe decision when demand rises.

The ISO 45003 guidance on psychological health and safety gives organizations a way to examine psychosocial conditions within the management system. The useful application is not to create a larger checklist. It is to connect workload, role clarity, relationships, change, and support to the decisions that protect people.

A leader can make this concrete by reviewing four operating conditions each month: workload, recovery time, decision authority, and access to support. A change in one condition should trigger a conversation about task allocation and controls, especially when fatigue or pressure affects a high-consequence decision.

5. Replace declared values with observable design choices

A value becomes credible when a leader can point to a decision that protects it under pressure. “People first” should be visible in staffing, stop-work authority, escalation time, design review, and the response to bad news.

Safety language becomes fragile when it stays abstract. Teams hear that people matter, then discover that production deadlines still decide whether a concern receives attention. The gap is not solved by repeating the value with more confidence. It is solved by changing the decision path.

Choose one high-consequence decision and map the five moments around it. Who sees the condition? Who can pause the work? Who has technical authority? Who receives the escalation? Who verifies the restart? This map shows whether the stated value has a practical route through the organization.

The same discipline applies when a leader reviews a safety decision memo for a capital project. The document should expose who owns the decision and what evidence will change it, rather than simply restating the value statement.

The U.S. Bureau of Labor Statistics injury and illness data can describe outcomes, but outcome data cannot show whether a team had the authority to prevent a particular exposure. Leaders need both the result and the operating evidence that explains what people could do before harm occurred.

Comparison: compliance-first versus context-first leadership

Compliance-first leadership asks whether the required element exists. Context-first leadership asks whether the element changes the decision in the work, remains usable under pressure, and produces evidence that the exposure is better controlled.

The table does not reject compliance. It shows where compliance stops. A required element can be necessary while still failing to answer the operational question that matters. Leadership earns credibility when it closes that gap rather than defending the element as proof of control.

Recommendation

Select one team, one high-consequence decision, and one recurring safety concern. Spend 30 days tracing the concern from first signal to leadership response, then change the work condition that made the concern difficult to raise or resolve.

Begin with two conversations in week 1. Ask the team what problem repeatedly makes a safe decision harder, and ask what would make speaking up easier. In week 2, verify the evidence with the supervisor and control owner. In week 3, implement one change with a named owner. In week 4, return to the team and test whether the decision is now clearer.

Andrea Hernandez's Episode 8 message is a useful challenge for leaders who have accumulated programs faster than they have improved decisions. Context does not replace standards, technology, or accountability. It tells leaders where those tools belong and whether they are doing the work people need them to do.

Listen to the full Episode 8 conversation with Andrea Hernandez for the discussion behind this approach. The strongest safety strategy is not the one with the most visible machinery. It is the one that helps a real team understand the problem, question the control, and act before the exposure becomes harm.