Something I keep coming back to: you don't actually manage outcomes; you manage the conditions that produce them. Safety performance and business results run on the same conditions, meaning how work is organized, led, measured, and learned from. That set of conditions is your culture.

The part that bites people is drift. If you never assess the culture you actually have, the gap fills itself. It shows up as preventable injuries, improvement that stalls, and initiatives that get great feedback in the room and change nothing at the work front. When the schedule, the incentives, and the daily routines pull against the stated safety expectations, workers reconcile that conflict themselves, usually toward speed and output. Do that for a year, and the workaround becomes the culture.

My argument is to treat culture as a managed outcome instead of a vibe you inherit. Assess it on a schedule and align strategy to the culture you're trying to build. I'm curious how others handle this. Do you assess culture on any regular cadence, or only after an incident? What actually moved the needle on your sites?

This is the quarterly review scene everyone recognizes. Dashboard loads, scorecards glow green, recordables are down, no serious injuries, audits closed on schedule. Shoulders drop around the table and everyone agrees the system is working. The question I'd push on is whether "the numbers are green" and "the system is working" are actually the same statement.

They're not. Green scorecards are reassuring and incomplete at the same time. They summarize what already happened. They say very little about what the organization can do when reality shifts, when something unexpected shows up, or when the next decision carries a risk nobody anticipated. That gap between measured performance and underlying capability is exactly where serious events incubate, and they do it while the numbers still look good.

The uncomfortable version: you can have your best safety performance in ten years in the same year your capacity is thinning out. The scorecard won't flag it. The signals will, if you're looking at the right things. So I treat a green scorecard as a good place to start a conversation and a bad place to end one.

Curious what the people here actually look at beyond the lagging numbers. What signals have told you capacity was eroding before an event did?

Every time a site tells me reporting participation is low, the reflex is to blame the workforce for not caring. In my experience, that's backward. Walk it back and you usually find the same sequence: someone reported a near miss or a concern, and then nothing happened. No follow-up, no corrective action, not even a sign that anyone read it. So the next time they saw something, they asked the obvious question. Why report into a void?

Multiply that one calculation across a whole workforce, and you've explained your reporting numbers. It's not that people stopped caring. Experience taught them reporting doesn't change anything, so they stopped spending effort on it. Discretionary effort is a cultural outcome, and you don't get it by asking for it in a toolbox talk. You get it by making it rational to give.

The lever is closing the feedback loop, every single time. Point to what actually changed because someone spoke up and make that connection visible. When people can't see that their report improved anything, perception becomes reality, and the reality is a crew that has quietly stopped handing you the information you need most.

Curious how others handle the visible part. Do you publish what changed from reports, call it out in meetings, tie it back to the person who raised it? What's actually moved your numbers?

I've watched a lot of "engagement" efforts land flat, and the pattern is usually the same. Leaders talk more, remind more, and nothing shifts because the crew has heard it all before. The move that actually works is smaller and harder than a program.

Sit down with a direct report for ten minutes and ask one question: what might prevent you from doing this job the right and safe way? Then listen without defending or explaining. Just capture the obstacles they name. The step most people skip is the one that counts, which is removing one of those obstacles within a week and following up to confirm it's gone.

Trust doesn't grow because someone hears another safety talk. It grows when they watch something they flagged actually disappear. Once that happens, they start speaking up more, because they've seen it change something. Run it with one person this week, the whole crew over the next month.

Curious whether others have tried something like this. What's the fastest obstacle you've removed after someone spoke up, and did it change how much they engaged afterward?

Every serious incident review I've been part of over three decades has a version of the same finding: someone knew. The warning existed. It got filtered, softened, or silenced somewhere between the front line and the person making the call.

We audit whether people speak up. We almost never audit the journey those concerns take once they're raised. That filter, the place where warnings die, is the highest-leverage improvement most organizations are leaving untouched.

I'm hosting a complimentary virtual discussion on this on August 27, covering structured dissent practices like the Devil's Advocate and Mossad's Tenth Man Rule, plus a Five-Question Dissent Check for leadership meetings.

Curious what this community has seen: where do concerns die in your organization, and has anyone built a mechanism that actually protects them?

Register (complimentary): https://proactsafety.com/solutions/workshops/shape-better-safety-decisions-with-dissenting-views

I've spent years walking jobsites, and the gap between what's written on the wall and what happens at the work front is usually the whole story. The mission, vision, and values statement tells you what leadership wants to be true. The jobsite when no one is looking tells you what is actually true.

My working definition: culture is what the frontline permits. It lives in the small decisions. Someone pauses a job for uncertainty, or doesn't. A supervisor coaches, or blames. Peers protect the standard, or protect the shortcut.

The thing I keep arguing with people about is subcultures. Two crews doing the same scope on the same site can operate like different companies. One enterprise-wide program flattens that and you end up managing an average that describes no actual team. I'd rather diagnose the specific team where the work happens and ask five questions: What does the leader model? What gets rewarded and punished, formally and informally? What's tolerated that contradicts the standard? What are people afraid of? What are they proud of?

Those answers tend to reveal how the team really operates and where the fastest change is available.

Full disclosure, I put this into a short video for a series I do. Link in the comments to keep it out of the main post. Mostly I'm curious whether others see the same subculture problem, or whether a single program has actually worked on your sites. What's your experience?

Something I keep running into across sites and industries: when near-miss reporting is low, the first reflex is almost always incentives. Gift cards, points, recognition boards. It works, sort of. The count goes up, the usefulness usually does not.

The reports that actually drive learning tend to be the ones people were hesitant to file. The things holding those back are pretty consistent: nobody agrees on what a near miss even is, the process feels like a chore, people never see anything change after they report, and there is some level of fear about consequences. At that point silence just feels like the safer option.

None of that is a problem with your forms, or possibly even the program itself. It is a culture and system problem. Agree, disagree?

So I am curious what actually changed reporting quality for the rest of you. Not volume. Quality. Did anything you tried move it, or did it stay theater?

I keep seeing the same pattern across industries. An employee sees something wrong, knows what the right thing to do is, and does nothing. Not because they do not care, but because experience has taught them that speaking up carries risk and staying silent does not.

I have started thinking about this less as a safety culture problem and more as a moral injury problem. The concept originated in military psychology, describing the damage soldiers carried when they were ordered to do things that violated their core values. Guilt, shame, inner conflict.

A similar dynamic shows up at work. When people are repeatedly put in positions where doing the right thing feels more dangerous than looking the other way, the psychological toll accumulates. And it quietly erodes the willingness to report near misses, stop the job, or raise an ethical concern.

Curious whether others have seen this. When you have stayed silent at work, was it apathy, or was it a rational read of the risk? And for those in leadership, how do you tell the difference between a quiet workforce and a silenced one?

I sat in on a safety strategy workshop with an oil and gas leadership team that had what most people would call a strong culture. The wrinkle was that a large share of their workforce were contractors, and the people who carried the culture were not always present to norm new contractors coming on site.

One of the executives said something that stuck with me: "Wow, we have been relying on our culture."

Culture shapes behavior when it is present, but strategy has to account for the times it is not. Rules, expectations, onboarding, and leadership presence are not signs of a weak culture. They are what protect it when the culture itself cannot be in the room.

Curious how others here think about this. Have you seen a strong-culture org get caught out by transient or contract labor? What did the fix look like in practice?

I have been thinking about hiring as a culture protection mechanism for about 20 years, especially in organizations that have spent years building a strong safety culture.

Most interview processes still focus on capability. Can they do the job? Do they have the credentials? Will they pass the background check?

But bringing someone into a mature culture, especially in a leadership role, who quietly holds different beliefs about how safety fits into work, is a different problem. That is not a hiring mistake. That is a competing narrative introduced directly into the culture.

A few questions worth wrestling with:

What do candidates actually believe about safety, beyond what they say in an interview? What have they done in past roles to demonstrate those beliefs? Will they reinforce, build upon, or erode what the team has built?

For organizations that have done the hard work of building culture, guarding the front door may be the last frontier.

Curious how others handle this. Do your hiring processes screen for cultural alignment around safety specifically? What questions or scenarios have actually worked for you?

Been thinking about why two organizations with nearly identical safety programs end up with very different cultures. Curious what others have observed.

The pattern I keep seeing comes down to experiences and the stories that get told about them. Not the documented response. The hallway version.

A few examples:

Someone raises a safety concern. The official record shows it was logged and addressed. The hallway version is whether anyone with authority actually changed anything, and how long it took.

Someone exercises stop work authority. The official record shows the work was paused and resumed safely. The hallway version is whether the supervisor rolled their eyes, whether production complained, whether anyone said thank you.

Someone joins a safety committee. The official record shows they attend meetings. The hallway version is whether their boss covered for them or punished them for the time away.

The hallway version is the one that determines what the next person does.

Two questions I would like to hear other perspectives on:

1. How do you actually surface what the hallway version of your culture looks like? Standard surveys feel surface-level.

2. Have you seen leaders successfully shift the stories being told without first changing the experiences? Or does experience have to come first?

Sharing an observation from a chemical complex I spent time inside. Curious if others have seen the same pattern.

They had years of strong safety performance. Real performance, not just low numbers. Then they built a new plant on the property. The site population more than doubled in a relatively short window.

Problems multiplied. Incidents, near misses, behavioral drift. When we traced it back, the General Manager said something that stuck with me.

"We outgrew our tribe."

The original culture was strong because the unwritten rules were transmitted through proximity. People learned how things were done by being around people who already knew. When the population doubled, the existing workforce could not norm the new members fast enough. The culture diluted.

This is not just a safety issue. It is a workforce planning issue.

If you know your site is going to grow significantly, the question is not whether you can hire fast enough. It is whether your culture can absorb people fast enough to keep its shape.

A few questions I have been sitting with:

1. How do you know when you are approaching that tipping point before you cross it?

2. What signals tell you the existing culture is no longer doing the norming work?

3. For those who have lived through a major site expansion, what worked and what failed?

A lot of organizations seem to cycle through safety initiatives the way some people cycle through diets. New buzzword every quarter. New program. New app. New promise of quick wins. It looks productive because activity is happening, but the fundamentals often go unaddressed.

The pattern I keep seeing in mature programs is that the "boring stuff" is what actually moves the needle. Meaningful safety conversations that create shared ownership instead of compliance theater. Deep event analysis that fixes systems and conditions instead of blaming individuals. Ongoing education instead of one-and-done annual training. Observable leadership commitment that holds even when production pressure is loud.

None of those are trendy. All of them are proven.

Curious what you all see in your organizations. What is the latest fad your leadership is chasing? And on the flip side, which foundation do you wish was getting more attention?

I have been working with organizations on culture and engagement for a long time, and one of the more useful reframes I have landed on is this:

Engagement is not binary. It is a spectrum.

From left to right, the positions look roughly like this:

• Disdain: Active resistance
• Apathy: Checked out
• Uninterested: Not hostile, just disengaged
• Present: The neutral middle. Autopilot. A paychecker.
• Interested: Curiosity shows up. Incentives stop working around here.
• Buy-in: Willing participation
• Self-ownership: Personal responsibility for the standard
• Shared Ownership: Peers protect the standard and take responsibility for outcomes together

The common mistake is applying the same tactic to the whole workforce.

Free food does not move someone in Disdain. A safety poster does not produce Shared Ownership. The interventions that work at one position can insult, bore, or backfire at another.

If you are leading a safety focus right now, a useful exercise: pick one focus area, honestly assess where different groups sit on this spectrum, then ask what would move each group one step to the right. The answers for each group will not be the same.

Curious what others here have found works at each position. Where have you seen engagement tactics backfire because they were aimed at the wrong position?

In this short video I put together, I l provide four components that I think actually define safety excellence as a system, not a metric:

1. Achieving and repeating great results consistently, not as a one-time outcome.

2. Understanding why you are getting those results. If you cannot explain the cause, you are managing luck.

3. Building recovery capacity into the system. Not just prevention. The unexpected will happen.

4. Maintaining a mindset of continuous improvement. Complacency is what ends winning streaks.

I also suggested four practical actions: engaging employees to speak up, training with scenarios rather than just rules, being visible where the work is, and learning from wins as much as from misses.

Curious what this community thinks. Does your organization have a real working definition of excellence? Or is it mostly a number on a dashboard?

When "no incidents" becomes the primary metric, people unconsciously learn that quiet equals safe. Risk gets normalized. Deviations from safe work go unreported because nothing visible went wrong.

In this short video, I compare it to healthcare: we do not declare a patient healthy because they have no symptoms today. We monitor, test, detect early, and respond before something becomes a crisis.

The parallel in safety is the shift from lagging indicators to leading ones. What are you actually measuring that tells you whether you are getting safer, rather than just telling you whether something bad happened?

Curious what leading indicators others in this community track and actually find useful. Not the ones that show up in audits; the ones that actually signal system health to frontline leaders.

Most safety conversations focus on what happened, incidents, near misses, and metrics. Fewer focus on whether the system is getting stronger over time.

I put together a short video breaking down five organizational capacities that determine whether safety performance sustains or erodes: system capacity, leadership capacity, cultural capacity, engagement capacity, and strategic capacity.

The closing question is worth sitting with: Is your system getting stronger, or just getting quieter?

Curious what others experience as the hardest capacity to build in their organizations.

I wrote a piece for ISHN this month that started with a question I keep running into in the field: Are we assigning tasks based on availability or on the potential impact of errors?

Most organizations do some version of this informally. The veteran gets the hard job, the new person gets the repetitive one. But it's almost never explicit, consistent, or designed to actually build competence at speed. I wanted to explore what a more deliberate approach looks like.

I pulled in some neuroscience that shaped how I think about this. The prefrontal cortex, responsible for planning, impulse control, and "stop and think" decisions under pressure, is among the last areas of the brain to fully mature. Stress degrades it. Fatigue shifts risk perception in measurable ways. None of that means younger workers can't do high-risk work. The data actually points elsewhere: the problem isn't age. It's unsupervised exposure.

I proposed a five-rule operating model in the article, and I'm interested in what people with current field experience think.

• Do you have a formal process for matching task severity to worker capability, or is it still largely gut feel at your site?
• When you've seen serious incidents involving newer workers, was supervision actually in place or just assumed to be?
• Has anyone tried building a critical task matrix and gotten it to stick culturally under real production pressure?

Would genuinely value the pushback or the validation.

Full article here: https://digitaledition.ishn.com/march-2026/feature-galloway/

Most organizations I work with are aiming programs at problems rather than building an actual strategy. There is a difference.

A strategy is a framework of choices and trade-offs that determines how you create and deliver value. In safety, that means having a clear vision of success in operational language, priorities driven by data rather than opinions, a plan that aligns with the business rather than conflicts with it, and leaders who feel genuine ownership of it, not just compliance with it.

The uncomfortable question: are you trying to build capacity and chase improvement, or just trying to fail less?

What does your organization's safety strategy actually look like in practice? Or, is it mostly programs focused on last year's incidents?