How to Build Trust With a New Safety Team in 90 Days

A new safety leader often arrives with a plan, a mandate, and a calendar full of meetings. The team does not yet know whether that plan will protect people, create more paperwork, or disappear when production pressure rises. Trust is therefore not an opening speech. It is the evidence people collect from your decisions during the first 90 days.

This guide gives a new plant safety manager or EHS leader a practical sequence for earning that evidence. The aim is not to become popular. The aim is to make it safer for people to tell the truth about risk, while making responsibility and follow-up visible enough that the team can believe the system is changing.

Step 1: Define what trust must make possible

Start by naming the operational behavior that trust should unlock. In a safety team, trust should make it easier to surface bad news, challenge an unsafe plan, ask for help, and report when a control did not work as intended. If the goal remains a vague statement such as “build a strong culture,” your first 90 days will fill with activity that is difficult to evaluate.

Write three observable outcomes for the quarter. For example, supervisors escalate changes in critical work before the task begins, workers can identify who owns a risk decision, and corrective actions receive a clear response rather than disappearing into a tracker. These outcomes give you a test for every meeting and field visit.

Use the same definition with the safety team, operations leaders, and worker representatives. A shared definition reduces the risk that one group treats trust as friendliness while another treats it as permission to avoid accountability.

Step 2: Listen before you redesign

Spend the first two weeks collecting evidence from different levels of the operation. Speak with operators, supervisors, maintenance planners, contractors, engineers, and the people who close corrective actions. Ask each person where risk information becomes distorted, which decision takes too long, and what happens after someone raises a concern.

Do not begin by asking people whether they trust leadership. That question produces a general opinion, not a usable diagnosis. Ask for a recent example instead. “Tell me about the last time the work changed after the plan was approved” reveals more than a score because it exposes the path between information and action.

Record patterns without attaching names to criticism. James Reason's work on organizational accidents reminds leaders that visible behavior is often the final layer of a chain that includes design, supervision, workload, and management decisions. Listening is valuable when it helps you locate those layers rather than when it creates a collection of complaints.

For a structured reference, connect this listening phase with the evidence approach described in Safety Culture Audit vs Climate Survey vs Field Verification. The point is to compare what people say, what leaders record, and what the field actually shows.

Step 3: Make one small safety promise and keep it

Trust grows faster from a completed promise than from a large vision. Choose one issue that the team has raised repeatedly and that you can move without waiting for a full transformation program. It might be an unclear escalation route, a corrective action that has remained open without an owner, or a field control that is checked inconsistently.

State the promise in operational language. Instead of saying that you will “improve communication,” say that every high-consequence concern raised during the weekly review will receive an owner, a due date, and a written response within two working days. Only promise a cadence you can maintain.

Then publish the result, including what you could not change. A transparent boundary is more credible than a confident promise that quietly expires. The team should be able to compare your words with the next decision without needing access to a private leadership conversation.

Step 4: Put decision rights where risk appears

New leaders often try to build trust by keeping every important safety decision close to themselves. That creates the opposite effect because the frontline waits for permission, supervisors learn to escalate everything, and urgent risk can remain unowned between meetings.

Define four levels of decision rights. The person closest to the work can pause an activity when a critical control is absent. The supervisor can change the sequence or resource the control. The operations manager can accept a temporary constraint only within a documented boundary. The senior leader can decide on exposure that requires capital, schedule, or design changes.

For each level, state what evidence must be present before the decision is made and who must be informed afterward. This turns trust into a system property rather than a personality test. The safety decision rights matrix guide can help you convert this discussion into a usable operating document.

Never confuse delegation with abandonment. A leader who assigns decision rights still owns the quality of the boundary, the resources behind it, and the response when someone uses the authority in good faith.

Step 5: Show up where work changes

Field presence matters only when it produces better decisions. A tour that collects observations without removing a barrier teaches the team that visibility is performance theater. A useful visit follows a work change, a non-routine task, a schedule compression, or a handoff where the plan may no longer match reality.

Ask questions that reveal the conditions around the task. What changed since the work was planned? Which control is carrying the most consequence? What would make the crew stop? Who can authorize a change if the control cannot be maintained? These questions keep the conversation focused on risk and responsibility rather than on finding a person to correct.

Close the loop before leaving or state exactly when you will return with an answer. A field visit becomes credible when people can see how their information changed a permit, a sequence, a resource decision, or a management review.

For a concise behavioral model, use the three practices in Visible Felt Leadership Explained, then adapt them to the work rather than copying a script.

Step 6: Respond well to bad news

The first serious concern raised to a new leader is a test that cannot be staged. If the response is defensive, the team learns to edit future information. If the response is curious but vague, people learn that speaking up is emotionally safe but operationally pointless. A credible response combines respect with a clear next action.

Begin by thanking the person for making the risk visible. Ask what happened, what was expected, and what changed. Separate the immediate condition from the deeper system question, because correcting the visible act alone can leave the pressure, design, or supervision problem untouched.

Give the person a time for the next update. If an investigation or engineering review is required, explain who owns it and what decision will be made. Do not promise a result before the evidence exists. People do not need you to agree with every concern, but they do need to know that the concern will not vanish after the conversation.

When the issue involves a disagreement about work, use the same disciplined response described in How to Receive Bad News in 8 Supervisor Steps. The method protects both worker voice and managerial accountability.

Step 7: Reward evidence, not optimism

A new team watches what receives attention. If leaders praise a green dashboard more than a well-supported escalation, people will protect the appearance of control. If leaders examine a red signal without humiliating the person who raised it, the organization gets a better view of exposure.

During weekly reviews, ask what evidence supports the status and what evidence could disprove it. Review field verification, control tests, overdue actions, changed work, and unresolved concerns alongside injury data. Do not treat a higher number of reports as automatic deterioration, because reporting volume can rise when information starts moving.

Andreza Araujo makes this distinction central in Safety Culture: From Theory to Practice. A safety value becomes credible through repeated behavior, especially when the operation is under pressure. That position is more demanding than asking people to display confidence, because it requires leaders to make room for inconvenient evidence.

Step 8: Review the first 90 days with the team

At the end of the period, do not issue a self-congratulatory scorecard. Bring the team back to the three outcomes you defined in Step 1 and ask where the system now behaves differently. Which concerns receive faster responses? Which decision still has no clear owner? Which group remains least willing to raise a problem?

Compare the original listening themes with current field evidence. A successful first 90 days does not mean every risk is solved. It means people can see a more reliable path from concern to decision, and leaders can identify where that path still breaks.

Publish the next three priorities with an owner, a review cadence, and a reason for the sequence. Trust is not completed at day 90. The first cycle simply proves whether your leadership can turn attention into consistent action.

What a credible first 90 days looks like

A new safety leader earns trust when the team can predict the response to important information. People know how to raise a concern, who can pause the work, which evidence supports a decision, and when leadership will return with an answer. That predictability is built through listening, small promises, clear decision rights, field presence, and fair follow-up.

The practical test is simple. When the plan and the field no longer match, does the organization make the mismatch visible and adjust the work? If the answer is yes more often than it was on day one, the new leader is building a safety culture that can withstand pressure rather than merely describing one.

Explore Andreza Araujo's safety leadership resources for further guidance on turning leadership consistency into daily practice.