A Committee That Actually Changes How People Work: Redesigning Safety Culture Meetings

A safety culture committee can easily turn into just another routine meeting. Statistics, site reports, discussion, minutes. Everyone gives their update and goes back to their desks, while managers continue working the exact same way as before.

We redesigned the format several times. Here is what we tried, where we went wrong, and what we ultimately settled on.

Reports: From Thirty Slides to Four Questions

At one of our earliest meetings, presentations ate up almost all the time. Sites brought 20- to 30-slide decks, and each talked about something different: one focused on risks, another on non-conformities, and a third on completed actions. Comparing them and spotting systemic issues was difficult.

For the next session, we cut presentations down to 7–10 minutes and gave everyone the same template: one result, one problem, one significant risk, and one decision needed. The meeting became manageable, but we overcorrected. Identical slides and a flood of numbers made the reports indistinguishable. You could no longer tell what was actually hurting a specific site.

Our takeaway: identical slide decks are unnecessary. What you need are shared questions, while each leader decides how best to answer them. There are four questions: where the pain point is, what has already been tried, what fell short, and what decision is needed.

Discussing Strategy After Visiting the Shop Floor

We once tried presenting the strategy framework before the breakout sessions. It seemed logical: set the direction first, then fill in the details. The document fell flat. Nobody objected—people simply lacked a shared picture of reality to build on.

We had to flip the agenda. In the morning, brief updates and a candid conversation about where things stand. In the afternoon, going out to operational areas. In the evening, debriefing observations, working in breakout groups, and only then tackling strategy.

After time on the shop floor, the exact same document landed differently. Participants could map its points directly to what they had seen with their own eyes earlier that day. The strategy stopped looking like paperwork handed down from above. Instead, it addressed the very problems people had just identified themselves.

Safety Walks With a Specific Assignment

Simply getting leaders out onto the shop floor guarantees nothing. Without a clear objective, a site walk turns into a sightseeing tour.

Now every group has its own observation focus, assigned in advance:

• The first group looks at how compensating controls for a critical red risk are being carried out in practice.
• The second examines how a contractor's maintenance area is set up.
• The third observes how a frontline supervisor runs a pre-job risk briefing.
• The fourth checks what actually changed on the ground after corrective actions were taken for a specific incident.

What should they come back with? Answers to three questions: what we saw, what it tells us about our management system, and what decision is required. Simply walking a route is not enough to answer them. Leaders have to talk with workers and dig into the situation on the spot.

Groups bring these answers to the evening debrief.

Real Discussion Does Not Happen on Its Own

When one person speaks and the room listens, there is no discussion. Asking people to "participate more actively" rarely works.

We started building short polls, live voting, direct questions to participants, and breakout sessions into the agenda ahead of time. We made mistakes there too. If five groups get the exact same question, by the fourth reportout everyone is repeating one another and the room tunes out.

Now each group gets a distinct assignment, and we train facilitators in advance. Keeping time is only a small part of their job. A facilitator prevents one voice from dominating the conversation, draws in quieter participants, steers the group back from tangents toward a concrete decision, and captures the outcome.

We still haven't beaten smartphones. Asking people to put them away only works briefly. Active engagement works much better: when you are asked a direct question or tasked with presenting on behalf of your group, passive attendance becomes much harder.

How to Wrap Up

"We need to strengthen our efforts" is phrasing that changes almost nothing. By the end of a committee meeting, it must be clear who owns each action, what exactly needs to be done, by what deadline, and when the interim checkpoint will take place.

For instance, instead of a vague action item to "address maintenance risks," the workstream is assigned to a specific executive. They have a clear roadmap and a set date to demonstrate initial results.

Even that is not enough. If nobody works with those roadmaps, tracks status updates, or reviews interim progress between sessions, the next committee meeting will start with reminders about overdue tasks. That is why we now treat the committee as just one link in a continuous cycle: preparation, discussion, decision, execution, verification, and the next review.

What We Still Struggle With

We are still looking for an honest way to measure the committee's impact. Injury rates shift slowly and depend on dozens of factors. Tying them to a single meeting would be misleading.

Logistics remain heavy. Every session means a new host site, new walk routes, and new coordination, turning preparation into a standalone project. We need a repeatable standard that can be handed off smoothly.

And one final point. Appointing a workstream owner is only the beginning. Real results appear later, once that leader pulls a team together, carves out dedicated time, and turns the roadmap into tangible change on the ground.

In short, we stopped judging the committee by how smoothly the meeting went. Instead, we look at what we agreed on—and what actually happened to those commitments by the time we meet again.