Leadership Escalation Case: 250+ Projects

Leadership escalation is the management rhythm that moves safety risk from field observation to accountable decision before exposure becomes normal. In a multi-site organization, it defines who can stop, who must decide, which evidence travels upward, and how fast unresolved risk returns to the field as visible action.

The Bureau of Labor Statistics reported 5,070 fatal work injuries in the United States in 2024, with one worker dying every 104 minutes from a work-related injury. This case study shows how leadership escalation changes when safety is treated as a decision system, not as a campaign that waits for injuries to prove risk.

1. What was the initial scenario?

The initial scenario was familiar across large operations: hazards were visible locally, but decision authority was too slow, too vague, or too dependent on the personal courage of one supervisor. In more than 250+ cultural transformation projects supported by Andreza Araujo, this pattern appears when sites have reporting channels, dashboards, and meetings, although the unresolved risk still returns to the same crew the next day.

The Headline Podcast often describes safety as a real conversation among constantly learning people, and that language matters here because escalation fails first as a conversation failure. A worker raises a concern, a supervisor recognizes the exposure, an EHS manager records the issue, and the organization still does not decide who owns the change.

OSHA identifies management leadership as a core element of effective safety and health programs because leaders provide the vision, resources, and expected performance. The case pattern shows the same point from the field: without authority, even accurate information becomes a parked issue.

That is why this article sits beside executive safety sponsorship. Sponsorship is not a speech about commitment; it is the decision architecture that tells the organization what happens when a risk has no local owner.

2. Which decision changed the case?

The decision that changed the case was separating reporting from escalation, because a report says what happened while escalation says who must decide by when. Across 25+ years leading EHS in multinational environments, Andreza Araujo has seen that leaders often mistake a clean reporting channel for control, even when the same hazard repeats across 3 sites or 3 shifts.

As Andreza explores in *Safety Culture: From Theory to Practice*, culture becomes visible in routine choices under pressure. If a plant manager accepts a blocked emergency route for 30 days because the dashboard is green, the culture is not defined by the written value statement. It is defined by the tolerated delay.

The practical move is to create 3 escalation levels. Level 1 belongs to the supervisor when the fix is local and can be verified within 24 hours. Level 2 belongs to the plant or functional leader when the fix requires staffing, budget, maintenance priority, or operational rescheduling. Level 3 belongs to the executive sponsor when the exposure crosses sites, repeats after closure, or affects serious injury and fatality potential.

This is also where safety decision rights become visible. A company does not need louder reporting if the real weakness is that no one knows which leader has the right and obligation to interrupt production.

3. How did execution look across sites?

Execution across sites looked like a weekly operating rhythm with 4 fixed questions: what risk is repeating, who owns the decision, what evidence proves the fix, and when will the field see the change. ISO 45001:2018 specifies requirements for an occupational health and safety management system, including planning, operation, evaluation, and improvement, but the case lesson is that those verbs need named owners.

In Headline terms, the useful conversation is not whether people care about safety. The useful conversation is whether the system moves risk with enough speed and authority. A regional EHS team can coach, audit, and compare patterns, although only line leadership can change staffing, sequencing, capital priorities, or production incentives.

The strongest execution rhythm used a 30-day loop. Week 1 classified repeated risks, week 2 assigned leadership owners, week 3 verified field action, and week 4 reviewed whether the same exposure had returned. When the exposure returned, the item moved up one escalation level instead of being closed again with better wording.

That loop connects directly to visible felt leadership, because workers judge escalation by whether leaders return to the field with action. A closed action in software is not closure if the crew still sees the same blocked access, missing tool, or unstable work sequence.

4. What result should leaders measure?

Leaders should measure whether escalation reduces repeat exposure, not whether the organization creates more safety reports. OSHA states that worker participation includes reporting hazards and hearing what actions were taken, which means the quality of the response matters as much as the existence of the channel.

A useful escalation dashboard has 5 measures: repeat risk count, age of unresolved Level 2 and Level 3 items, percent verified in the field, recurrence after closure, and executive decisions made before an injury. These measures tell leaders whether safety information is reaching authority or only circulating inside EHS.

Andreza Araujo's work across 30+ countries reinforces a blunt lesson: the dashboard can look mature while the field has learned that hard issues move slowly. That is why control health and SIF exposure metrics matter more than a neat count of completed corrective actions.

5 escalation measures are enough for a monthly executive review because the point is not to build a heavier dashboard. The point is to make delayed authority impossible to hide.

5. Where did the system drift?

The system drifted when leaders treated escalation as an exception rather than a normal part of safety governance. Once escalation depends on personal bravery, the organization teaches supervisors to absorb risk locally until a serious event forces attention.

The first drift point is language. Teams say an issue was "communicated" when no one accepted ownership. The second is age. A Level 2 risk older than 14 days often signals leadership delay rather than technical complexity. The third is recurrence, because a closed item that returns within 60 days was usually not closed at the level where the decision belonged.

This is where Andreza's book *A Ilusao da Conformidade*, translated as *The Illusion of Compliance*, gives the case its sharper edge. The appearance of control can become more dangerous than visible disorder, since leaders stop looking once the form, meeting, or action tracker says complete.

In practical terms, every repeated high-potential condition should trigger a short governance review. The question is not only why the control failed. The question is why the organization allowed the same control weakness to remain local after evidence showed it was structural.

6. How should executives compare weak and strong escalation?

Executives should compare escalation systems by the speed and quality of decisions they produce, not by the number of reports they receive. A weak system moves information upward without moving authority downward or across, while a strong system makes every unresolved exposure visible to the leader who can remove it.

The comparison below is designed for a 30-minute monthly safety governance review. It helps senior leaders see whether they are receiving evidence of risk or merely receiving proof that people filled out the process.

The table also explains why safety culture drift can hide inside a disciplined management system. Leaders may see movement, meetings, and closure, while the field sees that difficult risk still waits for permission.

7. What should a leadership team do in the next 30 days?

A leadership team should use the next 30 days to test escalation with real unresolved issues, because a redesigned chart means little until it changes one decision. Pick 10 recent safety concerns, including at least 3 repeated conditions, and ask whether each had the correct owner, deadline, evidence standard, and field verification.

Start with a small governance trial. In week 1, define Level 1, Level 2, and Level 3 triggers. In week 2, apply those triggers to 10 open issues. In week 3, verify whether field crews saw any changed work. In week 4, review recurrence and move any repeated exposure up one level.

On Headline Podcast, co-hosts Andreza Araujo and Dr. Megan Tranter often return to the difference between talking about safety and changing the system that carries risk. Leadership escalation belongs in that difference, because it turns uncomfortable information into a named decision rather than a polite record.

Each month that unresolved risk stays trapped below the leader who can decide, the workforce learns a quiet rule: report the issue, but do not expect the system to move.

Conclusion

Leadership escalation works when it makes risk travel to the level of authority fast enough to change work, and the 250+ project pattern shows that reporting alone rarely does that.

If your organization wants better safety conversations at executive and field level, listen to Headline Podcast and use this case to test whether risk is reaching the leaders who can actually remove it.