Have you ever seen initiatives start with a big hype, turn into a bureaucratic process improvement rigmarole, and finally be given up (typically slowly and silently)? Lean If so, then you have experienced the culmination of one or more failure modes of Lean implementation. But what is the reason? Is it Lean ideas? Is it the way they are communicated? Perhaps it's the organization's fault for not being "Lean-compatible"? Or are Lean fans simply not loud enough to convince everyone of the wonders of Lean? If you are interested in an often-avoided potential explanation, read on. Lean ideas are great - and insufficient I like Lean. As others with a penchant for making things better, I’ve read and watched a lot about Lean concepts. I’ve also had many opportunities to interpret and apply Lean ideas in logistics administration operations, in R&D, in product and service development, and even in project . management Without a doubt: Lean delivers the goods, when applied pragmatically. Lean is a great set of ideas that has verifiably helped numerous companies to cut cost and create value - unfortunately, in that order of focus, cementing Lean as a cost-cutting management fad in many minds. However, for everyone else without such experience of hands-on success with Lean application there is often confusion, rather than clarity about Lean – despite the fact that Lean ideas have been with us in the West for many (20+) years. It's not about a lack of knowledge As with any complex system regarding human behavior and change, there are many root causes for this confusion, and the resulting stagnating or failing Lean implementations. As an example, these include (but are not limited to) a lack of alignment across hierarchical levels, insufficient discretionary funding for pilot projects, and unrealistic expectations imposed by management and consultants on pilot project teams. Some "Lean priests" bemoan the lack of awareness and knowledge of Lean as the largest root cause; and proclaim: “If only our people would really get how Lean simply makes sense!” Yet, knowledge and good-enough understanding of Lean is a commodity. Lean is being taught in universities and MBA programs, trained in corporate training courses, and preached in numerous articles and case studies. You can read a book (like “Lean Thinking”), or even a business novel (like “The Lean Manager”) or watch a YouTube video and grasp its essence far beyond the unfortunate focus on methods. Lean would have no chance to ever succeed if it required triple PhDs and/or an MBA degree. No, a lack of access to Lean knowledge isn't what is blocking companies from benefiting from Lean. Few people are openly talking about one of the largest root causes: unnecessary and ill-timed hype — especially those with "Lean" as part of their professional identity. Hype reflects a lack of pragmatism regarding change In my experience, one of the largest (if not the largest, by far) root causes delaying or even preventing business success with Lean is the following: Lean is often naively communicated and “sold” as the end-all, be-all answer to all business challenges. The key problem is that the usual approach to "doing Lean" in larger, complex organizations is a romantic attempt to apply lofty ideals on the messy reality of business and its operations. This represents two issues with implications that are quite incompatible with Lean itself: A lack of pragmatism and the willingness to make tough business trade-offs. Implication: Lean is a given solution, we just have to do it by-the-book. A lack of understanding of how people change behaviors, and of what Lean calls "pull". Implication: Lean is the inevitable solution, we just have to yell it louder. Often, the very people tasked with creating value through Lean implementations are the ones who set themselves up for failure simply by talking too much about Lean (even though they might also be doing a lot with it). This can (and often does) lead to unrealistic expectations on all levels of the organization. The resulting push-based implementation attempt turns people off and leads to change fatigue, cynicism, and bureaucratic compliance to Lean. Ultimately, in many organizations, nowadays Lean (and "agility") is just another fad, much like TQM, Six Sigma, BPR, and phase-gate before it; all of them useful ideas that in many cases were transformed into tools of a strengthened bureaucracy, instead of tools for delivering value. Instead, organizations that want to actually get value out of Lean fast, instead of just sharing some internal slides patting themselves on the back, need to lead pragmatic change. How this is to be achieved in practice is an entirely different post (but you can read a bit more about it ). here Lean hype is the reference mode As with many other change and improvement initiatives, Lean hype is the dominant reference mode: i.e. what typically happens in an organization that mismanages Lean implementation. One key reason for this is that Lean is mostly communicated in a polarized manner, and often simultaneously: As a set of very specific hands-on methods, tools and clever ideas with impenetrably mystical and "cool" Japanese names. As a set of lofty ideas and principles to do business by, akin to a philosophy or religion (for some, even to live by). We can debate endlessly about which one is true. Probably both are, and that's OK. And, guess what? (spoilers ahead) Nobody who is asked to apply Lean really cares about Lean-theological arguments. Smashing the feedback loop There is a way out of the "Lean hype" reference mode, which I have experienced to be reliably successful. Yet, it's also what the fewest practitioners/preachers of Lean dare to do: go beyond Lean navel-gazing. Here are some ideas on how you can achieve this: Stop the political correctness of conflating Lean with "the only right way to organize operations". It probably is, but bludgeoning stakeholders doesn’t help. Openly question whether Toyota could have stumbled upon the one, true approach that is supposed to work anywhere and in every business and cultural context. In Aikido-style persuasion: first, admit that some of your Lean pilots are underwhelming, and then invite open criticism from all levels - and listen. Stop using the Lean Manufacturing treatment on every single aspect of your business. No, you are not more productive by standardizing your desktop layout and the location of your stapler. And yes, one-piece flow in R&D is counter-intuitively detrimental. Finally, and most importantly: Tread the middle ground. Take Lean beyond Japanese buzzwords, and also down from the theoretical stratosphere. Bridge the theory-practice gap by looking at how Lean fits your organization, not the other way around. How to achieve this? Deceptively simple, and at the same time tough to do: Apply Lean on its own implementation; i.e., how should you market and sell Lean internally in an organization to enable ? pull-based, gradual adoption Set-based on Lean implementation itself This article is long enough as it is, so I would like to leave you with a final thought for a more hassle-free and business-minded Lean implementation. Within Lean Product Development there is a concept called "set-based development". Simplified, this includes the creation of multiple potential paths to success, the exploration of their trade-offs, the repeated elimination of the weakest paths, and the re-use of insights from all paths examined, good and bad. This gradual evolution relies on also understanding what doesn't work for your specific context, and avoiding expending effort (and later, rework) on it. Lean implementation, as everything involving people, is a tricky endeavor. To get it right somehow, it's more business oriented and prudent to know where not to end up, instead of trying to predict and plan for the right solution, like the old waterfall approach. And that, compared to point-based mandating of what Lean should be for your company, is rather more reminiscent of Lean approaches to getting things done with and for people. More Read on similar business challenges, and follow me and . other articles on LinkedIn on Twitter
