Where EBITDA Leaks: The Hidden Cost of Operational Friction

EBITDA rarely disappears all at once

Margin erodes gradually, shaped by how work moves across the system over time. Revenue can remain stable, activity can remain high, and teams can remain fully engaged, yet financial performance still falls short of expectation.

The signals are subtle. Delivery continues, customers are served, and the organisation appears to function as intended. There is no clear point of failure. Instead, there is a gradual shift in how effort translates into outcome, and it is within that shift that margin begins to move.

Performance holds while friction builds

Operational performance often appears stable for a sustained period. Targets are approached, service levels are maintained, and the system continues to deliver. Underneath, the conditions of delivery begin to change.

As organisations grow, layers of interaction increase. Coordination expands, more stakeholders become involved, and dependencies between teams deepen. Decisions take longer to resolve, ownership becomes less defined, and processes begin to rely on local adaptation.

Each change appears manageable in isolation. Together, they slow the flow of work and increase the effort required to sustain performance. Delivery continues, but at a rising cost.

Effort sustains performance while cost accumulates

Capable teams respond to increasing complexity by applying more effort. They communicate more frequently, align more closely, and invest additional time managing dependencies. Activity rises to maintain output.

This response stabilises performance in the short term. Over time, the system becomes dependent on effort rather than design. Manual workarounds become embedded, variation increases, and the true cost of delivery becomes less visible.

Operational activity remains high, while the relationship between effort and outcome weakens. Margin adjusts as the cost of maintaining performance continues to rise.

The system absorbs inefficiency

As these patterns develop, inefficiency becomes part of normal operations. Each adjustment supports continued delivery, and the organisation adapts without structural change. The system absorbs the friction.

Additional layers of control are introduced to manage complexity. Reporting expands, oversight increases, and coordination becomes more formalised. These actions stabilise outcomes while adding further interaction into the system.

The organisation remains functional and performance appears consistent. Margin continues to move through the cumulative effect of small inefficiencies across the system.

EBITDA follows the path of the system

EBITDA forms as an output of how the operating system functions over time. It reflects how decisions move, how ownership is defined, how processes perform under pressure, and how capability is applied across the organisation.

Where flow is maintained, performance is sustained with lower effort and greater consistency. Where friction accumulates, the cost of maintaining performance increases and margin adjusts accordingly.

Most organisations carry more capability than their performance reflects. The system determines how that capability is used. Friction shapes the system.

Margin follows the path of work.

A simple diagnostic

EBITDA leakage is usually embedded in how the system behaves day to day.

A small number of questions can surface where it sits:

• How quickly do pricing and commercial decisions respond to changes in cost or demand?
• How visible is cost-to-serve across products, customers, and channels?
• How well does labour flex with changes in volume and demand?
• Where do processes rely on exceptions, workarounds, or manual intervention?
• Which customers or activities consume disproportionate operational effort?
• Where have costs gradually become embedded without clear ownership or challenge?
• How consistently are performance, cost, and actions reviewed and followed through?

Patterns across these answers indicate where friction is shaping outcomes.

Understanding where leakage exists is the first step. Designing the system to remove it is what changes performance.