• Mar 18

Ten Departments. One Airline: When the Organizational Chart Kills Value Flow

  • David Lapesa Barrera

A closer look at why airline organizational structures create silos, delay decisions, and generate cross-functional friction across the value stream.

In many airlines, the organizational chart looks clean, logical, and efficient. Clear reporting lines. Defined departments. Strong functional expertise.

And yet—value does not flow.

Aircraft are delayed waiting for decisions. Projects stall between departments. Continuous improvement initiatives lose momentum. Employees spend more time coordinating across silos than serving the operation.

The issue is rarely competence.
It is friction. Cross-functional friction.

The Illusion of Functional Efficiency

Organizational charts are necessary in aviation. Safety, compliance, and accountability demand clear authority. Regulators expect defined accountable managers. Financial control requires cost ownership. Engineering approvals require formal responsibility.

Hierarchy protects governance.

But traditional airline structures are built around functional departments: Flight Operations, Maintenance, Ground Operations, Commercial, Finance, HR, Safety, IT. Each department optimizes its own targets, budgets, and performance indicators.

Individually, they may perform well.

Collectively, they often create delays, duplication, and defensive behaviors.

A maintenance team optimizes hangar productivity while operations maximize aircraft utilization. Commercial pushes schedule density while ground handling struggles with turnaround constraints. Finance protects cost centers while frontline teams require investment to eliminate recurring operational waste.

The chart reinforces vertical loyalty.
The value stream requires horizontal collaboration.

When structure contradicts flow, friction becomes inevitable.

Where Friction Shows Up

Cross-functional friction appears in predictable ways:

  • Endless email chains to clarify responsibilities

  • Escalations for routine operational decisions

  • Projects requiring multiple steering committees

  • Improvement initiatives that stall between departments

  • KPIs that compete instead of align

Consider a simple aircraft turnaround. It touches crew, dispatch, maintenance, ground handling, catering, fuel, cleaning, and customer service. Yet in many airlines, each of these reports through different vertical chains with different performance objectives.

The passenger sees one airline.

Internally, the system behaves like separate companies negotiating at every step.

The result is hidden waste: waiting, rework, miscommunication, and defensive decision-making.

The Cost of Vertical Thinking

Vertical structures encourage local optimization. Leaders are evaluated on functional performance, not system performance.

This creates three dangerous patterns:

Boundary Protection
Departments protect resources and information to maintain control.

Blame Transfer
When targets are missed, responsibility moves sideways instead of being solved systemically.

Decision Bottlenecks
Cross-functional decisions escalate upward because no shared authority exists at operational level.

Over time, collaboration becomes negotiation.
Negotiation becomes politics.
Politics kills speed.

In aviation, speed and clarity are operational necessities.

Organizational Charts Are Not the Problem

The issue is not the chart itself. Airlines cannot operate without hierarchy.

The real problem emerges when the organizational chart becomes the dominant design principle — and value streams are an afterthought.

Aircraft do not move vertically through reporting lines.
Passengers do not experience departments.
Operational value flows horizontally.

If the structure ignores that reality, friction becomes structural.

Organizational Charts as Value Flow Enablers

An organizational chart should not only define reporting lines. It should coexist with clear value stream ownership.

In an airline, value flows:

  • From planning to aircraft preparation

  • From maintenance planning to release to service

  • From booking to check-in to boarding to arrival

  • From arrival to turnaround to next departure

If structure interrupts that flow, artificial barriers are created.

A simple question reveals alignment:

Does our structure make it easier or harder for value to move across functions?

If constant alignment meetings are required just to execute daily operations, the design may be misaligned with the work.

From Functional Silos to Value Streams

This does not mean eliminating expertise. Airlines require deep technical knowledge in safety, engineering, operations, and compliance.

But expertise must serve flow.

Lean organizations clarify:

  • Who owns the end-to-end process?

  • Who can solve cross-functional issues without escalation?

  • How are KPIs aligned to system performance rather than departmental output?

For example:

Instead of measuring maintenance solely on productivity, measure aircraft availability within operational context.
Instead of evaluating ground handling only on labor efficiency, measure full turnaround performance.

Shared metrics reduce friction because they reduce conflicting incentives.

Hierarchy remains.
But it no longer blocks flow.

The Role of Leadership

Structure alone does not eliminate friction. Leadership behavior determines whether silos harden or dissolve.

Cross-functional friction decreases when:

  • Leaders walk processes end-to-end

  • Improvement initiatives are co-owned across departments

  • Problems are solved at process level, not defended at hierarchy level

  • Recognition is tied to collaborative results

Organizational charts define authority.
Leadership defines how authority is used.

Signs Structural Friction Is Present

Watch for these signals:

  • Routine cross-functional adjustments require senior approval

  • Improvement projects stall between departments

  • Functional KPIs improve while overall performance stagnates

  • Employees say, “That’s not our responsibility”

  • Meetings exist primarily to negotiate priorities

If these patterns are frequent, the issue is not capability. It is design.

Final Reflection

Organizational charts are necessary in aviation. They provide safety, compliance, and accountability.

But they are not neutral. They shape incentives, behavior, and speed.

Airlines do not compete on how well departments perform independently. They compete on how seamlessly the entire system delivers safe, reliable service.

Hierarchy ensures control. Flow ensures performance.

When structure supports value streams, friction decreases.
When it ignores them, it quietly kills value flow.


Learn more about airline organizational structures and cross-functional management →


Author

David Lapesa Barrera is the founder of The Lean Airline® and author of The Lean Airline: Flight Excellence and Aircraft Maintenance Programs. His work focuses on lean management, operational excellence, and continuing airworthiness.