Why Your Safety Tools Aren't Increasing Engagement

Why Tools Don’t Create Engagement – Community Does

How everyday interactions shape contribution, engagement and performance.

In many conversations I hear the same challenges:

• Initiative overload

• Low engagement

• Difficulty demonstrating ROI

• Struggles gaining executive support

These show up regardless of industry, and across roles, from senior leaders to frontline

teams.

Across our profession, the toolset is surprisingly consistent.

• Audits.

• Observations.

• Learning teams.

• Incident reviews.

• Walks, tours, inspections.

Yet the outcomes vary widely. Some organisations steadily improve; others struggle to

create value. I’ve often found that those who struggle can respond by launching new

initiatives focused on the tools, but I have a question: If the tools are similar, something else must be shaping the results.

The missing piece

Very often, that “something else” is how people interact, and the environment, or

conditions, we create for those interactions. In other words, their community.

What do we mean by community?

A community is not a group of people who simply live in the same town or work in the same

company. In highperforming organisations, it is a group of people who help each other

succeed.

The same tools may exist in every organisation, but their impact changes depending on the

environment in which they’re used.

Organisations don’t behave like toolkits. People apply tools through a social operating

system, a community “filter” shaped over time by what helps their community. That operating system determines:

Over time, people learn how to “belong” or “fit in” to

that system.

Not by what they’re told, but by what they see.

You belong when you act in line with it.

If you don’t, you feel it.

So you share and improve what is important to your

social groups, and stay clear of what isn’t “socially

acceptable.”

Why perception shapes participation

I saw this clearly in an organisation where Fiona, an Operations Vice President, was leading

a group struggling to improve safety.

During a leadership meeting, observations were a discussion point.

Fiona laughed: “Employee observations are usually trivial,” she said.

Others in the room nodded, some laughed too, nothing dramatic, but it revealed something

about the social operating system, a “community insight.”

It wasn’t true that employees had nothing useful to say, what was true was that those with

influence had already decided the perceived value of the observation process to their social

group. That belief meant they were predicting what they would see, not what was there.

And the system adjusted because of that. Not consciously. But consistently.

What got noticed. What got acted on. What got shared.

The process didn’t fail, the social operating system didn’t allow it to succeed.

When contribution becomes capability

After much debate, we created a different question for Fiona to try:

“What change can we make that would help others?”

What happened next – her team looked for an answer.

One team of ecologists had already seen a problem. Insights from startofwork meetings

were disappearing into paperwork. So they changed it. They began recording observations

in a way that others could actually use.

They started sharing information within their own community so the next team arriving

didn’t have to rediscover everything. They could build on what was already known.

Nothing about the formal tool changed, but the adaptation had gone unseen.

Why?

Because no one believed it was worth sharing upwards, it didn’t fit what leadership believed

mattered, so the organisation came up with a workaround.

Sharing this story in the context of Fiona’s response changed a leadership belief. Now both

sides could see how their contribution shaped the system.

When leadership adjusted what was valued, capability became visible, and could be scaled,

but something deeper and more important followed.

Communities where contribution becomes capability will always outperform those where

contribution isn’t valued. The lesson wasn’t in a single team sharing information with

another, leadership attitudes shifted so that the whole organisation could see that their

contribution was valued.

Tools don’t drive culture

We often introduce tools expecting them to change behaviour. In reality, culture edits the

tool more than the tool edits culture.

If people believe:

• Sharing leads to help

• Problems lead to improvement

• Ideas are taken seriously

They contribute. If they don’t, they don’t.

And that difference determines whether performance improves.

Try this:

To understand how community shapes contribution everyday, pay attention to what

happens when:

• Someone raises a problem

• Someone suggests a better way

• Someone asks for help

Track what happens next.

Do people act on it, or move past it? Does the system build on it, or shut it down?

Over time, these responses become patterns that decide whether people contribute or

stay quiet. If you want to understand your culture, don’t start with a survey. Start with acts

and look for patterns. That’s where your community operating system becomes visible.

• Who acts to help others?

• Who acts to avoid helping others?

• Where is collaboration strongest and weakest?

Here lies your value proposition.

Why this matters

When communities work well, they shape contribution

positively, and organisational performance improves far

beyond safety outcomes alone.

Safety becomes one outcome, alongside quality,

reliability, wellbeing, and all other business metrics.

Final thought

If tools are consistent but results vary, the difference isn’t capability.

It’s whether people choose to contribute what they know, and that choice is shaped by the

community they experience every day.

If this feels familiar, you don’t need more tools.

You need to understand what your system does when people try to contribute.

That’s where change begins.

This has helped me see how everyday interactions shape what people choose to share, and

what happens when they do.

When those interactions support contribution, engagement and performance follow.

Close

If you want to get more from what you already have, more contribution, better

problemsolving, stronger performance, that’s the work we do.

Turning safety effort into real performance by adjusting systems to work for people, not the

other way around.

If you’d prefer to explore it first, this is the thinking behind The Invisible Script, described by

Dr Paul Zak as “a must-read playbook for high-performing leaders.”