How 19 Countries Learned to Use One Risk Language Without Losing Local Reality

Risk language is the shared way a region names hazards, controls, escalation thresholds, and decision rights so leaders can compare exposure across sites without pretending that every country faces the same work. It matters because a register that means one thing in Mexico, another in Colombia, and another in Argentina is not governance, even if every site uploads a file on time.

During Andreza Araujo's tenure as Director SHE LATAM at Unilever, the documented scope covered 19 countries, 30,000 employees, 34 factories, and more than 60 distribution centers. That scale makes one thing obvious. Regional risk management fails when people confuse a common template with a common operating language.

Key Takeaways

• One regional template is not the same as one risk language, because the same words can hide different assumptions about exposure and authority.
• Leadership must define what is common, such as escalation triggers and critical-control criteria, and what stays local, such as site scenarios and legal differences.
• Risk governance improves when field evidence can challenge managerial confidence, not when managers only review tidy reports.
• In more than 250 cultural transformation projects, Andreza Araujo has seen that clarity fails first at the handoff between local autonomy and regional review.
• A regional EHS system becomes usable when it changes the question leaders ask before they accept residual risk.

Initial Scenario

The initial scenario in a multi-country role is usually a mosaic. One country classifies contractor road risk as high because it has recent events, another scores the same exposure as medium because the matrix averages the inputs, and a third treats it as a local operations issue outside the central EHS view.

That variation can look like local maturity, although it often hides a translation failure. If a plant manager, a country manager, and a regional EHS director use the same words but mean different things, the organization does not have a shared system. It has local interpretations with a common logo.

Andreza Araujo's book Safety Culture: From Theory to Practice is useful here because it treats culture as repeated decisions under pressure, not as a slogan. The first decision in a regional case is therefore not what software to buy. It is what the region must be able to say the same way everywhere.

This is also where the practical risk appears. A country can appear compliant, the archive can be complete, and the meeting cadence can be visible, while the controls do not prove that serious exposure is actually reduced. The problem is not poor presentation. The problem is that leadership cannot compare the risk quality of one site against another.

Decision

The decisive move was to separate what must be common from what must stay local. Severity definitions, escalation triggers, critical-control criteria, and evidence standards needed a common spine, while site scenarios remained local because the hazard profile was not identical.

That distinction matters because the same template can travel across countries without changing the actual decision. Governance begins when the same exposure produces the same leadership question, even if the corrective action differs by site. If the question changes from country to country, the region is still guessing.

Across 25+ years leading EHS in multinationals, Andreza Araujo has seen that weak risk systems usually fail at the point where leaders assume local reporting equals regional control. ISO 31000 helps frame the issue, but the standard does not make a forklift route in a crowded distribution center comparable to a chemical transfer in a factory. The region has to build that comparability through definitions, evidence, and decision rights.

That is why the risk language question belongs to operations, not only to EHS. If the plant manager cannot explain the top fatal risks in the same terms that the regional director uses, the system is still translating itself instead of governing risk.

Execution

Execution started with a taxonomy that reduced noise. Every site had to classify operational risk using agreed categories such as energy isolation, vehicle movement, working at height, contractor interface, chemical exposure, process change, and emergency response. The goal was not to erase local reality. The goal was to make local reality comparable.

The second layer was evidence. A regional team should not accept a green status unless the site can show current control verification, field observations, closed actions, and leadership review. That is where indicator triangulation matters, because no single metric can prove that a risk is under control.

The third layer was escalation. If a site had repeated overdue critical actions, weak verification, or a serious exposure accepted beyond its authority level, the issue moved from local tracking to regional review. That movement is governance, because it changes who has to decide.

The region also had to protect the messenger. If local teams believed that early disclosure would be treated as failure, they would sanitize the register. If leaders rewarded early exposure of weak controls, the register would become a management tool rather than a compliance archive.

Each quarter without a shared risk language allows local improvisation to harden into culture, and after that, the template becomes harder to correct than the original technical gap.

Measured Result

The measurable result in this case is not an invented injury reduction number. The verified public anchor is the scale of the Unilever LATAM scope, 19 countries, 30,000 employees, 34 factories, and more than 60 distribution centers. The result that can be defended is the creation of a common risk conversation across that scale.

That matters because scale changes the nature of risk. A weakness that looks isolated at one factory may reveal a regional pattern when the same control gap appears in five countries, and a control that looks mature in one distribution center may fail when contractor turnover changes. Regional comparability is the real output.

The strongest signal of maturity is not a prettier dashboard. It is the moment when a country manager, a plant leader, and a regional EHS director can look at the same exposure and agree on whether the risk is accepted, transferred, reduced, or escalated. That agreement is measurable because it changes the quality of executive attention.

The practical value of that before-and-after shift is simple. The region stops asking whether every site submitted the same form and starts asking whether every site is using the same logic to manage the work that can hurt people.

Generalizable Lesson One

The first lesson is that translation is a risk-management problem. If the region cannot translate a hazard into the same decision language across countries, then it does not yet have governance. It has documentation with different accents.

This lesson appears in risk register fields that keep controls alive. A risk register only helps when it names the exposure, the owner, the interim control, the verification method, and the review date in a way that another leader can act on without guessing.

In more than 250 cultural transformation projects, Andreza Araujo has seen the same pattern repeat. The first breakdown is rarely lack of concern. It is mismatch between the words leaders use and the decisions those words are supposed to trigger.

Generalizable Lesson Two

The second lesson is that what must be common should be small. A region does not need to standardize every local scenario. It needs to standardize severity definitions, escalation triggers, evidence standards, and critical-control criteria. If those few pieces are stable, local teams can adapt the rest without losing comparability.

That balance is why MOC, PTW, and PSSR belong in the same conversation. A regional template that treats every control as a generic action item will miss the difference between approving a permit and accepting a startup risk.

As Andreza Araujo argues in A Ilusao da Conformidade, the illusion is thinking that a completed form proves a controlled worksite. The stronger test is whether the same control logic still holds on night shift, during maintenance, and when a contractor changes the pace.

Generalizable Lesson Three

The third lesson is that the messenger must be protected. When local teams see that bad news produces support and clearer priorities, rather than blame, they report weak controls earlier and with better evidence. When they see punishment, they sanitize the register.

Andreza Araujo's broader record across 25+ years in multinational EHS roles shows why this matters. A regional system becomes credible when field evidence can challenge managerial confidence. Without that friction, the dashboard becomes a mirror for optimism.

The same logic appears in safety culture drift. Drift starts when people learn that the written answer matters more than the field answer, and after that the region may still look aligned while the operating logic splits.

What to Apply in Your Operation

A regional EHS manager should begin with the five exposures that can kill, disable, or create severe regulatory consequences. For each exposure, define the minimum control standard, the evidence required, the decision owner, and the threshold that forces escalation. If those four points are not visible, the region is still making the same mistake in different languages.

Then test the system with three sites that are different on purpose, a mature factory, a pressured distribution center, and a site with high contractor dependency. If the same risk language survives those three contexts, the model has a chance of working across the broader network. If it fails, the region learned something before it paid for the mistake.

Use the first 30 days to compare how each site names the same exposure. Ask one plant how it describes contractor road risk, ask another how it describes energy isolation, and ask a third how it describes escalation. If the answers drift, the region needs a translation standard before it needs another metric.

For teams that want a practical next step, start the review with the same questions used in indicator triangulation. What does the number say, what does the field show, and who has to decide if the two disagree?

FAQ

What is the main lesson from the Unilever LATAM case?

The main lesson is that regional governance needs one risk language across countries, while still preserving local scenarios and site-specific controls. Without that, the region can look aligned while the actual risk logic stays fragmented.

Why is one template not enough?

A template proves that the same form traveled across countries. It does not prove that the same exposure produces the same leadership question. Governance only begins when decision rights, evidence, and escalation mean the same thing everywhere.

What should stay local in a regional risk model?

Local scenarios, legal differences, contractor realities, and site-specific work methods should stay local. The region should standardize the spine, not every detail. That is what keeps the system comparable without flattening reality.

Who should own the risk language?

The language has to be owned by operations and regional leadership together, with EHS facilitating the method. If only EHS owns it, the system becomes advisory. If only operations owns it, the system can drift into convenience.

What is the first 30-day move?

Pick the five exposures with the highest consequence, then compare how three different sites describe them. If the same words do not trigger the same decision, the region needs a common translation standard before the next review cycle.

Recommendation

Use the Unilever LATAM lesson as a test of governance, not as a memo template. A region is mature when leaders can compare risk, challenge weak controls, and decide escalation in the same language while still respecting local reality.

If your organization needs to turn fragmented site-level risk information into a governance model that leaders can actually use, Andreza Araujo's advisory work can help structure the diagnosis and the first 30-day reset. Start the conversation at Andreza Araujo.