Operational Excellence Programs Are Not Enough. It’s Execution Physics That Determines EBITDA

Most industrial companies pursue operational excellence through programs. Lean initiatives. Continuous improvement roadmaps. Digital dashboards. Yet many still struggle with the same operational symptoms year after year. Lead times expand. Inventory grows. Delivery performance becomes fragile.

The reason is rarely effort. The teams are capable. The initiatives are sincere. The intentions are right.

The problem is that performance in complex industrial systems is governed by something more fundamental than any program can address. I call it execution physics.

After spending over three decades working inside complex industrial operations, and later advising manufacturers and private equity portfolio companies, one pattern appears more consistently than any other. Organizations pursue operational excellence through programs and initiatives, but performance is ultimately shaped by structural forces that govern how work moves through the system. When those forces are understood and managed, results improve. When they are ignored, no program can fully compensate.

This article is the first in a series exploring those forces and how they connect directly to EBITDA, working capital, and enterprise value.

The Execution Physics Framework

Operational excellence consulting work, at its best, starts by recognizing that industrial systems are not simply collections of processes. They are governed by three structural forces.

Flow describes how smoothly work moves from order to completion. When flow is strong, work advances predictably through each stage of production. When flow breaks down, queues form, priorities collide, and supervisors start making judgment calls that introduce even more variability.

Variability describes the volatility introduced by demand, product mix, supplier behavior, and process inconsistencies. Every industrial operation contains variability. The question is whether the system is designed to absorb it or whether variability is allowed to multiply unchecked through the value stream.

Constraints are the resources that ultimately limit throughput. Every system has one. In most organizations, the constraint is not identified deliberately – it is discovered accidentally, usually when a critical delivery is at risk and leadership is asking why the system cannot respond faster.

When these three forces align – when flow is stable, variability is managed, and the constraint is protected – the results are measurable: lead times compress, throughput increases, working capital declines, and EBITDA improves.

When they conflict, the opposite happens: queues expand, priorities collide, expediting becomes a way of life, and margins erode. Often months before leadership sees the financial impact.

What You See on the Floor

Walk almost any factory long enough and you will see the moment execution control begins to break down.

Supervisors are chasing parts. Queues are building between operations. Schedules are changing hourly. The expediting board is full. Operators know what they are supposed to be doing, but they have learned that the list will change before the shift ends.

These are not discipline problems. They are not capability problems. They are symptoms of a system that is violating execution physics and programs layered on top of that system will not fix the underlying structure.

This is the essential distinction between traditional continuous improvement work and what I mean by execution physics: one addresses visible inefficiencies inside a broken system; the other addresses the system itself.

Why Operational Excellence Programs Are Not Enough

The appeal of operational excellence programs is real. They provide structure,  build skills,  create shared language across an organization, and often produce genuine early results.

But programs alone cannot govern a system. They cannot determine how much work should be released to the factory floor at one time. They cannot protect a constraint from being overloaded and cannot stabilize flow when demand volatility and internal variability are both rising simultaneously.

To illustrate: one question I often ask leadership teams is deceptively simple: How do you decide how much work gets released to the factory at one time?

In manymost organizations, that decision is distributed across several functions: sales, planning, engineering, and operations. Each function makes reasonable local decisions. Together, they frequently flood the system. When total work-in-process exceeds the system’s absorption capacity, congestion grows rapidly, lead times expand, and everything becomes more expensive to manage.

This is not a failure of effort. It is a failure of system governance. And no lean event or improvement initiative can fix a system governance problem.

EBITDA Is the Output of Flow

Many leaders assume EBITDA is primarily a function of effort; that if the team works harder and smarter, the numbers will improve. In reality, EBITDA is heavily influenced by flow stability.

Flow determines revenue timing. It influences working capital intensity. It shapes inventory exposure and service reliability. When flow deteriorates, financial performance eventually follows. The lag is often three to six months, which means by the time EBITDA reflects the problem, the operational conditions causing it have been present for some time.

This delay creates a dangerous blind spot. Leadership often responds to financial symptoms (margin compression, inventory growth, premium freight) with financial solutions, when the actual root cause is a system that is no longer flowing effectively.

Restoring flow is not primarily a financial exercise. It is an operational one. But it has direct financial consequences, which is why the most effective operational excellence consulting engagements are structured around financial outcomes from the beginning.

The Execution Physics Series

Over the next several weeks, this series will explore how execution physics shapes performance across a range of industrial environments: from private equity portfolio companies operating under hold-period pressure, to aerospace and defense contractors balancing compliance requirements with operational efficiency, to high-mix manufacturers trying to apply lean principles in complex environments.

Each article will follow the same structure: identify the underlying execution physics at work, examine how it shows up in practice, and offer a diagnostic question that leaders can use to assess their own systems.

The goal is not a framework for its own sake. The goal is to help industrial leaders and their operational teams connect what they see on the floor to what appears, months later, in financial results.

The next article examines one of the most overlooked drivers of execution instability: excessive work-in-process. WIP itself is not the problem. Every manufacturing system needs a healthy level of WIP to protect flow and absorb normal variation. Excessive WIP quietly destroys margins, working capital, and delivery reliability when it exceeds the system’s ability to absorb it.

Diagnostic question for this week: How do you decide how much work gets released to the factory at one time, and who actually governs that decision?

The answer will tell you more about your execution system than most performance dashboards ever will.

Want to talk about your challenges?

Let’s connect.

Execution Physics vs Operational Excellence Programs FAQs