Organisational Collaboration

In aviation, safety is rarely lost because one person makes a bad decision.

It is lost when good decisions don’t connect. 

Modern aviation organisations are made up of highly competent people working in specialised roles: 

• flight crew
• cabin crew
• dispatch and OCC
• engineering and maintenance
• ground handling
• training
• safety and compliance
• management and leadership

Each of these functions perform well in isolation. And yet, when things go wrong, investigations repeatedly uncover the same underlying issue:

The system did not fail, the interfaces did.

The Illusion of Coordination

In a mature organisation, collaboration often looks healthy.

Meetings are held. Emails are sent. Responsibilities are defined. Processes are documented.

But real operational collaboration is not about structure, it is about shared understanding. Complacency creeps in when organisations confuse:

• Communication with comprehension
• Coordination with connection
• Responsibility with ownership

And when everyone believes they are doing their part, it becomes harder to see the gaps between parts.

Safety Lives Between the Boxes

Most safety management systems are designed around functions. But most safety events happen between functions; at handovers; at shift changes; at organisational boundaries; at moments where assumptions replace confirmation.

Consider how often safety depends on:

• One department realising the downstream impact of its decision.
• Another department noticing that something has changed.
• Someone feeling confident enough to challenge “business as usual”.

When collaboration weakens, risk doesn’t increase suddenly — it accumulates quietly.

When No One Is Wrong and Something Still Goes Wrong

The most difficult safety events to understand are those where procedures were followed, competence was high, intent was good and outcomes were still poor

These are not failures of individuals. They are failures of alignment.

Each part of the system acted rationally, based on the information, priorities and pressures it could see. What was missing was a shared picture of risk.

Three Familiar Patterns of Collaboration Failure

Note: The following examples are fictional, but deeply familiar.

1) “We Thought They Knew”

Engineering identifies a recurring technical issue assessed as non–safety-critical. The issue is recorded, monitored, and deferred in accordance with established limits. Operational teams are not fully briefed on the basis that no immediate action is required.

Over time, the unresolved issue contributes to increased crew workload during a high-demand phase of flight.

All actions were compliant and individually reasonable. However, the operational relevance of the information was not effectively communicated, and the risk only emerged through the accumulation of small decisions across time and functions.

2) “That’s Not Our Decision”

A frontline team raises a concern that doesn’t clearly sit in any single department.

Operations sees it as a technical issue. Engineering sees it as an operational issue. Safety sees it as insufficiently defined.

The issue stalls, not because of disagreement, but because ownership is unclear.

Eventually, the concern fades away. So does the opportunity to learn!

Collaboration in a High-Performance System

In high-performing organisations, collaboration risks are harder to see.

Why? Because things usually work, trust is high and failure is rare. 

Ironically, this success makes it harder to challenge assumptions. People hesitate to ask:

• “Who else needs to know this?”
• “What happens downstream?”
• “Are we relying on luck here?”

Complacency thrives when collaboration is assumed rather than tested.

3) “Together” Is a Design Choice

Working together is not a cultural aspiration.

It is a design requirement. It requires organisations to:

• Deliberately design interfaces.
• Stress-test handovers.
• Clarify ownership of cross-cutting risks.
• Reward escalation, not silence.
• Create space for inconvenient questions.

True collaboration is visible when:

• Information flows faster than hierarchy.
• Concerns travel across silos.
• Safety decisions are shared, not delegated.

Safety Map Summary

🧠 Mindset
Safety is created between roles, not within them.

👥 People
Good people working in isolation can still create unsafe systems.

⚙️ Equipment
Technology connects systems — but people connect meaning.

📋 Compliance
Defined responsibilities matter, but shared ownership matters more.

⚠️ Risks
Handover failures, silo thinking, assumption-based decisions, and unclear ownership.

📚 Learning
Most collaboration failures are visible long before they cause harm — if we choose to look.

Short Summary & Call to Action

Aviation does not fail because people stop caring.

It fails when:

• Information doesn’t travel.
• Assumptions replace dialogue.
• Collaboration becomes implied instead of intentional.

 The call to action: This week, identify one interface you rely on for safety.

Then ask: “How do we know this works — and how would we notice if it didn’t?”

Because safety is not something we deliver individually.

It is something we create — together.