High-Performance EHS Team: Build One Without Firefighting

A high-performance EHS team is not the team that answers every call, joins every meeting, and repairs every weak process by personal effort. It is the team that makes the right safety decision visible, assigns the work to the person who can control it, and verifies the result before the risk returns.

This distinction matters when production pressure rises. A department can look busy while its EHS professionals remain trapped in incident response, document corrections, and last-minute approvals. The work feels urgent, yet the operating system stays weak. The guide below is for EHS managers and safety leaders who need to build a team that improves control quality without creating a permanent firefighting culture.

Across more than 25 years of multinational EHS leadership, Andreza Araujo has seen that performance depends less on individual heroics than on repeated decisions. Her experience across more than 250 cultural transformation projects and operations in more than 30 countries supports the same practical thesis found in Safety Culture: From Theory to Practice. The team becomes credible when its decisions can be followed from the field to the leadership table.

What you need before starting

Choose one operating unit, one leadership sponsor, and one 30-day improvement window. Do not begin by rewriting every job description. Begin with the work that currently consumes the team, such as overdue actions, repeated incident reviews, permit exceptions, or unresolved field concerns.

Collect four kinds of evidence. Review the team structure, the last 10 recurring requests, the most recent field-verification records, and the three safety measures leaders already use. Include one worker, one supervisor, one operations manager, and one EHS representative in the first review, because a team cannot improve its interface with the operation from inside the EHS office.

Write down the decision you want to improve. For example, the objective may be to decide within 24 hours whether a temporary control is acceptable, to close high-risk actions within 30 days, or to escalate a serious exposure before production scheduling makes it harder to stop. A precise decision gives the team a testable outcome.

Step 1: Map the decisions before assigning tasks

List the decisions that the EHS team influences during a normal week. Include risk acceptance, work authorization, incident escalation, contractor readiness, control verification, emergency response, and action closure. Then identify who owns each decision, who supplies evidence, who must be consulted, and who has authority to stop or delay the work.

The verification question is whether two people would make the same decision when faced with the same evidence. If the answer depends on which EHS professional is available, the team has a person-dependent system. The common error is to describe responsibilities as activities, such as auditing or training, without defining the decisions those activities must support.

Use the boundaries between accountability and blame to separate ownership from personal fault. A named owner is responsible for moving the decision and proving the control. That does not mean the owner caused every condition that made the decision difficult.

Step 2: Separate expertise from ownership

Technical expertise and operational ownership are related, but they are not interchangeable. The EHS engineer may explain the exposure, the supervisor may control the task, and the maintenance manager may control the equipment condition. If the team assigns every problem to EHS because EHS understands the hazard, the operation never develops control ownership.

Create a simple responsibility map with three fields. The first field states who must decide. The second states who must act. The third states what evidence proves that the action worked. Keep the map close to the daily work rather than hiding it in a policy manual.

Check one recent action that was marked complete. If the only evidence is an uploaded photograph, a training attendance sheet, or an email saying “done,” the team has not yet separated activity from control effectiveness. A high-performance team asks what changed at the point of work and who can demonstrate that change.

Step 3: Design a field rhythm that leaders can sustain

Set a weekly rhythm with a clear purpose for each contact. One field visit should test critical controls, one conversation should surface operational constraints, and one review should remove decisions that are stuck. The schedule can be short, but it must be protected from being replaced by meetings that produce no field action.

Use the six questions that reveal whether leaders see the real work when preparing a field visit. The goal is not to collect more observations. It is to discover where the approved method, the available control, and the work sequence no longer match.

Ask each team member to record one changed condition, one control that worked, and one decision that needs escalation. That three-part record creates a common language across shifts. It also prevents the field rhythm from becoming a tour whose only output is a list of photographs.

Step 4: Build competence around decisions, not attendance

Training should prepare people to make and explain a decision. For each critical responsibility, define the evidence a competent person must recognize, the judgment they must exercise, and the action they must take when the condition changes.

A supervisor who completed four hours of training may still be unable to recognize an unstable barrier during a live task. Conversely, a supervisor who can explain the exposure, identify the control, and stop the job when the control weakens provides stronger evidence of competence. The four evidence types in a competence matrix help the EHS team test that difference.

Run one practical verification every 30 days for the first quarter. Use a real task, a changed condition, or a short decision scenario. Record what the person noticed, what they chose, and what support would make the safer decision easier next time.

Step 5: Replace the hero queue with an escalation path

Firefighting grows when every issue arrives through the most available EHS person. Replace that queue with three escalation levels. The first level is a local correction that the supervisor can close during the shift. The second level requires a manager decision because resources, sequencing, or equipment ownership must change. The third level concerns a serious exposure, a repeated control failure, or a decision that could create irreversible harm.

Set response expectations for each level. A local correction may be reviewed before the next handover, a management decision may require a 24-hour response, and a serious exposure should be escalated immediately through the site’s established emergency process. These time windows are operating rules for the team, not a substitute for the site’s legal or emergency requirements.

Review the path after two weeks. If people still bypass supervisors and send every question directly to EHS, the issue may be trust, unclear authority, or a history of leaders ignoring bad news. The answer is not to create another mailbox. It is to make the escalation response visible.

Step 6: Give the team a small set of useful measures

Choose measures that show whether the team is improving decisions. A practical set can include the age of high-risk actions, the percentage of critical controls verified in the field, and the time between a serious concern and a named management decision. These measures do not replace injury rates. They show whether the preventive work is moving before an injury provides the response.

Review the measures once a week with the people who can change them. If the EHS team owns the dashboard but cannot influence action closure, equipment readiness, or supervisor response, the dashboard will become a report about frustration. The measure must lead to a decision, an owner, and a next verification date.

Andreza Araujo’s book The Illusion of Compliance is useful here because a completed form can create the appearance of performance while the underlying work remains unchanged. Count what leaders can act on, then test whether the action reached the field.

Step 7: Make disagreement part of the operating method

A strong EHS team does not agree quickly just to protect the meeting schedule. It explains which evidence supports the decision, which evidence is missing, and what would change the conclusion. That discipline is especially important when production targets, maintenance deadlines, and safety concerns compete for the same window.

Ask the person with the closest view of the task to speak before the senior person gives an opinion. Invite one contrary interpretation, then verify it in the work area. Amy Edmondson’s research on psychological safety helps explain why people are more likely to surface concerns when leaders respond to information with curiosity rather than humiliation.

The practical test is whether a worker can challenge a control without becoming the problem. If the team thanks the person, checks the condition, and records the decision, disagreement becomes an early-warning mechanism rather than a personal confrontation.

Step 8: Close the 30-day build with a leadership review

At the end of 30 days, review the team against five questions. Are decision owners clear? Does the escalation path work under pressure? Can field evidence show whether controls are effective? Are measures producing decisions? Does the operation now own more of the controls that it must sustain?

Use a short before-and-after table with the original problem, the new decision rule, the owner, and the evidence of change. If the team reduced its open action age but did not improve field verification, say so. Honest evidence is more useful than a perfect score because it shows where the next constraint sits.

Then set the next 60-day priority. A team that tries to fix every interface at once will return to firefighting. A team that chooses one decision family, verifies it, and expands only after the method works can build capacity without hiding weakness.

Final checklist

• Define the decisions the EHS team must improve before assigning more activities.
• Name the decision owner, action owner, evidence owner, and escalation route.
• Protect a weekly field rhythm that tests controls instead of collecting tours.
• Verify competence through real decisions, changed conditions, and observable actions.
• Use three or fewer measures that produce a named decision and follow-up date.
• Review the 30-day result honestly, then choose one 60-day priority.

FAQ

What makes an EHS team high performance?

A high-performance EHS team makes safety decisions clear, timely, and connected to field evidence. Its members know who owns the decision, who must act, what proof is required, and when an issue must be escalated. The team does not measure value by how many requests it absorbs. It measures whether the operation can recognize serious exposure, apply the right control, and sustain that control without permanent dependence on EHS heroics.

How large should an EHS team be?

There is no responsible universal headcount because team size depends on risk profile, operating hours, geographic spread, legal duties, and the complexity of the work. Start by mapping the decisions and response obligations that must be covered across each shift. If critical decisions have no owner or if field verification is routinely postponed, the organization has a capacity or design problem that a simple headcount comparison cannot solve.

How can an EHS manager reduce firefighting?

Begin with the last 10 urgent requests and classify each one by decision, owner, evidence, and escalation level. Repeated requests usually reveal unclear authority, weak control ownership, or a missing field-verification routine. Set response expectations, move local corrections to supervisors, and reserve EHS escalation for issues that require technical judgment or management action. Review the pattern after 14 days rather than waiting for an annual planning cycle.

What is the difference between EHS activity and EHS performance?

EHS activity describes what people did, such as training, inspections, meetings, or reports. EHS performance describes what changed in the risk control and whether the change stayed effective under operating conditions. A completed training record does not prove that a supervisor can recognize a weakened barrier. A field verification that tests the supervisor’s judgment provides stronger evidence. The distinction is central to Safety Culture: From Theory to Practice by Andreza Araujo.

How should an EHS team work with safety culture leaders?

The EHS team should connect technical controls with the repeated decisions that leaders reward, tolerate, and review. A safety culture leader can help identify where compliance language hides weak ownership, while the EHS team can define the evidence that shows whether the control works. The four evidence layers of safety culture provide a useful way to connect stated values with shift decisions. This partnership is stronger when both sides stay close to the work.

A high-performance EHS team is built when the operation can make safer decisions without waiting for a hero. Start with one decision family, prove the control in the field, and expand the method after 30 days.