How Leadership Follow-Up Cut a 50% Accident-Ratio Drop in Six Months

Across 25+ years leading EHS at multinationals, Andreza Araujo has seen the same failure pattern repeat: leaders ask for more reports, then treat the meeting as proof of control. It is not. In PepsiCo South America Foods, her 180-day plan led to a 50% reduction in accident ratio in six months, and the reason matters more than the number. The improvement came from tighter follow-up, clearer ownership, and field verification that forced each review to produce a decision.

On the Headline Podcast, Andreza Araujo often returns to the same point: if leadership is not present at the point of decision, the work will drift back to habit. This case shows that point in measurable form, because a dashboard can warn a team but only leadership can turn the warning into a change in the work itself. As Andreza Araujo argues in Make The Difference: Be a Leader in Health & Safety, the leader's job is not to add noise. It is to make the next step obvious, visible, and accountable.

Initial scenario

At the start, the operation had the usual signs of a mature safety routine: metrics, meeting cadence, and people who could repeat the right language. What it did not have was a loop that forced the review to change the work. The leaders could describe risk, but the field still had too much freedom to let an unresolved issue drift for another cycle.

That gap matters because a meeting without a decision creates a false sense of progress. The room becomes a place where people discharge concern, not a place where they convert concern into action.

Decision

The decision was simple and hard at the same time. Every recurring review had to end with a named owner, a due date, a verification method, and a rule for escalation when the field did not match the plan. Andreza Araujo's 180-day plan made the review less theatrical and more operational.

In Safety Culture: From Theory to Practice, Andreza Araujo describes maturity as the point where behavior, supervision, and systems stop sending different messages. This case is one of those moments. The message to the line changed from report and wait to report, decide, verify.

Execution

Execution happened in the rhythm of the week, not in a poster campaign. Supervisors and EHS teams focused on the few signals that repeated often enough to matter, then tied each one to a field check that someone could actually verify. The work moved faster when the owner of the risk was also the owner of the follow-up.

That is the piece many organizations miss. A corrective action is not finished when the spreadsheet is updated. It is finished when the field shows the change, because the field is where the next incident either survives or dies.

A related article on this site, How a LATAM Food Operation Turned Behavior Signals Into a 50% Accident-Ratio Drop, looks at the signal side of the same discipline, while Leadership Cadence: 4 Decisions Behind a 50% Accident-Ratio Drop shows how the meeting rhythm itself shapes the outcome.

James Reason helps explain why this works. The injury is visible, but the weakness usually sits upstream, in latent conditions that were allowed to stay in place because the organization kept talking after it should have decided.

Measured result

The number is important, yet the behavior behind it is the real lesson. The team stopped treating a status review as success and started treating verified closure as success.

What leaders usually miss

Three traps show up again and again. The first is believing that more meetings equal more control, when the opposite can be true if no decision leaves the room. The second is pushing every action onto the safety team, which trains line leaders to stay spectators. The third is accepting a low number as proof that nothing else needs attention, which is how organizations protect the metric and miss the work.

A fourth trap is thinking the leader can stay outside the loop once the action has been delegated. When that happens, the organization learns that accountability belongs to the slide, not to the work. Andreza Araujo's field experience across more than 250 projects points in the opposite direction. Credibility rises when the person with authority stays close enough to the verification step to be challenged by reality.

Generalizable lessons from the case

1. Close the loop in the room. If the leader leaves the meeting without an owner, a date, and a verification method, the organization learns that concern is enough.
2. Keep the action with the role that owns the work. EHS can support the process, but the line leader has to own the change if the work is going to hold.
3. Verify in the field. A closed item on paper is only a promise until the field proves it.
4. Use the review to shape behavior. Repetition of the right loop is how a mature culture becomes visible, which is why more than 250 transformation projects led by Andreza Araujo keep converging on the same lesson.

That last point aligns with the broader pattern in Andreza Araujo's work. Across more than 250 cultural-transformation projects and 30+ countries, the strongest gains come when leaders stop asking for reassurance and start asking for proof.

What to apply in your operation

If you want to adapt this case, start with one recurring signal, not ten. Pick the exposure that appears every week, define the one leader who owns the next move, and decide how the field will verify the change. That sequence matters more than a polished dashboard.

1. Name the signal. Choose the repeat issue that keeps creating delay or exposure.
2. Name the owner. The best owner is the person who can change the work, not only report on it.
3. Name the proof. Decide what the field will show when the action is real.
4. Name the review date. Bring the item back before it fades into the next agenda.
5. Name the escalation rule. If the field does not match the plan, the issue goes up, not around.

The point is not speed for its own sake. It is interval discipline. When leaders let two or three cycles pass without a check, the operation relearns delay, and the follow-up loses authority.

The operational test is simple. If the review closes with a name but the next field visit shows nothing changed, the loop is still decorative. If the same leader keeps showing up at the check, the action gets heavier, the team learns that follow-up is real, and the next review starts from a better place.

Andreza Araujo's case is useful because it resists the usual safety theater. No new acronym is needed. No poster is needed. The work changes when the leader refuses to confuse visibility with control and keeps the action alive until the field proves it.

FAQ

Why did follow-up matter more than more reporting?
Because reporting only names the problem. Follow-up changes the conditions that keep the problem alive.

Is this only relevant to multinational companies?
No. The scale changes, but the logic does not. A supervisor in one plant can use the same loop if the owner, the proof, and the date are clear.

How does James Reason fit this case?
His work helps explain why visible failures are usually downstream of latent conditions. The review loop has to reach those upstream conditions, not only the last event.

Which Andreza book should a leader read first?
Make The Difference: Be a Leader in Health & Safety if the problem is execution, or Safety Culture: From Theory to Practice if the problem is maturity and decision quality.

What is the fastest test of control?
Ask whether the next meeting will show a verified change in the field. If it will not, the action is still incomplete.

For teams that want to apply this now, begin with the next review, not with a new slogan. Put the owner, the due date, and the field check in the same room, then keep the conversation honest enough to finish the work. For the books and courses that support this discipline, visit Andreza Araujo's book store and Safety School.