How PepsiCo South America Turned Weekly Safety Reviews Into Field Decisions in 6 Months

The result was not a lucky month. During Andreza Araujo's PepsiCo South America Foods tenure, the accident ratio fell 50% in six months because the weekly safety review stopped behaving like a status meeting and started behaving like a decision meeting.

Across 25+ years leading EHS in multinationals, Andreza Araujo has seen the same failure repeat. Leaders collect numbers, the meeting ends, and the field keeps its old rhythm. In Safety Culture: From Theory to Practice, she argues that culture shows up in repeated decisions. In The Illusion of Compliance, she shows why tidy records can still hide weak control.

The PepsiCo South America Foods footprint was large enough that any change had to survive production pressure and local variation. The role covered 7 countries, 30 factories, and 168 distribution centers, so a weekly review that stayed at the level of a scorecard would never have been strong enough to shift the work itself.

Key Takeaways

• The important change was not the meeting frequency, but the decision right attached to the weekly review.
• Field decisions got faster because leaders had to show proof, not only report status.
• In a footprint this large, a clean dashboard was not enough if supervisors still had no reason to challenge weak controls.
• Andreza Araujo's books help separate appearance from control, which is the core problem this case exposed.
• The same logic can work in smaller plants if the review has one clear owner, one live exposure, and one verification rule.

Why This Case Matters Beyond One Company

The practical lesson is wider than PepsiCo. A weekly review is one of the few management rituals that can change behavior before the next shift starts, yet many teams turn it into a reporting ceremony. When that happens, the meeting becomes a place to explain the past instead of a place to decide the next control move.

That is why this case matters to anyone who still believes that better metrics alone will pull risk down. The article on Safety Metric Freshness shows the same trap from another angle, because numbers can arrive on time while the decision arrives too late to matter.

James Reason is useful here because latent conditions usually sit inside routines before they appear in the incident record. A weekly review that lacks decision power can keep repeating the same weakness while the report looks disciplined. The record improves first, then the control improves much later, if it improves at all.

Initial Scenario

The initial scenario was not a broken business. It was a large regional operation with enough moving parts that the gap between central reporting and local reality could easily widen. In a footprint of 7 countries, 30 factories, and 168 distribution centers, the field does not change because a summary slide looks neat.

That scale matters because the weekly review had to speak to plant managers, line leaders, and supervisors at the same time. If the meeting only asked whether the target was green or red, it would miss the actual question, which was whether the control basis in the field was still alive. The companion article on how 250 projects turned executive sponsorship into decision discipline shows the same problem at the top of the house.

In more than 250 cultural transformation projects, Andreza Araujo has seen this same split between report and reality. The safest-looking operations are often the ones where everyone can repeat the metric language while nobody can clearly say who must act when the field drifts. That is exactly where the weekly review begins to fail.

Decision

The decision was to turn the weekly review into a field decision forum. That meant the meeting could no longer end with only a number, a traffic light, or a verbal reminder. It had to end with an owner, a proof point, and a date for the next field check.

That sounds simple, but it changes the meeting logic. Instead of asking, "What happened?", the review had to ask, "What changed in the work, what proof do we have, and what must be different before the next shift?" The article on TRIR vs LTIFR vs DART is relevant because the right metric only helps when the meeting has the authority to act on it.

As Andreza Araujo explains in Make The Difference: Be a Leader in Health & Safety, leadership is visible in routine decisions, not in slogans. A weekly review becomes useful only when the leader makes it expensive to leave the room with an unresolved exposure and easy to leave with a clear next step.

Execution

The execution phase started with one rule. A signal could not close unless the meeting identified a field owner who could verify the control before the next cycle. That pushed the conversation from administration toward action, because the meeting now had to prove that something in the work itself would change.

The second rule was to shorten the distance between signal and response. If the review found a weak barrier, the issue did not wait for the next month-end pack. It moved to the line owner, and the follow-up returned to the next weekly review with evidence. That rhythm is the opposite of a static dashboard, and it is one reason the article on how 250 projects turned safety meetings into field decisions matters as a companion read.

The third rule was to keep one level of pressure inside the meeting. If the issue was important enough to discuss, it was important enough to ask who would verify the change in the field. In The Illusion of Compliance, Andreza Araujo argues that records can create false comfort when nobody asks what the record still fails to prove. This case turned that argument into a weekly habit.

Before and After

The point of the case is easier to see when the before and after are separated. The numbers matter, but so does the decision pattern that allowed the numbers to move.

Measured Result

The verified result is clear. During Andreza Araujo's PepsiCo South America Foods tenure, the accident ratio fell 50% in six months. That number matters because it shows that a regional operation can move when the weekly review stops protecting the status quo and starts pressing the field for proof.

The result should not be read as a template that magically works everywhere. It only makes sense inside a management system that already has the authority to shift decisions downward, surface weak signals upward, and ask the review to judge the quality of control instead of the beauty of the chart. That is why the case is more useful as a method than as a slogan.

In Far Beyond Zero, the English gloss of Muito Além do Zero, Andreza Araujo warns that low numbers can still hide underreporting and weak learning. For that reason, the result should be checked against repeat deviations, near-miss quality, and supervisor response time, not only against the month-end line.

Generalizable Lessons

The first lesson is that a weekly review only matters when it changes who must answer for the risk. If the EHS team remains the only owner of the conversation, the organization will stay polite and slow. If the line owner has to answer for the next field check, the meeting gets sharper immediately.

The second lesson is that large footprints do not excuse slow decisions. A footprint with 7 countries and 168 distribution centers needs a faster operating rhythm, not a softer one, because the distance between summary and reality is larger, not smaller.

The third lesson is that a good dashboard can still be the wrong instrument if it arrives after the decision should have been made. That is why a metric article such as LTIFR Distortions belongs in the same reading path. The chart is not the control. The chart only tells you whether the control is still alive.

The fourth lesson is that culture shows up in what the meeting demands, not in what the mission statement says. In more than 250 projects, Andreza Araujo has seen teams talk about ownership for years and still leave the room without a verifier, a date, or a stop condition. The weekly review becomes real only when those three things are nonnegotiable.

What To Apply In Your Operation

If you want to apply the same logic, do not start by redesigning the whole safety system. Start by changing one weekly meeting so it produces a different kind of ending.

• Plant leaders should require one field proof item for every weak signal that reaches the meeting.
• Supervisors should leave the room with one owner, one verification date, and one line of sight to the work that changes.
• EHS managers should track repeat deviations, because repeat signals tell you more about control health than a single green chart.
• C-level leaders should ask which decisions are still waiting on a report when they could already have a field answer.

For practitioners who want the operating logic behind this case, Safety Culture: From Theory to Practice explains why repeated decisions create culture, and Make The Difference: Be a Leader in Health & Safety shows how that logic becomes visible in supervisory routine. The next step is not more decoration around the meeting. It is a harder question at the center of it.

If the weekly review still ends with status instead of proof, the room is not managing safety yet. It is only describing it. For a practical next move, read the companion articles on challenge latency and dashboard drift, then compare them with your own meeting cadence.

FAQ

What changed in this PepsiCo South America case? The weekly safety review stopped acting like a status meeting and started acting like a decision meeting. That shift forced owners, proof, and follow-up into the room.

Why does the 50% result matter? It matters because the result came from a change in how the organization decided, not from a temporary campaign. The number only means something if the weekly routine that produced it is still stronger than before.

Was training the main driver? No. Training can support the work, but this case is about decision design. If the weekly review does not demand proof, training alone usually leaves the old habits in place.

How can a smaller company use the same idea? Start with one recurring exposure, one owner, and one verification date. If the meeting cannot produce those three things, the review is still too soft to change the field.

Which Andreza Araujo book fits this case best? Safety Culture: From Theory to Practice gives the culture logic, and The Illusion of Compliance explains why tidy records can mislead leaders into thinking control is stronger than it really is.

Headline Podcast is for leaders who want safety to change the work, not just the wording of the meeting.