How a Consumer-Goods Operation Cut Accident Ratio 50% in 180 Days by Turning Follow-Up Into a Control System

The result was not luck. During Andreza Araujo's PepsiCo South America Foods tenure, the accident ratio fell 50% in 180 days because follow-up stopped being an administrative task and became a control system that supervisors had to defend in the field.

That distinction matters because Andreza's regional role covered seven countries, 30 factories, and 168 distribution centers. When a change survives that spread, it is not a local trick. It is a repeatable leadership pattern that can travel through scale, language differences, and production pressure.

In Safety Culture: From Theory to Practice, Andreza argues that culture is built through repeated decisions. In The Illusion of Compliance, she shows how a clean record can hide weak control. This case sits between those two ideas, because the work improved only when the people closest to exposure had to prove what closed, what stayed open, and what still needed a decision.

Initial scenario

The starting point was familiar to most EHS leaders. The operation had inspections, action lists, monthly reviews, and people who believed the work was moving because the spreadsheet was filling up. The problem was that a filled spreadsheet does not tell you whether the same exposure is still present on the next shift.

When follow-up lives in the office, the organization learns to confuse ownership with administration. That is why this case is useful alongside How to Diagnose Compliance Theater Before the Next Audit in 30 Minutes. Both pieces point to the same blind spot, which is that tidy records can coexist with weak control if nobody has to show proof in the field.

James Reason's latent failure model helps explain the pattern. A weak action stays weak, then it gets normalized, then it gets copied, and eventually the site treats the workaround as if it were the system. Follow-up is where that chain is interrupted or allowed to continue.

The decision

The key decision was to stop asking EHS to own closure by itself and make line management responsible for the first real response. In practice, that meant supervisors had to see the deviation, understand the control that should hold it, and return to the crew with a decision that could be checked.

That shift sounds small until you compare it with the usual rhythm. Many organizations treat follow-up as a reminder, a note in a tracker, or a polite chase for an update. In this case, follow-up became part of the control structure, which meant it had to show the same discipline as any other work decision that affected exposure.

The useful companion article is Leadership Cadence: 4 Decisions Behind a 50% Accident-Ratio Drop, because it makes the same point from a different angle. A result like this does not come from more noise. It comes from fewer decisions being allowed to drift.

The execution rhythm

Execution depended on cadence. The weekly routine had to surface repeat deviations quickly, and the managers closest to the work had to answer what changed, who owned it, and whether the change was verified where the exposure actually lived. Without that rhythm, the action log would have returned to being a storage place for intent.

Andreza Araujo's experience across more than 250 cultural transformation projects shows why this matters. Many leaders believe a faster response is mostly a matter of effort, yet the real issue is often decision design. If no one can say what proof closes the loop, the same issue will keep returning with a better status update.

That is why the case pairs naturally with How 250+ Projects Turned Executive Sponsorship Into Decision Discipline. The boardroom version and the plant version share the same weakness, which is that attention without a proof standard becomes theatre.

Measured result

The verified result is direct. During Andreza Araujo's PepsiCo South America Foods tenure, the accident ratio fell 50% in 180 days. The number matters, but only if it is read as the output of changed leadership behavior rather than as a badge for one company.

What changed was the operating condition around closure. The same site that once tolerated slow follow-up began to treat unfinished action as a live control gap. That is a different message to the workforce, because it says the company is no longer satisfied with a promise that looks tidy on paper.

That table should not be read as a universal recipe. It is a way of showing that a result improves when leaders change what counts as closed, not just what counts as reported.

What the result actually proves

The result proves that follow-up can be a control function when leaders treat it that way. A lot of sites already have action trackers. Far fewer have a routine that makes closure part of the same management discipline that controls production, maintenance, and scheduling.

This is where the story overlaps with How to Build an Incident Evidence Map in 48 Hours. Both articles reject the idea that a cleaner record automatically means a safer operation. Evidence matters only when it changes the next decision.

It also explains why Andreza's books stay relevant here. Safety Metric Freshness Explained: 4 States That Matter shows why stale numbers can hide a live problem. Safety Culture: From Theory to Practice explains how repeated decisions create the culture people actually live. The Illusion of Compliance explains why a site can look organized while still depending on memory, pressure, and informal workarounds.

What most leaders miss when they copy the case

Most leaders copy the visible part and miss the control logic. They see the 50% reduction and think the answer is a campaign, a tighter checklist, or a new dashboard. The real answer was less dramatic and more demanding, because someone had to own the quality of follow-up every week.

Another common mistake is to assume the case only applies to a large multinational. It does not. Scale helped the lesson become visible, but the logic applies in a single plant, a contractor-heavy site, or a distribution network where small misses are quietly repeated until they become expensive.

The safest transfer question is simple. If your crew cannot explain who owns the next decision, what proof closes the item, and when the issue returns to the agenda, then you do not yet have follow-up as a control. You still have follow-up as admin.

What to apply in your operation

If you want to apply the case, start with one recurring exposure and one visible closure rule. Do not spread attention across every action list at once. Pick one pattern that returns often, then make the line manager responsible for field proof and the supervisor responsible for the next step.

Three practical moves usually matter first. Name the owner of each open item in the line, not only in EHS. Define what counts as proof in the field. Review repeat deviations before the next shift, not after the month-end report has already softened the issue.

The article on meeting drift is a good companion if you want a more technical structure for tracing proof. If your issue is broader leadership discipline, use decision latency to reset the management rhythm behind the follow-up itself.

Final recommendation

Use this case to audit your own closure routine. Ask whether a supervisor can prove the item is resolved in the field, whether repeat deviations get fast attention, and whether unfinished work still has a named owner after the meeting ends.

If the answer is no, the problem is not effort. The problem is that your operation is still treating follow-up like paperwork instead of control. When that changes, the field changes with it.