Operational Excellence Is a Leadership Behavior

Operational systems rarely drift randomly. They perform to the standard that leadership allows. This is one of the more uncomfortable truths in industrial operations and one of the most consistently validated by experience.

In the previous article in this series, we examined how WIP inflation quietly erodes margin, working capital, and delivery reliability. The natural question that follows is: who actually governs the conditions that allow WIP to grow? Who permits the system to tolerate a level of congestion that is visibly damaging performance?

The answer is leadership.

Not because leaders are inattentive or misaligned. Most leadership teams in industrial organizations are working hard, engaged, and genuinely focused on improvement. The issue is not intent. The issue is that operational excellence, sustained and structural, is not a function, a department, or a program. It is a leadership behavior. And like all behaviors, it reflects what is consistently modeled, measured, and enforced at the top of the organization.

Systems Reflect Leadership Tolerance

Every operational system has explicit and implicit standards. The explicit standards are documented in procedures, policies, and quality systems. The implicit standards are set by what leadership observes and what it allows to continue.

If priority overload is tolerated (i.e. sales can override the production schedule whenever a customer calls) congestion becomes structural. The floor learns that the schedule is a suggestion, not a commitment, and operators adapt accordingly.

If heroics are rewarded and the people who stay late to expedite a crisis shipment are celebrated more than the people who prevent the crisis from occurring, variability increases. The organization develops an addiction to firefighting because firefighting is how recognition works.

Silos harden if cross-functional misalignment persists:  if planning, operations, and sales are each optimizing for different metrics without a shared view of system performance. Coordination becomes difficult. The cost of misalignment accumulates quietly.

Continuous improvement teams can surface these patterns. They can document the problems, run the Kaizen events, and train the workforce on lean tools. But they cannot change the behaviors that created those patterns. Only leadership can do that.

What Floor Signals Actually Reveal

Walk any factory where leadership engagement with operational discipline is weak, and the same signals appear.

Operators are improvising priorities and deciding for themselves which order to work on next because no authoritative guidance exists. Supervisors are escalating exceptions constantly, spending their shift managing interruptions rather than supporting normal flow. Schedules are rewritten daily because the planning process has no credibility with the people who execute it.

These behaviors are not signs that the workforce is undisciplined. They are signs that the system is not well governed. Operators improvise because they have learned that the official priority list will not be honored. Supervisors escalate because there is no reliable mechanism for resolving conflicts before they escalate. Schedules lose credibility because they have been overridden too many times for anyone to take them seriously.

The root cause in each case is a governance vacuum. Governance vacuums are filled by whoever is willing and able to fill them. Usually, that means individual contributors making judgment calls that should be made at the system level.

What Operational Excellence Leadership Behavior Actually Looks Like

In high-performing industrial organizations, leadership engages with operational performance differently than in organizations that struggle.

The difference is not primarily in the sophistication of tools used or the maturity of the continuous improvement program. It is in what questions leadership asks, what behaviors they model, and what they consistently refuse to tolerate.

High-performing operational leaders focus on flow stability – not just on output metrics. They want to know whether work is advancing predictably through the system, not just whether the quarter’s shipment numbers were met.

They protect constraints deliberately. When they understand that a specific resource limits throughput across the entire system, they make decisions that protect that resource – even when it means saying no to orders, engineering changes, or schedule modifications that would overload it.

They align commitments to capacity. They do not allow the organization to make delivery promises the system cannot keep. They understand that overpromising creates expediting, and expediting creates chaos, and chaos is far more expensive than the discipline of commitment alignment.

And critically, they do not ask: “Did we run the Kaizen?” They ask: “Did the system behave differently this week?”

This distinction matters. 

The first question focuses on activity:  on whether the improvement program is running as designed. 

The second question focuses on outcomes: on whether the system is actually performing differently as a result of that activity. 

Leaders who ask the first question may have active programs and stagnant performance. Leaders who ask the second question rarely tolerate the gap between the two for long.

The Governance Conversation Most Organizations Never Have

Most industrial organizations have regular leadership meetings that cover financial performance, customer issues, safety metrics, and maybe a high-level operational scorecard. Fewer have structured conversations about how the operational system is governed.

The governance questions,

• “How much WIP should be in the system?”
• “What happens when a sales commitment exceeds current capacity?”
• “Who decides when to expedite and when to hold the sequence?”
• “What are the rules for releasing new work to the floor?”

… are often left to functional managers to navigate individually, without explicit guidance from leadership.

This is not an oversight. It reflects the reality that most leadership teams were not taught to think about operations as a system with governing principles. They were taught to manage functions and review results.

The shift in operational excellence leadership behavior requires a different orientation: treating the operating system itself as a leadership responsibility, not just the outcomes the system produces.

This is often more challenging than adopting a new improvement framework. It requires leaders to engage with operational detail they may be accustomed to delegating. It requires them to be consistent – because inconsistency is the fastest way to undermine any operational standard. And it requires them to measure themselves against system outcomes, not just program activity.

The Leadership Diagnostic

The most useful diagnostic question for this aspect of execution physics is direct:

What operational behaviors does your leadership team consistently tolerate that degrade flow?

Almost every organization has some answer to this question because every leadership team has blind spots about the implicit signals it sends. The order that always gets expedited regardless of the schedule. The customer that can always override production priorities. The functional leader who is never held accountable for releasing work that floods the system.

Identifying those behaviors, and being honest about what they signal to the rest of the organization, is the beginning of genuine operational excellence leadership behavior.

The next article in this series examines why many lean transformations plateau after early gains, and why sustainable performance improvement requires changing the operating system and not simply deploying better tools.

—

Diagnostic question for this week: What operational behaviors does your leadership team consistently tolerate that degrade flow? What does that tolerance signal to the organization?

Want to talk about your challenges?

Let’s connect.

Miss the rest of the series? Be sure to read:

• Article 1: Operational Excellence Programs Are Not Enough. It’s Execution Physics That Determines EBITDA
• Article 2: Execution Physics: How Excessive Work In Process Management Quietly Destroys Margins
• Article 3: Operational Excellence Is a Leadership Behavior < You’re here!
• Article 4: Why Lean Transformations Plateau

FAQs About Operational Excellence Leadership Behavior