Why your lean programme quietly died, and how to bring it back to life

When I walk into a plant whose lean programme has fizzled out, I almost always see the same thing. The hall is clean, but the shadow boards have gaps. The shopfloor board shows KPIs nobody discusses any more. The action list has items whose owners no longer work for the company. And in the office next door, order processing runs the way it did before the programme: by email, Excel and shouting across the room.

The striking thing: nobody consciously ended lean. There was no decision, no meeting, no announcement. It simply went quiet. One meeting was cancelled, then a second. An audit was postponed. The lean manager was given an additional project. Plant management had a quality problem with a customer and no headspace for boards.

A plant with several assembly lines that I supported had started an extensive programme with consultant backing three years earlier. When I arrived, half of the shift leaders no longer knew which standards actually applied. The other half had built their own. Neither was ill-intentioned. It was the logical consequence of nobody following up any more.

In my experience there is no single mistake, but an interplay. Four reasons come up almost every time.

• Lean was a project, not a leadership task. It had a start date, a budget and an end date. After the end date, it was only logical that it stopped.
• Too many building sites at once. Value stream, kanban, changeover workshops, workplace organisation, boards and a new KPI system, all in parallel. None of them was properly finished, none of them became second nature.
• The programme lived in production and ended at the factory gate. Order clarification, purchasing and production planning were left out. The line got faster, but the order still reached it too late.
• The knowledge hung on one or two people. When the lean manager left, the programme left with them.

In group-owned plants a fifth reason often comes on top: the programme came from head office and was completed as a box-ticking exercise. Audit passed, tick set, back to daily business. In mid-sized companies it tends to be the reverse: plant management genuinely wanted it, but had no staff function and had to carry lean on top of everything else.

The obvious reaction is to launch the whole thing again. New consultants, new training wave, new name. In my view that is the surest way to live through the same story a second time. The workforce still has the first attempt in mind. A second big launch only confirms the suspicion that this will be another wave you can sit out.

What I recommend instead is unspectacular: no campaign, but an honest stocktake. What is still running? What is dead? What annoyed the people on the line back then, what did they value? Who got involved back then and is frustrated today? These conversations are uncomfortable and that is exactly why they are valuable.

The restart begins with plant management standing at the board themselves, not the consultant. That is not a formality. It is the difference between a project and a leadership task.

My approach to the restart has three steps. It sounds simple, and that is deliberate.

• Diagnosis. I measure the maturity level, separately for shopfloor and office, and talk to shift leaders, clerical staff and management. The result is not an expert report but one page: where do we stand, where is the biggest lever.
• Cut dead weight. Everything left over from the old programme that no longer adds value goes on a cut list. Reports, committees, KPIs, methods. Cutting is the first visible act of the restart, and it creates breathing room.
• Roadmap. Two to three value drivers that actually move lead time, quality or delivery performance. With owners, with a rhythm for follow-up, with a first quick win that can be seen in the hall.

The decisive difference from the first attempt is focus. Not ten methods, but the one that sits at the bottleneck. Not every area, but the pilot area with the most visible problem. And: the value stream is looked at from customer order to delivery, not just from goods receipt to dispatch.

Lean only holds if leadership lives it daily. That sounds like a line from a textbook, but the practice is concrete. Plant management goes to the line regularly, asks questions and listens instead of giving instructions. Deviations are discussed at the board, not in the Friday meeting. Whoever takes on an action is asked how it is going, and that every single time.

The same applies in the office. If the head of administration does not look at their own in-trays, waiting times and handovers, lean office remains a buzzword. Regular communication has to be in place before the first method is introduced.

And leadership has to learn to say no. To new projects, to additional KPIs, to requests from head office that have nothing to do with the bottleneck. I have led laterally, without line authority. I know how hard the no is, and I know that it is the point at which it is decided whether it holds this time.

The last building block is the one most often forgotten. A lean programme that hangs on one person is a bet on that person staying. That is why, in a restart, I build up internal lean champions from the very beginning: shift leaders, team leaders from the office, people from production planning. They facilitate the boards, they run the small improvement rounds, they keep the standards alive.

The goal is to make myself redundant. If I leave after the mandate and the plant falls back, it was not a restart, just another attempt. The measure of success is not the closing document, but the board that is still in use a year from now.