How a 19-Country Operation Turned Workload Into a Management Decision in 90 Days

In a 19-country operation, psychosocial risk stops being abstract as soon as workload, conflict, and return-to-work decisions affect whether the next shift can work safely. The real question is not whether support exists. It is whether one manager owns the decision that changes the job.

This case study is for HR, EHS, and operations leaders who still see psychosocial issues as a support-service problem. If you need the mechanics of the authority model, the decision-rights matrix guide shows how to assign owners without turning every issue into a committee case.

Across 25+ years leading EHS at multinationals, Andreza Araujo has seen the same pattern repeat. The company responds to distress, then leaves the work design untouched. In more than 250 cultural transformation projects, the fix only held when leaders changed the decision path, not only the message.

Initial scenario

The operation in this case was large enough that nobody could pretend the problem was local noise. The leadership system had to work across 19 countries, 30,000 employees, 34 factories, and 60+ distribution centers, which meant one weak decision could travel quickly through many sites. Workload complaints were appearing, but they were being handled as support requests instead of control signals.

That is the first trap. When workload sits in HR language, operations keeps treating it as something soft, personal, or temporary. The field experiences something else. People receive the same deadlines, the same role ambiguity, the same conflict, and the same incomplete handoffs, which means the risk stays alive even when the conversation sounds caring.

As Andreza Araujo argues in A Ilusão da Conformidade, translated as The Illusion of Compliance, formal order can look clean while the real exposure stays in the work. ISO 45003:2021 points in the same direction because psychosocial risk is tied to work organization, social relationships, and the environment that shapes them. A policy is not a control if the job still produces the same pressure tomorrow.

Decision

The leadership shift was not to launch a bigger awareness campaign. The decision was to stop asking who needed help and start asking who could change the job. That sounds small until you see how many cases move through a company before anyone asks that question. Once the team changed the question, the whole conversation moved away from support alone and toward named ownership.

The next step was to separate three issues that had been mixed together for too long. Workload adjustments, conflict escalation, and return-to-work review were no longer allowed to sit in one informal queue. Each of those decisions needed a clear owner, a response time, and a way to prove that the work condition actually changed. If you want that logic in template form, the decision-rights matrix article is the practical companion.

That change mattered because supervisors often receive a distress signal and then send the person to support without changing the work that created the signal. The better sequence is different. Listen, protect the person, change the job where needed, and only then close the loop. The article on return-to-work decisions shows why the handoff fails when the job side is ignored.

Execution

The execution phase worked because it was simple enough to survive a real operation. The team mapped the most repeated psychosocial triggers, named the owner for each trigger, and fixed one review path that could move across borders without waiting for a monthly committee. In practice, that meant the line leader, HR, EHS, and occupational health each knew what they had to do before the case drifted into delay.

The most important rule was that every case needed a work decision, not just a support referral. If the issue was workload, the manager had to review priorities, sequencing, staffing, or deadlines. If the issue was conflict, the supervisor had to address the relationship and the local conditions that kept it alive. If the issue was return to work, the team had to verify what would change in the schedule, the demand, or the supervision before the employee came back.

This is the point where many organizations fail. They call the case closed because the person got a conversation, a note, or a referral. That is not closure. It is documentation. Andreza Araujo's view in Safety Culture: From Theory to Practice is useful here because repeated decisions, not polished language, reveal the culture. If the decision does not change the job, the job is still the control problem.

That structure is also why the related guide on auditing psychosocial risks in 30 days matters. A review can expose the pressure points, but a decision-rights model is what keeps the review from becoming another file that nobody owns.

Measured result

The measured result was not that every issue disappeared. The result was that five recurring decision gaps stopped reappearing in different forms. The operation no longer treated workload, conflict, return to work, escalation timing, and job change as separate conversations that could be postponed indefinitely.

That shift is important because organizations often celebrate awareness while the same pattern keeps repeating. A training session can make people more articulate about stress, but it does not move deadlines, redistribute work, or clarify authority. In more than 250 cultural transformation projects, Andreza Araujo has seen that a psychosocial problem improves only when the operating system changes the same week the problem is named.

The scale of this case also mattered. In a 19-country operation, one local success is not enough if the decision model stays vague. Once the manager, the supervisor, and the support function had different but connected responsibilities, the operation could act faster without turning every case into a crisis.

Generalizable lessons

The first lesson is that psychosocial risk is a management issue before it is a wellbeing issue. That does not make it cold. It makes it workable. If the company cannot name who can change workload, conflict, or return-to-work conditions, then the organization has created support without control.

The second lesson is that support without work change only manages symptoms. Workers may value the help, but they still pay the price of the unchanged job. That is why the market's favorite shortcut, awareness plus referral, usually fails under pressure. Andreza Araujo's book A Ilusão da Conformidade is a reminder that formal gestures can look responsible while the underlying exposure remains untouched.

The third lesson is that return-to-work belongs inside the control system. If the same demand pattern, the same conflict, or the same schedule returns, the case is not really closed. It is paused. The practical bridge between support and control is the supervisor, which is why Make The Difference: Be a Leader in Health & Safety matters for line managers who need to own the next decision, not just receive the report.

If psychosocial risk only gets attention after absence, turnover, or a formal complaint, the operation is still paying for silence instead of managing the cause.

What to apply in your operation

If you want to use this case without copying it, start with four actions that can be tested in one month.

1. Name one manager who owns workload escalation for the highest-risk team.
2. Set one review window, ideally within 48 hours, for workload, conflict, and return-to-work cases.
3. Require one work change before a case can be called closed, even if the person also received support.
4. Check whether the worker can describe what changed in the job, not only who listened to the concern.

The point is simple. When psychosocial risk is tied to a named decision, the organization stops treating the problem like a general mood and starts treating it like an operating condition. If you want help turning that into a site-level method, Andreza Araujo and ACS Global Ventures can help you turn the logic into a diagnostic and a working routine.