Unilever EHS Case: 5 Handoffs That Kept 19 Countries Aligned

A regional safety leader can publish one standard, schedule one leadership call, and still operate nineteen different safety systems. The gap appears at the handoffs, where a corporate expectation becomes a plant decision, a plant decision becomes a supervisor routine, and a supervisor routine becomes evidence from the field.

Andreza Araujo’s Unilever LATAM case is useful because its operating scope was large enough to make that problem visible. Her documented executive history covers 19 countries, 30,000 employees, 34 factories, and more than 60 distribution centers during her 2014 to 2016 tenure as Director SHE LATAM. The lesson is not that one playbook solved every local problem. The lesson is that scale requires explicit handoffs, otherwise ownership fragments while the reporting structure still looks coherent.

In a multi-country safety system, a governance handoff is the defined transfer of intent, decision authority, evidence, and follow-up between corporate, country, site, and frontline levels. The Unilever case shows why these transfers must be designed as operating routines rather than left to goodwill, personal relationships, or periodic reporting.

Why the Unilever case matters beyond its company name

The Unilever case matters because the operating span created different failure conditions at the same time. Nineteen countries could share a corporate expectation while facing different legal duties, languages, production profiles, contractor interfaces, and leadership habits.

Andreza Araujo’s documented scope is a useful boundary for the case. It identifies a regional SHE leadership role across 30,000 employees, 34 factories, and more than 60 distribution centers, not a single-site improvement story. That distinction changes the management question. A plant can correct a weak routine through direct observation; a regional leader must make the correction transferable without turning it into a slogan.

The analysis below separates documented facts from practical synthesis. The five handoffs are a leadership model derived from the case scope and from the principles Andreza develops in Safety Culture: From Theory to Practice. They should be tested against local evidence before adoption.

Handoff 1: Convert the corporate promise into local risk decisions

The first handoff is complete only when a corporate safety priority becomes a local decision about work, resources, and exposure. A message that remains at the level of values has not yet reached the operation.

At regional scale, leaders often confuse consistency with identical execution. Consistency means that every site can explain which risk matters, who owns the decision, what evidence will be reviewed, and when an exception must be escalated. It does not mean that every factory uses the same meeting, wording, or sequence.

For a country or site leader, the translation should fit on one page. State the critical exposure, the decision that protects people from it, the role authorized to stop or redesign the work, and the evidence that will show whether the control is operating. The document becomes useful when a supervisor can use it during a shift decision without asking the regional office to interpret the intent.

Andreza’s argument in Make The Difference: Be a Leader in Health & Safety points to the same test. Leadership is visible in the decisions that change work, not in the number of messages distributed after a campaign.

Handoff 2: Preserve one standard while allowing local ownership

Local ownership protects a safety system from becoming a central-office ritual, but it only works when the non-negotiable elements remain visible. The regional leader must distinguish the control that cannot be weakened from the method that can be adapted.

A factory may need a different language, shift pattern, contractor process, or consultation route. Those differences are not automatically signs of inconsistency. The stronger question is whether the local method still protects the same exposure and produces evidence that another leader can understand.

A practical governance sheet can separate four fields. The first identifies the required outcome. The second names the minimum control. The third lists local choices. The fourth defines the escalation trigger. This structure gives site leaders room to solve problems while preventing local ownership from becoming an excuse for invisible variation.

The trap is centralization disguised as quality. When every local decision requires regional approval, leaders learn to wait, copy, and report upward. When no boundary exists, the network becomes a collection of private interpretations. The handoff works between those extremes.

Handoff 3: Move from country reporting to site evidence

Regional reporting is useful only when it points leaders toward evidence from the worksite. A dashboard that confirms activity without testing control performance can create confidence while the exposure remains unchanged.

The regional leader should ask each site for a small evidence set tied to the stated risk. That may include a field verification record, an authorization sample, an overdue action with its owner, a worker question that changed the plan, or a photograph linked to a dated control check. The exact evidence depends on the hazard, but the principle remains stable. Activity counts do not substitute for proof that the control worked under operating conditions.

ISO 45001:2018 supports this direction because the management system requires organizations to monitor, measure, analyze, and evaluate relevant performance, while also considering worker participation and operational control. The standard does not make a regional dashboard credible by itself. Credibility comes from the connection between the indicator and the physical or organizational condition it represents.

In The Illusion of Compliance, Andreza Araujo frames the danger clearly. A completed form can demonstrate that a process exists, but it cannot prove that the process prevented exposure when production pressure, maintenance urgency, or a contractor change altered the work.

Handoff 4: Make escalation faster than normalization

Escalation protects a multi-country system when local leaders encounter a condition that the standard process does not cover. If escalation takes longer than the work cycle, people normalize the deviation before senior leadership sees it.

The regional design should define the events that cannot wait for the monthly review. Examples include a failed critical control, a repeated high-potential near miss, a change that invalidates the original risk assessment, or a conflict between production authority and safety authority. Each trigger needs a named receiver, a response time, and a decision record.

James Reason’s work on latent failures helps explain why this matters. Serious events rarely depend on one isolated action; they emerge when several defenses contain weakness and the organization continues operating as if the weakness were temporary. A fast escalation routine interrupts that drift before it becomes normal practice.

The regional leader should also review the quality of escalations. A site that reports nothing may be highly controlled, or it may have learned that raising a problem creates blame, delay, or unwanted attention. The useful signal is not the highest number of escalations. It is whether leaders receive the information early enough to change the conditions that produced it.

Handoff 5: Return learning to the frontline routine

A safety lesson becomes organizational capability only when it returns to the routine in which the original risk is managed. A regional communication that stops at the country or site leadership team has not completed the handoff.

The return path should answer three questions. What changed in the work? Which role must act differently? How will the supervisor know that the new behavior is present during a normal shift? If the answer is a poster, an email, or a training attendance list, the organization has transferred information but not control.

For a distribution center, the return path might change loading authorization, pedestrian separation, or the shift-start briefing. For a factory, it might change maintenance isolation, line clearance, or the review of temporary deviations. The local routine will differ, which is precisely why the handoff needs a defined outcome rather than a fixed script.

Safety Culture: From Theory to Practice argues that culture is observed in repeated decisions. The frontline test is therefore simple and demanding. Can the person doing the work describe what changed, why it changed, and what to do when the control no longer fits the conditions?

What the case teaches leaders about measurement

The Unilever case suggests that multi-country safety performance should be measured through the quality of transfers, not only through the volume of regional activity. A leader needs indicators that reveal whether intent survived its journey to the worksite.

These are not a substitute for injury or exposure data. They are a way to test whether the management system is capable of influencing leading conditions before lagging outcomes arrive. A regional leader who reviews only the final rate may discover a failure after the operating system has already adapted around it.

How to apply the five handoffs in a 30-day review

A site or regional leader can test the handoffs in 30 days without launching another broad culture campaign. The work starts with one material risk and one recent decision that crossed organizational boundaries.

1. Days 1 to 5. Select the risk, trace the last decision from corporate intent to frontline execution, and record every point where ownership or evidence became unclear.
2. Days 6 to 12. Interview the people at each transfer, including a supervisor and a worker who operates the control. Compare what each role believes the standard requires.
3. Days 13 to 20. Rewrite the handoff sheet with the required outcome, minimum control, local choice, escalation trigger, and evidence owner.
4. Days 21 to 30. Observe the routine during normal work, correct the transfer that failed, and review the result with the next level of leadership.

The review should end with one changed operating decision, not a longer action register. If no decision changes, the review has described the system without improving its ability to control risk.

Where leaders can misuse the Unilever lesson

The case should not be copied as a universal template because the documented scope does not describe every local condition, legal requirement, or intervention used at each site. The useful transfer is the governance logic, not an imagined list of internal actions.

Three distortions appear often. First, leaders create a regional playbook and call the work complete before testing the handoffs. Second, they give sites freedom without defining the minimum control, which turns ownership into variation without visibility. Third, they replace field evidence with a new scorecard, which increases reporting while leaving decisions untouched.

Andreza Araujo’s broader experience across more than 250 companies and 30+ countries reinforces the point. Scale does not make culture abstract. It makes the transfer between decisions more important, because every weak handoff can be repeated across a network.

What the case means for safety leadership now

The Unilever case shows that regional safety leadership is less about issuing a universal message and more about protecting the quality of five transfers. Corporate intent must become a local decision, local ownership must preserve the required control, reporting must return to field evidence, escalation must outrun normalization, and learning must change the frontline routine.

That is the strategic value of a multi-country case study. It gives leaders a way to inspect the architecture between levels instead of praising the existence of the architecture itself. The next review should therefore ask where the last safety decision changed hands, what was lost at that point, and which routine will prove that the transfer is now stronger.

For deeper work on the relationship between leadership decisions and operating culture, explore Andreza Araujo’s books, including Safety Culture: From Theory to Practice, through the official store.