19-Country EHS Rollout: How Safety Culture Scales

A safety culture rollout across 19 countries with different languages, labor rules and operating habits fails when headquarters treats culture as a communication campaign. This case study shows how senior EHS leaders can scale culture through governance, local translation and visible leadership without turning the program into another poster set.

On the Headline Podcast, hosted by Andreza Araujo and Dr. Megan Tranter, the recurring question is not whether leaders believe in safety. The harder question is whether the operating system makes that belief visible when production, cost, contractors and deadlines collide.

1. Initial scenario: the problem was not lack of safety language

A multi-country EHS rollout begins with a deceptive advantage, because every site can repeat the same safety words while practicing different decisions. In the verified Unilever context from Andreza Araujo's multinational career, the leadership challenge was not to invent a slogan for 19 countries, but to make safety culture legible inside local management routines.

Many global programs fail at this point because they confuse alignment with repetition. A plant manager can display the corporate message, attend the launch meeting and still run maintenance planning, contractor access and incident review exactly as before. That is why safety culture diagnosis has to look at operating behavior, not only at stated belief.

Across more than 250 cultural transformation projects, Andreza Araujo has observed a recurring pattern: culture becomes scalable only when the executive team defines the few decisions that must change in every site. Without that decision list, the rollout spreads vocabulary faster than it changes risk.

The first move for a senior EHS leader is therefore uncomfortable. Instead of asking each country to promote the new culture, ask each country to name the management decisions in which the old culture still wins.

2. The decision: make culture a governance rhythm

A 19-country rollout needs a governance rhythm before it needs a training calendar. The rhythm defines who reviews cultural evidence, how often they review it, which decisions are escalated and what leaders must do when the evidence contradicts the official story.

Co-host Andreza Araujo explores this same logic in Safety Culture: From Theory to Practice, where culture is treated as the way decisions are made under pressure, not as an attitude survey score. That logic matters because a survey can improve while high-risk work remains unchanged.

For the executive sponsor, the practical decision is to set a monthly culture review that is separate from the standard injury-rate review. The agenda should include exposure, weak signals, contractor integration, speak-up quality and the age of corrective actions, which connects this rollout to safety decision rights rather than to campaign management.

Each month without that rhythm allows local sites to interpret culture as optional style, while high-risk work continues to be governed by informal shortcuts that rarely appear in corporate dashboards.

3. Execution: translate the standard without diluting it

Local translation is not local permission to weaken the standard. In a multi-country rollout, translation means each site explains the same cultural requirements through its labor context, supervisory structure, contractor model and regulatory reality.

This is where many corporate teams lose control. They either force a central script so rigid that sites ignore it, or they allow so much customization that the rollout becomes 19 separate programs. The stronger path is to fix the non-negotiable behaviors and allow local examples, language and meeting formats to vary.

On Headline Podcast, leadership conversations often return to visible felt leadership because field credibility is built in the moment where leaders notice real work. A senior leader who visits a site and asks only about the injury rate teaches one culture, while a leader who asks how a permit was challenged teaches another.

The working rule is simple enough to audit. Every country can choose its examples, but no country can opt out of the core routines: leadership field presence, high-risk work review, worker voice, contractor inclusion and action closure.

4. Field adoption: supervisors carried the rollout or stopped it

Supervisors determine whether a culture rollout becomes work practice because they translate executive intent into daily trade-offs. If the supervisor is measured only on production recovery, the rollout will be heard as a speech from headquarters.

Andreza Araujo's experience across multinational EHS roles shows that frontline adoption depends on what supervisors are allowed to stop, question and escalate. The Hudson maturity model can help leaders see that a site does not move from reactive to proactive because a central team says so. It moves when supervisory routines change under real pressure.

In practice, the rollout should give supervisors a short set of field questions, not a long training deck. They need to ask what changed since the last shift, which control depends on human vigilance, where the crew sees pressure, and what work should pause if the condition changes.

The trap is to call this empowerment while punishing the first costly stop-work decision. Culture scales when the first expensive interruption receives executive protection, because everyone watches that case more closely than the launch event.

5. Measured result: the signal was cultural repeatability

The primary result in a 19-country culture rollout is repeatability of critical decisions across diverse operations. Injury rates matter, but they lag behind the cultural mechanics that make risk visible before harm occurs.

The verified comparison point from Andreza Araujo's wider career is the PepsiCo South America tenure, where the accident ratio fell 50% in six months. That result is useful here not because every rollout should promise the same number, but because it shows that cultural work can move indicators when leadership routines and operating discipline change together.

For Headline readers, the useful metric is not how many people attended the launch. Track how many high-risk decisions were escalated, how many leadership visits changed a condition, how many contractor gaps were closed and how many weak signals reached the executive review without being filtered.

6. Generalizable lesson: culture cannot be delegated to EHS

Safety culture fails to scale when the EHS function becomes the owner of every cultural action. EHS can design the method, train the reviewers and protect technical discipline, but line leadership owns the daily decisions that create culture.

This distinction matters for boards because safety is increasingly treated as operational and reputational risk. An executive team that frames safety as material risk will ask different questions from a team that frames safety as a departmental scorecard.

Dr. Megan Tranter's leadership lens on Headline Podcast is especially relevant here because global organizations do not change through EHS language alone. They change when leaders across operations, HR, procurement and finance understand which behaviors their systems reward.

The decision for the C-suite is to stop asking whether EHS has rolled out the program. Ask which executive-owned processes now carry safety culture as a decision criterion.

7. What to apply in your operation

A senior EHS leader can apply this case without copying the 19-country model. The point is to convert culture from a message into a repeatable operating pattern that survives distance, language and leadership turnover.

Start with a 90-day review of three sites that differ in maturity, risk and operational pressure. In each site, compare what the culture program says with what work planning, contractor control and incident review actually reward.

Then define five non-negotiable routines for the next quarter: executive field review, supervisor risk dialogue, high-risk work escalation, contractor culture integration and action aging review. Link those routines to leadership presence in the field, because culture rarely changes from conference rooms alone.

The last step is to publish the first hard decision. If a plant delays a job because the rollout exposed a weak control, treat that delay as evidence of culture working, not as evidence of poor planning.

Comparison: campaign rollout vs operating-system rollout

Conclusion

The central lesson from a 19-country EHS rollout is that safety culture scales only when leaders make the same few risk decisions visible across very different local realities. A campaign can create attention, but only an operating rhythm changes what supervisors, managers and executives do when pressure arrives.

Headline Podcast is the space where leadership and safety come together to shape better workplaces and better lives. If this case belongs in your next executive safety discussion, listen to the conversations hosted by Andreza Araujo and Dr. Megan Tranter at Headline Podcast.