How Siemens Put Well-Being Into Company Strategy With a Four-Question Score

A well-being program can exist for years without changing the work that makes people unwell. It can have a polished name, a strong launch, and a library of resources while employees still face unclear priorities, relentless change, poor recovery, or leaders who punish bad news. The Siemens example discussed by Andrea Hernandez on the Headline Podcast takes a different route. It treats well-being as part of company strategy and gives leaders a comparable signal that can be reviewed with the same seriousness as other operating conditions.

The important lesson is not that a four-question score solves workplace mental-health risk. It does not. The lesson is that measurement becomes useful when it is attached to decisions about how work is designed, led, and supported. That distinction matters for EHS and HR teams that are asked to improve well-being without the authority to change the conditions employees experience every day.

Why a well-being program needs an operating model

Many organizations respond to mental-health concerns by adding resources around the existing system. They promote an employee assistance program, publish coping guidance, schedule a resilience workshop, or ask managers to remind people to take breaks. Those actions may help some employees, yet they do not answer the management question that sits underneath the signal. What in the work is creating strain, and who has the authority to change it?

Andreza Araujo's work across more than 250 cultural transformation projects provides a useful safety-culture lens for this question. Declared concern is not the same as operated care. Employees judge the organization through scheduling, staffing, supervisory response, decision speed, and what happens when someone says that the plan cannot be executed safely.

Siemens' approach is relevant because it moves well-being from a peripheral activity into the company strategy. That move changes the conversation from whether people know about support to whether the organization is creating conditions in which support can be used before a crisis.

What the Siemens example changed

The case has two connected parts. First, well-being became a company-level concern rather than a subject reserved for the safety function. Second, Siemens used a comparable four-question well-being score, which gave leaders a consistent way to see the signal across the organization and over time.

The four questions are not presented as a clinical assessment. They are a management listening instrument. A short score can show whether a team is experiencing a deteriorating condition, but the score cannot explain whether the cause is workload, role ambiguity, leadership behavior, weak recovery, personal circumstances, or a combination of factors. Leaders still have to investigate the work system without turning the survey into a label for individuals.

That separation protects the quality of the conversation. The score identifies where leaders should look. It does not give them permission to assume why the result occurred.

How the four-question score becomes useful evidence

A recurring score creates a baseline, but a baseline is only the beginning. Leaders should compare the result with operational evidence that can confirm or challenge the story. Relevant evidence may include overtime patterns, vacancy duration, schedule instability, absence trends, turnover, incident reporting, near-miss follow-up, change volume, and the time supervisors can protect for planning and recovery.

None of these measures should be treated as a substitute for conversation. A team may report a stable score while people have stopped expecting anything to change, or the score may fall because employees finally feel safe enough to describe the pressure. That is why the interpretation needs local interviews and field observation, with questions that connect the result to actual work.

Why company strategy matters more than a safety campaign

When well-being sits only inside a safety campaign, the organization can unintentionally make the problem look individual. The message becomes one of awareness, self-care, or personal resilience, even when the pressure comes from conflicting objectives, chronic understaffing, constant technology change, or a leader who treats every concern as a performance problem.

Placing well-being in company strategy creates a broader accountability map. Operations owns the design of work. HR owns people systems and workforce planning. EHS connects mental and physical risk to the way tasks are planned and performed. Senior leaders decide which trade-offs are acceptable when output, speed, and recovery compete.

This is also consistent with ISO 45003, published in 2021, which frames psychosocial risk as a work-related issue requiring attention to organizational conditions. The standard does not turn every difficult day into a diagnosis. It does require leaders to examine how work is organized, managed, and experienced.

What leaders must not do with the score

The first trap is treating the score as a ranking system. If teams believe that a poor result will make their manager look weak, they have a reason to soften the answer or avoid the survey. The instrument then measures political safety rather than well-being.

The second trap is launching a communication response before understanding the work. A new poster about balance cannot compensate for a schedule that removes recovery, and an optional workshop cannot resolve a role conflict that has two executives giving opposite instructions.

The third trap is asking EHS or HR to own the entire response without giving those functions decision rights. A function can coordinate evidence and convene the review, but the manager who controls staffing, sequencing, priorities, and supervisor conduct must own the correction.

These traps are why James Reason's distinction between visible actions and latent conditions remains useful. A poor well-being result is visible evidence. The conditions that made it likely may sit in planning, governance, incentives, or leadership routines that are harder to see.

How to turn a weak result into a management decision

Leaders can use a five-part review after each measurement cycle. Start by locating the result by team, role, shift, site, or work pattern, while protecting confidentiality. Then identify the operational changes that preceded the result. Ask employees what makes the work harder than the formal process suggests, and compare that account with staffing, workload, overtime, and change data.

Next, name the decision owner. If the cause is conflicting priorities, the executive sponsor must resolve the conflict. If the cause is role ambiguity, the line leader must clarify authority and interfaces. If the cause is a recovery problem, operations must change the schedule or capacity instead of telling people to manage fatigue better.

Close the review with a verification plan. The organization should record what changed, who owns it, when the team will feel the effect, and which evidence will show whether the response worked. A later score can support the review, but it should be accompanied by direct feedback and observable changes in the work.

What EHS and HR can learn from the case

The Siemens example gives EHS and HR a practical boundary. They should not promise to solve every source of distress, and they should not reduce a complex work condition to a wellness metric. Their role is to make the exposure visible, protect the quality of the listening process, connect the signal to safety and organizational evidence, and bring the accountable decision-maker into the room.

For EHS, that means treating psychological health as part of the conditions that shape safe performance, reporting, attention, and recovery. For HR, it means connecting employee experience to staffing, management capability, role design, and change governance. For operations, it means accepting that a well-being signal can require a change to the operating plan rather than a better message.

Across 25+ years of EHS leadership, Andreza Araujo has consistently emphasized the gap between a value that is declared and one that survives pressure. The same test applies here. A company can declare that people matter, but employees learn whether that statement is real when workload rises, a deadline moves, or someone says that the current plan is not safe or sustainable.

Measured well-being is only the beginning

Siemens' model is valuable because it makes well-being visible at the level where company strategy is discussed. The comparable four-question score creates a shared signal, and the company-level framing makes it harder to dismiss mental health as a private issue or a benefits topic. The result is not a perfect measure. It is a better starting point for accountable management.

Leaders should use the score to ask better questions, then change the conditions that the questions reveal. When the response remains limited to awareness, the organization has measured concern without reducing the exposure. When the response changes priorities, workload, role clarity, recovery, or leadership behavior, well-being becomes part of how the company operates.

Explore more practical workplace safety and leadership analysis on the Headline Podcast blog and learn more about Andreza Araujo's books and resources at Andreza Araujo's store.