How 19 Countries Kept Safety Decisions Aligned

How do you keep safety coherent when one region spans 19 countries, 30,000 employees, 34 factories, and more than 60 distribution centers? The answer is not to force every site into the same script. The answer is to align the decision path, the evidence standard, and the escalation rule so that local reality can vary without the control logic breaking.

Across 25+ years in multinational EHS and more than 250 cultural transformation projects, Andreza Araújo has seen the same pattern repeat. Sites do not fail because they lack a policy. They fail because each country interprets the policy a little differently, and that small difference becomes a real gap when pressure rises. In Safety Culture: From Theory to Practice, culture is visible in what people do under pressure, not in the sentence that was approved by headquarters.

This case comes from Andreza Araújo's Unilever LATAM leadership scope. It is useful because it shows a real transformation problem, not a theoretical one. The region had to keep one safety language across countries that were not identical, while still respecting local work, local regulation, and local operational constraints. That is exactly where Safety Culture Maturity: 3 Assumptions That Keep Leaders Stuck becomes practical, because maturity is not the same as having more slides.

Initial scenario

The initial problem was not chaos. It was fragmentation that looked normal from a distance. One country called a barrier check complete when the form was filled, another wanted field proof, and a third treated escalation as a local issue unless the site manager insisted otherwise. The paperwork looked orderly, but the operating logic was inconsistent.

That is the kind of drift Andreza Araújo warns against in A Ilusão da Conformidade. Compliance can be real and still be incomplete, because a site can satisfy the local ritual while the control itself remains weak. In a 19-country scope, that is not a small problem. It means the region can appear aligned while the field still behaves as if every country owns its own definition of acceptable risk.

In practice, the gap shows up in details that leaders often dismiss. One site closes actions quickly but never verifies them in the field. Another site verifies well but escalates too late. A third site uses the same label for a different behavior, which makes regional reporting look clean and operational comparison look false. This is why a safety culture case study matters: it exposes the difference between shared language and shared meaning.

Decision

The leadership decision was to stop treating alignment as a communication exercise. Instead, the team defined what was non-negotiable across the region, what could vary locally, and which proof would count everywhere. That sounds simple until a region spans multiple legal environments and operational models. Then the decision becomes a governance choice, not a messaging choice.

Andreza Araújo's view in Make The Difference: Be a Leader in Health & Safety is useful here because leadership is framed as a decision system. The leader does not just repeat the standard. The leader decides what must be true, who verifies it, and what happens when the answer is weak. That is the difference between regional control and regional decoration.

The decision also changed how the team thought about ownership. Instead of asking who would write the action, the team asked who could verify it, who could challenge it, and who could force the fix when the local site was already busy. That shift is similar to the logic in Critical-Risk Owner in 45 Days: Accountability Map, because risk control only becomes real when ownership is attached to a concrete decision.

Execution

The execution had three layers. First, the region established a common control language so that the same barrier had the same meaning in every country. Second, leaders created a shared escalation route, which reduced the chance that a weak signal would disappear inside a local queue. Third, supervisors were asked to verify barriers in the field, because the person closest to the work sees the first sign of drift fastest.

This part matters because regional alignment usually fails when leaders confuse standardization with centralization. The region did not need to control every local decision. It needed a few non-negotiables that were strong enough to survive local pressure. In more than 250 transformation projects, Andreza Araújo has seen the same pattern: when leadership standardizes the right decisions, the organization stops arguing about labels and starts dealing with the barrier itself.

Leadership Change Safety Reset in 30 Days is relevant here because any new leadership logic must survive the first month of pressure. If it does not, the site falls back to the old habit of declaring progress while the field stays inconsistent. That is why the execution phase focused on rhythm, not slogans.

The region also clarified the difference between reporting and proof. A report could say a control existed, but only field verification could show whether it actually held under routine work. That distinction is consistent with Safety Culture: From Theory to Practice, where culture is judged by repeated behavior and not by one-off compliance moments. It is also why regional safety culture work fails when leaders rely on dashboards alone.

Measured result

The measured result was coherence. Across a region of 19 countries, 34 factories, and more than 60 distribution centers, leaders were no longer dealing with 19 different answers to the same control question. They had one common logic for what counted, how it was checked, and when it had to move upward. In a multi-country operation, that is a serious result because consistency is itself a control.

The proof was not that every country became identical. The proof was that local variation stopped changing the meaning of the control. That mattered because a region can handle local differences, but it cannot handle different definitions of the same risk barrier without paying for it later in rework, delay, and blind spots.

The case also illustrates why A Ilusão da Conformidade remains relevant for leadership teams. A clean report can be comforting, but comfort is not evidence. When the region required field proof and explicit escalation, it reduced the chance that a site would stop at the appearance of control. That is measurable even when the measure is qualitative, because the same question now receives the same operational answer across the region.

Before and after

The table is useful because it shows the real shift. The region did not simply ask for more activity. It changed the type of evidence that was accepted, which means it changed the quality of the decision itself. That is why Safety Culture Maturity: 3 Assumptions That Keep Leaders Stuck belongs in the same reading path. Maturity is visible when leaders ask better questions, not when they produce more noise.

Generalizable lessons

Four lessons come out of this case. First, standardize the decision grammar, not the entire operation. If every site must use the same sentence to describe a different reality, the region will lose credibility fast. Second, never confuse compliance evidence with control evidence. A form can be accurate and still miss the barrier. Third, supervisors need a clear verification role because the field sees drift before the spreadsheet does. Fourth, regional leaders must decide what is local and what is non-negotiable, because ambiguity always gets filled by pressure.

These lessons are consistent with Make The Difference: Be a Leader in Health & Safety, which treats leadership as visible choices under pressure. They also connect with Critical-Risk Owner in 45 Days: Accountability Map, because ownership only works when one person is accountable for the actual control, not just the status update. When the region makes that distinction clear, the system becomes easier to see and harder to fake.

The strongest lesson is probably the simplest one. Safety culture does not scale by multiplying reminders. It scales when leaders agree on the proof standard and then use it every time, even when the local site is busy, tired, or convinced that the old habit is faster. That is the practical meaning of culture in a multi-country environment.

What to apply in your operation

If you run a regional operation, start with one control that matters to serious risk and ask four questions. What is the non-negotiable evidence? Who verifies it in the field? Who can challenge a weak closure? Who can force the fix when the site is under pressure? If those answers change from country to country, you do not yet have one control system.

For a plant manager, the first move is to remove the ambiguity around verification. For an EHS leader, the first move is to define the evidence that will count across sites. For a supervisor, the first move is to stop accepting paper closure without field proof. That sequence is practical, and it matches the leadership logic Andreza Araújo teaches in Safety Culture: From Theory to Practice.

If you want a sharper diagnostic, Safety Culture Diagnosis: Learn how to do your own helps turn the case into a working method. It is especially useful when the problem is not lack of effort but lack of shared criteria. For readers who need a field-ready companion, Leadership Change Safety Reset in 30 Days shows how to keep the first month from sliding back into old habits.

For practitioners who need to test this end to end, start with one country, one critical control, and one field check. Then compare the answer across the region. If the answer changes too much, the control is still local, even if the policy is regional.