Behaviour-Based Safety (BBS) has helped organisations reduce injuries across industries worldwide. But across Qatar, Saudi Arabia, and the wider GCC, it often under-delivers — not because the concept is flawed, but because the way it’s rolled out doesn’t match the reality on site.

In many cases, the numbers look great: observation targets hit, cards completed, dashboards filled. Then a serious incident happens and everyone is left asking the same question: If the system is working, why are we still seeing the same high-risk failures?

The gap is rarely about effort. It’s usually about context.

The Gap Between Promise and Practice

At its best, BBS is simple:
observe work as it really happens, have a short, respectful coaching conversation, reinforce what’s working, and remove the barriers that push people toward unsafe shortcuts.

But in the Gulf, BBS often turns into something else:

• A compliance programme judged by how many cards get submitted
• A reporting tool that flows upward — but doesn’t come back down as action
• A system workers don’t fully trust, especially when they think it can be used against them

When that happens, BBS becomes “busy work” instead of a culture tool. And the workforce quickly learns the difference.

Why Standard BBS Programmes Break Down in This Region

BBS isn’t failing because people in the Middle East “don’t care about safety.” It fails because standard, imported models assume conditions that often don’t exist on GCC projects.

1) Hierarchy makes honest conversations harder

In high power-distance environments, it’s not easy — or always culturally acceptable — to challenge a supervisor, question a decision, or openly point out unsafe behaviour. Many workers will avoid anything that feels like confrontation or “speaking up.”

If BBS depends on front-line workers freely calling out risk to people above them, that assumption needs to be adapted, not defended.

2) Language and cultural nuance get lost

Major projects routinely bring together teams speaking Malayalam, Bengali, Hindi, Tagalog, Urdu, Nepali, Arabic, and more. Yet observation cards and coaching scripts are often in English, and training is delivered in English.

Even when workers can follow basic instructions, the coaching conversation — the part that actually changes behaviour — is where nuance matters. If the language doesn’t land, the impact doesn’t land.

3) Short rotations disrupt trust

BBS works best when observers know the crews, the crews know the observers, and trust builds over time.

But frequent reassignment, short visa cycles, and package-to-package movement can reset relationships just as they start to work. In that environment, BBS becomes transactional: “tick the card and move on.”

4) Data gets collected… and then nothing happens

If workers see observations being recorded but hazards staying the same, they conclude (reasonably) that the programme is performative.

Once the workforce believes BBS doesn’t lead to real improvements, engagement collapses — even if observation totals stay high.

5) BBS gets confused with discipline

This is the fastest way to kill a BBS programme.

If workers think BBS is a tool to identify who to blame, they will stop being honest. They’ll only report what’s “safe enough to say,” and the programme becomes a theatre of compliance.

What Actually Predicts Whether BBS Works

Across industries and regions, a few fundamentals show up again and again:

• Visible leadership commitment (not slogans — action)
• Capable observers who can coach, not police
• Closed feedback loops so workers see follow-through
• Clear separation between coaching and discipline

Those are always important. In the GCC context, they’re non-negotiable — because the baseline barriers (hierarchy, language, turnover, and trust) are higher.

Key Failure Points at a Glance

• High power-distance culture suppressing open reporting
• Multilingual workforces without translated, contextualised tools
• Short workforce rotation cycles disrupting observer relationships
• Observation data not visibly driving corrective action
• BBS confused with punitive performance management
• Insufficient supervisor capability and ownership of the process

How to Fix It: A Practical Framework

None of the failure modes above are inevitable. The organisations that make BBS work in the Gulf don’t do “more BBS.” They do better BBS — and they design it around their real workforce conditions.

1) Localise — properly

Translation alone isn’t enough. Tools need to be translated and culturally adapted so the intent survives in the local language.

Coaching phrases, ways of correcting, and how feedback is given all carry cultural meaning. If the wording feels disrespectful, confrontational, or confusing, the conversation will shut down.

2) Start with supervisors, not cards

A common sequencing mistake is rolling out observation programmes before supervisors are ready to receive and act on them.

If supervisors respond defensively, ignore feedback, or treat observations as a nuisance, the workforce will follow their lead — and the programme will quietly fail.

What works is structured supervisor development: how to listen, how to respond without blame, how to remove barriers, and how to model the same behaviours they’re expecting from crews.

3) Close the loop — publicly and consistently

When an observation identifies an unsafe condition, there must be a visible response.

Even if the fix isn’t immediate, people need to see that it was taken seriously:

• what was raised
• what was done
• what’s pending and why

Posting anonymised “You said / We did” summaries in crew areas and toolbox talks is simple — and it’s one of the quickest ways to rebuild belief in the system.

4) Separate coaching from discipline — structurally

This needs to be more than a policy statement.

It needs consistent operational behaviour:

• Observations used for learning and improvement
• Discipline handled through separate processes
• Leadership messaging reinforced by what actually happens on site

Where trust has been damaged in the past, rebuilding it takes time — and steady leadership consistency.

5) Design for continuity in a mobile workforce

If rotation is unavoidable, design the BBS system so it doesn’t reset every time people move.

That can include:

• simple crew-level BBS histories
• safety “passports” or continuity notes
• pairing mobile observers with stable crew leads
• handover practices for observers, not just operations

The goal is to carry learning forward instead of starting from zero

6) Anchor BBS in visible leadership behaviour

In high power-distance cultures, what senior leaders do carries disproportionate weight.

If site leadership is seen having real coaching conversations, acting on feedback, and discussing what’s being learned — not just what’s being counted — it changes the tone of the whole programme.

Beyond Compliance: BBS as a Diagnostic Tool

The biggest missed opportunity with BBS in the GCC is treating it as a numbers exercise.

A strong BBS programme is a diagnostic system for answering:

• What are the real pressures shaping how work is done?
• Where does work-as-planned differ from work-as-done?
• What site conditions are quietly pushing people toward risk?

If leadership looks at BBS data and only asks, “Did we meet our observation target?” they’re managing by spreadsheet.

A better question is:
“What are we learning — and what are we changing because of it?”

One genuine coaching conversation, followed by visible action, will beat twenty completed cards every time.

The Path Forward

BBS isn’t a failed methodology. In the Middle East, it’s a methodology that demands contextual intelligence.

If you want BBS to work across Qatar, Saudi Arabia, and the wider GCC, the investment has to go beyond observation forms:

• translation and cultural adaptation
• supervisor capability and confidence
• trust-building through non-punitive practice
• visible follow-through
• leadership behaviour that makes safety conversations normal

The organisations that lead safety performance in this region won’t be the ones with the most observation cards.

They’ll be the ones with the most honest conversations — and the most consistent follow-through.

How “Lead to Inspire” Helps Us Navigate These Challenges

Many of the issues that derail BBS in the Gulf aren’t technical problems — they’re leadership and culture problems.

That’s why Demoura Lawson Consulting’s Lead to Inspire Safety Workshop is built around a simple truth: the actions and behaviours of leaders and managers shape the safety culture of the whole organisation.

The workshop focuses on helping leaders see (and own) the impact of what they say and do — because culture shifts fastest when leaders lead by example, not by instruction. When leaders work on improving their own safety culture and modelling the standard, the impact doesn’t stay at the top; it echoes through the organisation.

It also challenges a common trap in safety management: treating safety like “driving while only looking in the rear-view mirror” — managing only what already happened. Instead, leaders are pushed to define what “safe” actually means for their organisation, and to make sure everyone understands that standard.

In practical terms, that leadership shift helps unlock the exact BBS blockers we see most often in the region:

• Trust: when workers see leaders respond fairly and consistently, reporting improves
• Hierarchy pressure: when leaders invite feedback and act on it, speaking up becomes safer
• Follow-through: when leaders model closing the loop, the programme stops feeling performative
• Consistency: when leaders act based on what they know is right (not just “how we’ve always done it”), coaching replaces blame

And the goal isn’t just better numbers. The intended outcome is fewer accidents, injuries, and close calls — alongside better morale, productivity, and a stronger chance that people go home safe at the end of the day.