Research shows that many Lean initiatives fail to achieve a lasting effect, and the cause rarely lies in the methods. It lies in the way the introduction is approached. This article reviews the factors the literature points to as decisive.
Change with an end date rarely holds
One of the most frequent mistakes is to treat Lean as a project with a start date and an end date. Workshops are held, future value streams are drawn, and the organisation is then expected to drive the work on by itself. Repenning and Sterman's work at MIT points to that very approach as one that rarely creates a change that stays.
The three factors the research highlights
Looking at the efforts that actually hold, three factors recur in the literature:
1. Management behaviour before tools
- •Managers who use the boards themselves every day rather than looking in now and then.
- •A visible prioritisation of the improvement work in management's own calendar.
- •Consistent follow-up on deviations.
- •Mistakes treated as something worth learning from rather than as blame.
2. Meeting structures that create a rhythm
- •Daily management with agreed routes onward when a problem cannot be solved at the level.
- •Weekly improvement meetings with a fixed agenda.
- •A monthly review of how the key figures are developing, with the leadership team.
- •A quarterly adjustment of which improvements are to be prioritised.
3. Capability building in the organisation
- •Internal improvement leaders trained to drive the work themselves.
- •Managers close to operations with practical Lean experience.
- •Written standards that can be handed on to the next person.
- •Ongoing support until the behaviour can carry itself.
How the gap between plan and practice opens
The sequence is a familiar one. A company decides to introduce daily management with boards, puts the boards up, trains the team leaders and gets energetically through the first weeks. Then an urgent situation arises, the meetings are skipped, and by the time they are taken up again the figures on the board are too old to be of use. The team leaders lose their faith in the system, and the pattern is well documented in the Lean literature.
This is precisely why we at Prozanta work in phases — map, build, execute, anchor, and stay in operations until the improvement runs without us. A practical entry point to the governance part can be found in our guide to Daily Management.
✓The most important takeaways
- →Measure the anchoring and not merely the introduction. The question is whether the behaviour holds six months later.
- →Build the meeting structure before choosing tools. The rhythm of the daily discipline matters more than the choice of Lean method.
- →Expect resistance, and agree in advance what you do when everyday pressure squeezes the improvement work.
- →Invest in internal improvement leaders. External experience is to be handed over, not rented indefinitely.
Sources and further reading
- Repenning, N. P. & Sterman, J. D. (2001). Nobody Ever Gets Credit for Fixing Problems That Never Happened. California Management Review, 43(4).
- Womack, J. P. & Jones, D. T. (1996). Lean Thinking. Simon & Schuster.
- Lean Enterprise Institute — lean.org, knowledge centre for Lean thinking.
The references show the professional basis. Sources are reproduced in their original language.