How to Build a High-Performance Safety Team in 90 Days

A high-performance safety team is not the group that produces the most reports. It is the group that can detect a serious exposure, make ownership visible, and change the work before the control fails. This 90-day guide is for an EHS manager who must build that operating rhythm with supervisors, operations, maintenance, and frontline representatives.

Team performance improves when the work system makes good decisions easier to see. A new team therefore needs more than a training calendar or a revised organization chart. It needs a short sequence in which the team defines its purpose, maps decision rights, tests field contact, and proves that unresolved risk moves to the person who can act.

Andreza Araujo's work connects safety leadership to operational choices rather than ceremonial visibility. In Make The Difference: Be a Leader in Health & Safety, she treats leadership as a daily practice that must reach the point where work is planned and released. The method below applies that principle without turning the EHS team into a policing function.

What you need before starting

Before the 90-day cycle begins, name one accountable sponsor, one EHS lead, and one operations partner who can remove barriers. Reserve two 30-minute team sessions each week, identify three critical-risk work processes, and collect the last 90 days of serious near-miss, stop-work, overdue-action, and control-verification evidence. Do not wait for perfect data, because the quality of the first review is itself a useful signal.

The team should also agree on four working rules. Questions about exposure are welcome, escalation does not require permission from a higher-ranking person, actions need an owner and a due date, and a closed action must include field evidence. Those rules create the conditions in which a technician can challenge a plan while the supervisor still retains operational accountability.

Step 1: Define the team’s decision purpose

Write one sentence that states which safety decisions the team exists to improve. A useful version is, “We help operations identify and control serious exposure before work starts or conditions change.” The sentence is deliberately narrower than “we own safety,” because vague ownership invites every unresolved problem to be sent to EHS.

Ask each member to name one decision that currently arrives too late, such as approving a temporary repair, accepting a control deviation, or releasing a contractor interface. Record the answers in a one-page decision map. When the team can state the decision it improves, its meetings stop becoming status reviews and start becoming control reviews.

Step 2: Select three critical-risk work processes

Choose three processes in which a weak decision could produce a fatal or permanently harmful outcome. Select them from actual work, not from the department’s favorite procedures. The list might include energy isolation, mobile-equipment interaction, confined-space entry, lifting, or a high-energy maintenance task.

For each process, document the intended control, the person who verifies it, the condition that invalidates it, and the evidence that proves it worked. This creates a small operating sample that the team can inspect every week, which is more useful than opening a large register that nobody can test in the field.

Step 3: Assign decision rights before assigning actions

Give every selected decision a clear owner, technical challenger, field verifier, and escalation route. The owner decides whether the work can proceed. The challenger tests assumptions. The verifier checks what is present at the point of work, while the escalation route defines what happens when evidence is incomplete.

Use names or roles, not the phrase “the safety team.” That phrase hides responsibility when a control is weak. If operations controls the schedule, equipment, and work release, operations must own the decision, while EHS provides technical judgment and challenge. Andreza Araujo’s leadership model is useful here because it places safety influence close to the decision without confusing influence with ownership.

Step 4: Build a 15-minute field contact routine

Schedule one short field contact for each of the three selected processes during the first 30 days. The contact should include the supervisor and at least one person who performs the work. Ask what can change, which control is hardest to maintain, and what would make the planned method unrealistic.

Do not turn the visit into an inspection theater. Capture one exposure, one condition that supports the control, and one question that still needs an answer. A field contact earns value when the team returns to the work after the meeting and verifies whether its decision improved the task.

For a practical comparison, the Headline article on tests for antifragile safety teams can help the team examine whether disruption produces better control or only more activity.

Step 5: Run a weekly evidence review

Use a fixed 30-minute agenda with four questions. Which serious exposure changed this week? Which control was verified in the field? Which action is late because the owner lacks authority or capacity? Which decision needs to be reopened before work continues?

Limit the meeting to evidence that can change a decision. A dashboard that contains 40 measures can still leave the team blind if none of them shows whether the critical control was present when the work occurred. The team should leave with no more than three decisions, each of which has an owner, a due date, and a verification method.

Step 6: Test one control under pressure

During days 31 to 60, choose one control and test it in the condition that usually weakens it. The test might involve a late material arrival, a contractor change, a night shift, a production interruption, or an unexpected equipment condition. The purpose is not to stage a failure. It is to see whether the control still guides behavior when the plan meets operational pressure.

Record what the team expected, what actually happened, and which decision right became unclear. If the control depends on a single experienced person remembering an unwritten step, the team has found a design weakness, not a reason to blame the operator.

The result should become a small redesign, such as a clearer hold point, a better handoff, a physical identification method, or a supervisor verification prompt. As Andreza Araujo shows through her safety-culture work, training has value when it reinforces a work system that allows the safe choice to succeed.

Step 7: Close the feedback loop within 7 days

Every question raised by the field must receive a visible response within 7 days, even when the final answer is that more evidence is needed. Tell the person who raised the concern what changed, who owns the next decision, and when the team will return to verify it.

This is the point at which psychological safety becomes an operational property. People keep speaking up when they can see that information travels somewhere useful. They stop speaking up when questions disappear into a mailbox, a meeting note, or an action list with no owner.

Step 8: Review the team’s performance at day 90

At day 90, review the team against five outputs. It should have a decision purpose, three tested critical-risk processes, named decision rights, field evidence from at least three contacts, and a record of changes that reached the work. Do not grade the team by meeting attendance or the number of actions created, because activity can rise while control quality falls.

Ask senior operations leaders one direct question: “Which safety-critical decision do you now make earlier or with better evidence?” Their answers show whether the team changed the operating system or only improved its internal language. If the answer is unclear, extend the cycle with one process and one decision rather than adding more committees.

What the EHS manager should keep after 90 days

Keep the decision map, the three-process control sample, the weekly evidence review, and the field feedback record. Retire forms that do not change a decision. The team should remain small enough to act, broad enough to understand the work, and disciplined enough to return to the field after every important judgment.

Andreza Araujo’s experience across 25+ years of multinational EHS leadership, including the 50% accident-ratio reduction achieved in six months at PepsiCo South America Foods, supports a practical conclusion. Safety teams create value when they help the organization make better decisions earlier, then verify that those decisions survive contact with real work. Leaders who want to develop that capability can explore Andreza Araujo’s books and guides or follow the conversations at Headline Podcast.

A team that cannot identify who can stop, change, or release high-risk work is not ready for the next serious decision. Clarify that authority before the next schedule pressure tests it.