You have seen lean work.
It reduced waste. Improved on-time delivery. It added real dollars to the bottom line. The floor was finally running the way it was supposed to.
Then, a few months later, the gains started eroding. The 5S audits got missed. Priorities shifted. The chaos crept back.
You blamed the tools. Or the team’s discipline. Or the culture.
The real reason lies a layer deeper. And it has nothing to do with what’s happening on the floor.
The Lean Turnaround Was Real. Why Did It Stall?
Many lean programs work initially. They deliver results, tangible results financially, through reduced waste and improved processes, and intangible results in the form of improved morale and an environment becoming conducive to continuous improvement.
Then the pressures arrive.
Excess inventory bought in advance to protect against supply shortages. New product launches pulling the team in multiple directions simultaneously. Demand from the sales team to support a new market segment. Each pressure is legitimate. Together, they overwhelm a leadership system that was never designed to absorb them.
You and your leadership team, who had finally gained traction on the lean implementation, can no longer keep pace with the unplanned turbulence.
Most people diagnose this as a capability problem.
In reality, it is a capacity problem.
You and your leadership team lack the capacity to deal with the turbulences that any business will ultimately face. When those turbulences hit, they disrupt the improvements faster than the floor can absorb them.
The Layer That Nobody Mapped
You mapped every process on the floor. You know the cycle time, takt time, and exactly how to balance the line so demand is met.
But what about the layer above?
The leadership layer has no map. No utilization measurement. No visibility into how much time is actually required to sustain the operation or the improvements the lean initiative produced.
On the floor, when an upstream process produces variable output, the downstream process suffers. It spends its capacity fighting variation it didn’t create.
Leadership is the upstream process that feeds into every process on the floor.
When it has no standard work, no buffer, and no visibility into its own capacity, every wave of organizational pressure hits the floor as inconsistent direction, shifting priorities, and reactive decisions. The floor tools can’t absorb what the leadership system is producing.
The lean program was trying to run a stable improvement process underneath an unstable leadership layer. That’s why it didn’t hold.
What This Looks Like in Practice
This takes me back to the seat manufacturing plant I managed.
We had completed a lean turnaround that took on-time delivery from 36% to 97%, with orders that used to take 24 days to ship now taking 2 days. The floor was performing. The metrics were holding.
Then the demand for new product launches increased. The uncertainty of the 2008 recession had us constantly looking for ways to reduce costs. The priorities kept shifting. On-time delivery started slipping back. The 5S audits were being missed. The system was slowly falling apart.
Our instinct was to blame the process on the floor.
The actual constraint was the leadership system. There was no standard work, no buffer to absorb the unplanned, and no protected time to carry out the projects that mattered.
Once that constraint was made visible, the metrics on the production floor stabilized. The improvements held. In the years that followed, the team, which had been frustrated by constantly changing priorities, was delivering 30 to 40 improvement projects a year. Those improvements survived for over 13 years, through business acquisitions and two changes of ownership.
What the Tools Can’t Fix
If you have been practicing lean, you know each tool is designed for a specific problem. The right tool for the right domain.
None of them were designed for this domain.
VSM maps the production flow. It doesn’t map the leadership system above it. Standard work defines the operator’s process. It doesn’t define the leader’s process. 5S organizes the floor. It doesn’t organize how leadership capacity is allocated. Kanban makes inventory flow visible. It doesn’t make leadership overburden visible.
None of these are failures of the tools. They were designed for a specific domain. The leadership layer is a different domain, one that requires the same principles applied differently.
What Does Fix It
The same principles that stabilized the floor: standard work, buffer, and visibility. Applied to the leadership system above it.
Leader Standard Work creates the baseline. Buffer Capacity Engineering creates the slack you and your leadership team need to absorb the unplanned. The recalibrated 1:1 meeting with your direct reports serves as an early warning mechanism, detecting whether instability is creeping into the system before it becomes a crisis.
When the leadership layer is stable, the floor improvement holds. Not because the tools got better. Because the system above them was finally designed to sustain what they were producing.
When was the last time you mapped the leadership layer above your floor the same way you mapped the floor itself?
If the answer is never… that’s where to look.
The next posts in this series walk through the specific tools that address this constraint. If you want to understand the current state of your leadership system now, the diagnostic conversation is 30 minutes.
