The Cultural Operating System: Why Some Organizations Improve and Others Stay Stuck

If We All Use the Same Tools, Why Do Some Organizations Improve, and Others Stay Stuck?

At recent CHOLearning conferences, our community surfaced several persistent challenges:

• initiative overload

• low engagement

• difficulty demonstrating ROI

• struggles gaining executive support

These themes appeared across roles: senior leaders, operational leaders, consultants, and emerging practitioners.

In earlier articles in this series, we explored two of the signals behind these challenges.

First, we looked at how value often appears between contribution and capability, when people’s knowledge helps improve how work is actually done.

Second, we explored why organisations often respond to problems by adding initiatives, accidentally creating the very overload many teams experience.

That brings us to a deeper question:

If many organisations use the same tools, why do some steadily improve while others remain stuck?

Across our profession, the toolset is surprisingly consistent.

Audits.

Observations.

Learning teams.

Incident reviews.

Walks, tours and inspections.

Yet the outcomes vary widely.

Some organisations steadily improve.

Others remain locked in cycles of new initiatives, low engagement, and difficulty demonstrating value.

If the tools are similar, something else must be shaping the results.

Very often, that “something else” is the way people interact while doing the work.

In other words, the community.

What Do We Mean by Community?

Community is often described in broad or abstract ways. But in organisations, we can define it very practically.

A community is not a group of people who happen to work together. It is a group of people who help each other succeed.

Community is where shared success begins to feel part of people’s identity.

The same tools may exist in every organisation. But their impact changes dramatically depending on the environment in which they are used.

If attention stays on the tools while the operating system is ignored, performance will eventually suffer.

Organisations cannot behave like toolkits. People apply tools through the organisation’s cultural operating system.

It is this operating system that determines which contributions are welcomed, ignored, or even ridiculed.

And that operating system is largely created by the dominant sense of community:the patterns of interaction, expectations, and stories people hold about one another.

Why Perception Shapes Participation

I saw this dynamic clearly in an organisation where Fiona, an Operations Vice President, was leading a group where employee observations were of low quality.

During a leadership meeting, the topic came up and Fiona laughed.

Employee observations, she said, were usually trivial. Others in the room nodded and laughed as well.

That moment revealed something important.

It wasn’t that employees had nothing useful to say. It was that the organisation had already decided what counted as valuable.

Psychologists sometimes describe this phenomenon through the “red car effect.”

When you decide that red cars are important, your brain suddenly begins noticing red cars everywhere.  The cars were always there, but your attention filters changed.

Organisations behave in much the same way.

If leaders believe employee observations are trivial, their attention naturally focuses on examples that confirm that belief.

Over time, the system quietly trains people to submit observations that match the expectation.

The community narrative becomes self-reinforcing.

“We ask for input, but it’s rarely useful.”

Fiona and I discussed this at length.

Familiar leadership words surfaced: ownership, engagement, buy-in.But the more interesting question was this:

What questions are leaders asking that make certain answers more likely than others?

If leaders ask for ten observations per month, they may hit the target and miss the point.

So Fiona paused and asked a different question: 

“What would we see if employees believed their observations could genuinely improve how work is done?”

That question changed the conversation.

Leaders began to look for observations not as compliance data, but as contributions.

And when employees saw their input taken seriously, something changed.

The quality of observations improved.

But something else changed too.

People began adapting the system themselves.

In other words, the community had started to edit its own operating system.

When Contribution Becomes Capability

One example came from a team of ecologists working on environmental surveys.

They noticed that useful information from start-of-work meetings mostly disappeared into paperwork.

Months later, when another ecology team returned to the same location, they had to rediscover the same conditions all over again.

Instead of waiting for a corporate solution, the ecologists adapted the tool themselves.

They began recording environmental observations electronically in a way future survey teams could easily access.

They agreed a simple shared structure so someone returning months later could quickly understand what had already been seen.

The next time another team returned to the same site, those records helped them plan their work far more effectively.

A simple contribution had quietly increased the organisation’s capability.

The idea was eventually recognised in the company’s CEO awards.

But the real shift had already happened long before the award.

Nothing about the formal tool had changed.

What changed was the community operating system.

People believed their contribution mattered.

They believed they were allowed to shape how the work was done, not just follow the process as written.

And when contribution increased, capability followed.

People quickly learn which contributions matter, and which ones don’t.

Communities where contribution reliably becomes capability will always outperform communities where contribution quietly dies in a spreadsheet.

Human Performance Principles Through a Community Lens

Many organisations are already familiar with the core Human and Organisational Performance principles.

What is sometimes less visible is how strongly these principles depend on the surrounding community.

HOP Principle	Community Behaviour That Enables It
Individual behaviour is influenced by organisational processes and values.	The operating system of the organisation, its expectations, incentives, and stories, quietly shapes how people use tools and make decisions.
People achieve high performance through encouragement and reinforcement.	Community signals determine participation. What leaders and peers notice, reinforce, or ignore teaches people what kind of contribution is welcome.

Seen this way, the principles are not implemented through tools. They are expressed through community behaviour.

Tools, Culture, and the Operating System

This example highlights something many organisations experience but rarely articulate.

Tools are important.  But tools alone rarely transform organisations.

A useful analogy comes from technology.

Applications perform specific tasks. But applications only work well when the operating system supporting them is aligned.

Organisations behave in much the same way.

What we often describe as culture, trust, collaboration, or learning are not separate initiatives.

They are characteristics of the organisational operating system: the conditions shaping how people interact, solve problems, and make decisions.

When that operating system supports contribution and learning, tools amplify improvement.

When it does not, tools can easily become additional work without visible benefit.

Our profession often introduces tools expecting them to change culture. In reality, culture edits the tool long before the tool edits the culture.

Why This Matters for Our Community

For our colleagues in the CHOLearning community, this perspective shifts where improvement efforts focus.

The goal is not simply to introduce better tools; it is to strengthen the conditions that allow people to contribute to solving real problems in their work.

When communities operate this way:

• problems become visible earlier

• knowledge spreads more easily

• learning accelerates

• capability grows

And when capability grows, performance improves.

Safety becomes one of the outcomes, alongside quality, reliability, and human wellbeing.

Tools harness capability, community creates contribution, performance needs both.

A Few Questions for You, and for Us

If community acts as the organisation’s operating system, then tools behave more like applications.

The question is not only what tools we use, but what the system does when people try to use them.

Every operating system has default responses, the code that determines what happens next.

In organisations, those defaults become visible in everyday moments such as these:

1. When someone raises an observation or concern, what is the default response?Does the system encourage curiosity and learning, or does it quickly move toward accountability?

2. When work becomes difficult or conditions change, what does the system reinforce?Do people collaborate to adapt the situation, or do they reinforce compliance expectations?

3. When someone contributes a better way of working, how does the system respond?Is the contribution recognised as new capability, or absorbed into process with little impact?

These responses reveal something deeper than any tool or programme.

They reveal the default code of the organisational operating system.

If the same responses appear again and again, organisations may not need another tool. 

They may need an operating system upgrade to re-shape how tools are used.

Closing Thought

Our profession has developed many valuable tools over the years.

But tools alone do not create improvement.

Improvement emerges when the organisational community supports contribution, learning, and capability.

When that happens, value appears naturally in everyday work.

And safer outcomes follow.

The tools you already have may be enough.

The real leverage may lie in how your community chooses to use them —and in whose contributions are invited to shape what happens next.