How a Seven-Country EHS Operation Turned Follow-Up Into Safety Control

In large EHS organizations, the tempting story is that the leader who speaks strongly about safety changes the operation. The harder truth is more operational. A leader changes safety only when the organization can see what was promised, who owns the next action, where the deviation remains open and which manager lets the same weak signal return next week.

That is why Andreza Araujo's PepsiCo South America experience is useful as a safety leadership case, not merely as a headline result. During her tenure as EHS senior manager for PepsiCo South America Foods, her scope covered seven countries, 30 factories and 168 distribution centers. Under a 180-day plan, the accident ratio was reduced by 50%, a documented result in her professional record. The number matters, but the management lesson sits underneath it: scale exposes whether follow-up is a ritual or a real control.

This article does not claim that any company can copy a number from another operation. A food manufacturing and distribution network has its own risk profile, labor model, contractor exposure, fleet pressure and leadership structure. The transferable lesson is the cadence that makes weak execution visible before it becomes a serious event. That is the point many safety programs miss when they invest heavily in launches and lightly in follow-up.

Initial Scenario: A Large Operation Cannot Run on Safety Intent

A seven-country EHS scope creates a specific leadership problem. The central team may define the standard, but the real risk is managed by plant managers, warehouse leaders, supervisors, maintenance teams and route leaders whose decisions happen far from the meeting room. When the operation includes factories and distribution centers, the risk picture also changes during the day, because production pressure, loading windows, temporary maintenance, vehicle movement and contractor activity do not wait for the next monthly committee.

In that environment, safety intent becomes weak if it is not converted into a visible management rhythm. A policy can say that unsafe conditions must be corrected. A speech can say that people come first. A dashboard can show declining injuries for a few months. None of that proves that leaders are acting on the right signals, because an operation can look calm while overdue actions, repeated near misses and weak supervision accumulate below the surface.

As Andreza Araujo argues in Safety Culture Diagnosis, culture cannot be treated as a slogan installed from the top. It has to be measured through perception, routines and evidence, because the organization often says one thing while rewarding another. In a large regional structure, that gap becomes expensive. The corporate message may be consistent, while each site quietly invents its own tolerance for delay, shortcuts and unfinished corrective actions.

Decision: Make Follow-Up the Leadership Control

The leadership decision in a case like this is to stop treating follow-up as administrative closure. Follow-up is the control that proves whether the organization can learn, correct and sustain. If an action is assigned but never tested, the system has created paperwork. If a supervisor reports a deviation but receives no response, the system has trained that supervisor to stop escalating. If a site closes an action without checking the barrier in the field, the dashboard has become a decoration.

The practical shift is simple to describe and difficult to sustain. Leaders must review fewer items with more consequence. Instead of asking for every safety activity performed during the month, they ask which critical deviations remain open, which actions are overdue, which risk owners missed their commitment and which repeated signal suggests a deeper weakness in supervision, planning or maintenance. That changes the conversation from activity volume to control quality.

This is also where safety leadership separates itself from safety enthusiasm. Enthusiasm can launch campaigns, but leadership removes ambiguity from ownership. A regional EHS leader who manages seven countries cannot personally fix each unsafe condition, but she can build a cadence in which local leaders know that critical risk, late action and repeated drift will be reviewed with names, dates and evidence.

Execution: From Regional Message to Site-Level Evidence

The execution work begins by translating the regional message into a small set of repeated questions. Which events could have become serious if one more barrier had failed? Which corrective actions are late because the owner lacks resources, and which are late because nobody is managing them? Which supervisors are present in the field when high-risk work starts? Which site keeps reporting the same type of deviation without changing the work process that produces it?

Those questions matter because they connect leadership behavior to operating control. In a 30-factory and 168-distribution-center environment, the central team cannot rely on anecdote, because it needs comparable evidence. Not every site needs the same action, but every site needs the same discipline in classifying critical risk, escalating blocked actions and proving that the field condition changed after the meeting.

The strongest follow-up routines usually contain four elements. First, a short list of critical deviations, not a long archive of minor findings. Second, named owners who have authority to act, not symbolic owners who must beg for permission. Third, field verification before closure, because a closed action that did not change the work area is still open in operational terms. Fourth, repeated review by leaders whose calendars show that safety is part of management, not a visitor from the EHS department.

That rhythm also protects the organization from a common trap in large safety programs. Sites learn what leadership actually values. If leaders praise the number of completed observations but never ask whether the observation changed a risk, the site will produce observations. If leaders celebrate fast closure but never ask whether the control works, the site will close actions quickly. Follow-up quality tells the operation what kind of safety performance is real.

Measured Result: What the 50% Reduction Should and Should Not Teach

The documented PepsiCo South America result, a 50% reduction in accident ratio in six months, should not be read as a promise that any organization can obtain the same number in the same time. YMYL safety content has to be careful here, because borrowed numbers can create false confidence. The result is credible as Andreza Araujo's professional case, and it is useful because it shows that leadership cadence can move a large system when the work is disciplined.

The better question is what the metric reveals about management quality. A reduction of that size across a large scope usually requires more than communication. It suggests that the organization found and corrected patterns that had been allowed to repeat. It also suggests that the leadership layer became more effective at converting information into decisions, because accident ratio does not move sustainably when the field keeps the same weak controls and only changes the campaign poster.

The metric should still be handled with maturity. A fall in accident ratio can be distorted by underreporting, classification pressure or a temporary decline in exposure. That is why a serious leader reads it beside near misses, serious potential events, overdue corrective actions, audit quality and worker voice. The number is important, but the operating system around the number tells whether the improvement is real.

For an adjacent view on how leaders should avoid false confidence in indicators, see SIF Rate vs TRIR vs Precursors. The same principle applies to injury reduction, which is meaningful only when paired with evidence that serious risk controls are getting stronger.

Generalizable Lessons for EHS Leaders

The first lesson is that scale punishes vague accountability. In a small site, weak ownership may be visible because everyone knows who failed to act. In a seven-country operation, weak ownership hides behind distance, reporting layers and local exceptions. The leader has to design a rhythm that makes ownership explicit without turning every meeting into a trial.

The second lesson is that follow-up has to distinguish critical risk from background noise. A regional EHS team can drown in minor actions while high-energy hazards, contractor controls, vehicle movement, machine intervention and maintenance planning receive less attention than they deserve. The discipline is not to review everything. The discipline is to decide which unresolved items could injure someone seriously and then refuse to let them drift.

The third lesson is that closure requires evidence. A photograph, a field check, an operator interview or a supervisor walkthrough may reveal that the action was only closed in the system. James Reason's work on latent failures helps explain why this matters. Incidents often emerge from conditions that were present before the event, and a closure process that does not test the condition leaves the latent weakness intact.

The fourth lesson is that leadership cadence shapes culture more than slogans do. Andreza Araujo's work in Cultura de Seguranca: Da Teoria a Pratica, often presented in English as Safety Culture: From Theory to Practice, treats culture as repeated behavior supported by leadership consistency. In practical terms, the weekly review that asks hard questions about unresolved risk teaches more than a quarterly speech about commitment.

What to Apply in Your Operation

A smaller company can apply this case without pretending to be a seven-country network. Start with one weekly safety control meeting of 30 minutes. The agenda should include critical deviations from the week, serious-potential near misses, overdue actions, actions closed without field evidence and decisions blocked by resources. The meeting should be chaired by an operational leader, with EHS serving as technical conscience rather than owner of every problem.

For a multi-site company, the same structure can run at two levels. Sites review their own critical items weekly, while the regional or corporate team reviews patterns every two weeks. The higher level should not repeat the site meeting. It should ask which sites are drifting, which controls keep failing, where capital or staffing decisions are blocking correction and which lessons need to move across the network.

The first trap is reviewing too many actions, which turns leadership attention into clerical checking. The second is accepting closure without evidence, which rewards speed over risk reduction. The third is letting EHS own every corrective action, which teaches operations that safety is a department rather than a management duty. The fourth is celebrating a declining injury rate before checking whether reporting quality is still healthy.

Teams that need a deeper diagnostic structure can use Safety Culture Diagnosis: 250-Company Case as a companion article, because it shows why culture work begins with evidence before intervention. Leaders can also explore Andreza Araujo's books and advisory work at andrezaaraujo.com when they need a structured path from diagnosis to execution.

FAQ

What made the PepsiCo South America case relevant for safety leadership?

Its relevance comes from the scale and the documented 180-day result. A seven-country operation with 30 factories and 168 distribution centers tests whether leadership routines can travel beyond one charismatic site leader.

Why focus on follow-up instead of training?

Training matters when people lack knowledge or skill, but follow-up proves whether the organization corrects what it already knows. Many serious weaknesses persist because leaders tolerate delay after the finding is recorded.

How should leaders avoid underreporting during a reduction campaign?

They should read injury reduction beside reporting volume, near misses, serious-potential events, overdue actions and worker concerns. If the injury rate falls while weak signals disappear, the organization may be measuring silence rather than improvement.

Who should own corrective actions?

The owner should be the operational leader with authority over the condition, budget or work process. EHS can guide the technical quality, but ownership has to sit where the risk is created and controlled.

What is the first step for a company that wants to apply this case?

Begin with a short weekly review of critical deviations and overdue actions, then require field evidence before closure. That modest routine reveals very quickly whether safety is managed as control or as paperwork.