The Lean & Agile Practitioner
Lean: not just a hype word for efficiency
Yah sure, we do “lean” here and we operate a tight ship with just a few of us doing everything – you know, everyone is multi-taskin’.
“Lean” is such a convenient term, everyone uses it in their own definition. People frequently use “lean” in place of “efficiency”, probably because it sounds more cool. Another round of cost cutting? Sure, let’s tell everyone we’re “going lean”, again!
Lean is a proven, powerful productivity approach (we probably owe post-WWII modernity and the internet age to Lean!), yet most people don’t know what Lean is really about beyond the hype. And in this age of hyper-competition, not knowing nor using tools that are proven to work, is a big disadvantage.
So, people should learn and practice Lean. But there’s one complexity: today’s Lean is a mix up between two different but same sounding management concepts – Lean Manufacturing and Lean Startup. Lean Startup is a recent decade thing – it was inspired by and hence not disassociated with Lean Manufacturing, but it serves a somewhat different purpose and audience. Lean Manufacturing traces its routes to Japan’s post WWII industrial recovery with the aid of some key American industrial engineers.
Post WWII, Toyota shop floor engineer Taiichi Ohno rose through the ranks with the backing of Eiji Toyoda from the founding family, to install what became TPS (Toyota Production System), which in turn later became generally known as Lean Manufacturing.
Meanwhile, two industrial engineering mavericks were flown into Japan at the request of the Union of Japanese Scientists and Engineers: W. Edwards Deming and Joseph Juran. In the US, both of their work on quality management only came to mainstream attention in the late ‘80s when the concept of Lean Manufacturing started to emerge. But in Japan, Deming’s and Juran’s teachings, overlapping but somewhat different in approach (Deming more a statistical approach, while Juran more focused on management), were immediately embraced since they first set foot on Japanese soil circa 1950.
Taiichi Ohno was for sure the driver behind TPS, but it was not just him. It was the engineers at the Gemba (where things are happening, e.g. the factory floor) that voraciously absorbed and applied the many new teachings and discoveries happening within and brought into Japan, that made the radical shift from pre-war Mass Production to post-war Lean Manufacturing happen. The bottom-up culture of Lean was present from the onset.
Definition & Key Elements
Wikipedia’s summary of Lean Manufacturing is spot on so here’s the share:
“Lean Manufacturing is a systematic method for waste minimization (“Muda”) within a manufacturing system without sacrificing productivity. Lean also takes into account waste created through overburden (“Muri”) and waste created through unevenness in workloads (“Mura”). Working from the perspective of the client who consumes a product or service, “value” is any action or process that a customer would be willing to pay for.”
While practices such as JIT (just-in-time inventory management) is specific to the manufacturing industry, many of the Lean Manufacturing concepts are applied and relevant to all other industries:
Literally meaning “board” in Japanese, Kanban introduced the practice of making a team’s progress of work openly visible to others on the floor. Kanban was adopted as a core concept in the later Lean Startup and Agile. And for good reason: you can see productivity increase apparent just having a Kanban board practice running, even before Scrum and Sprint routines are in place. The simple notion of persistent, visualized sharing of information; it’s that powerful.
Muda, Muri, Mura (むだ、むり、むら)
Muda means waste, Muri means overburden and Mura means unevenness. Cutting out Muda is at the core of Lean, i.e. take out the fat (but some fat is good, i.e. slack – more on this later). Making things that won’t immediately sell, let alone sell anytime is an obvious Muda, but unnecessary processes, waiting time, idle inventory and even producing to over quality are all examples of Muda. So in Lean, just making a good product is not good enough. It needs to be produced in a way that is not wasteful.
The second Muri is more focused on process. This is where the concept of “slack” comes in – counterintuitively, slack is good in Lean. When we think of slack, we think it is waste. So when we think of “optimizing” processes, our intuition is to cut out slack and try to make processes close to each other as much as possible. This is the number one cause of Muri, which results in bottlenecks. Processes need to be elastic, and slack is that elasticity. Hence, process optimization is all about how much slack to build in and adjust dynamically (of course, too much slack is Muda). On this topic, Eliyahu Goldratt’s “Goal” is an awesome read (actually, a must read).
Finally on Mura, this is where Lean meets TQM (and all other stochastic processes of quality management including Six Sigma). Mura and Total Quality Management is not just about minimizing product defects, but also eliminating unevenness in processes (e.g. speed and volume). “Heijunka” (平準化), meaning leveling of production, therefore, is a combined concept between elimination of Muri and Mura.
When an accident or failure happens, the first thing to do is to go to the Genchi, the actual place it happened, and look at the Genbutsu, the actual thing that broke or failed. As simple as that, in large organizations, even in Japan, head quarter managers still get caught in paralysis and fail to get their priorities right.
Gemba has the same meaning as Genchi, i.e. the local place where things are happening. In Lean Manufacturing language, Gemba is used to teach the importance of respecting the line managers and floor workers – they are the most intimate with the manufacturing process and most likely to be able to come up with continuous improvement ideas – which some of them can leap frog to innovation.
The character for Kai means “modification”, Zen in this case means for “better”. There’s a subtle difference to Kairyo (改良) which Ryo still means “better”. Kaizen has a connotation of smaller incremental improvement and more on behavioral improvements (i.e. better ways of doing things), while Kairyo hints functional improvements (i.e. on the product or manufacturing equipment). Kaizen is an encouragement for small improvements on a daily basis, hence synonymous to continuous improvement.
Think Sony Walkman. Kakushin means revolutionarily new, the punchy word for innovation in Japanese. (On a side note, Kakushin is an elusive slogan in Japanese organizations; conformity culture make workers great at Kaizen but leaves almost no space for the Einstein with the crazy idea to survive in a Japanese organization. The only reason why Sony’s Walkman made it to the market, and the Honda Jet is flying today after decades of investment, is because the sponsors were the founders of the companies.)
Most famously known by Eric Ries’ 2011 book of the same title, Lean Startup originated after Steve Blank, back in 2004 taught Ries (Blank was a lecturer at UC Berkley), and invested in his start-up. Ries promptly burned Blank’s money and from that learning, Lean Startup was born. (Blank is also the author of the 2005 book Four Steps to the Epiphany which not surprisingly is the genesis of Ries’ later Lean Startup.)
Difference between Lean Manufacturing and Lean Startup
Lean Manufacturing and Lean Startup are actually apples and oranges. They have fundamentally different objectives, solution applications, users and modalities:
In short, Lean Manufacturing is about “how to build better”, and Lean Startup is about “what to build”; the former more catered to established enterprises running mass production, and the latter for entrepreneurial businesses developing new products in untested markets.
Definition & Key Elements
Ries defines “A startup is an organization designed to create new products and services under conditions of extreme uncertainty.” Ries developed Lean Startup out of desperate needs: the timing that Ries was running his startups was post dot-com crash and access to capital was tight, yet the internet thing was here to stay and the opportunity set was apparent. How to find product market fit fast and cheap was a matter of survival.
Lean Startup is a modern update of the age old adage of “trial and error”. The refinement lies in the concept of Minimum Viable Product, or MVP. In a traditional product development cycle (i.e. waterfall), product release is a final state and goal, so “oops, let me try it again” doesn’t exist. If the product doesn’t fly, either it gets abandoned, or a new product development cycle takes place – it’s time consuming and expensive to fail in waterfall. Lean Startup is revolutionary because it makes failure cheap, fast, and most importantly, welcome.
- Value Hypothesis: Will this product deliver real value to the user?
- Growth Hypothesis: How will new customers discover this product?
Ries stresses that “”Learning” is the essential unit of progress for startups.” At first, there are assumptions. “I have a great product idea” is a hypothesis and it needs to be tested. The most direct way to test a hypothesis is to run an experiment. A really simple version of the product that represents the hypothesis will be needed for that experiment, hence build a Minimum Viable Product.
With the MVP, tests are conducted and the results and other findings are measured. From the measurements, you want to learn if the hypothesis was valid, somewhat valid, or invalid – Ries labels this “validated learning”. This whole cycle from hypothesizing all the way to validated learning is called “Build-Measure-Learn” in Lean Startup.
Validated learning from the experiment should not just answer “Should this product be built?” but also “Can we build a sustainable business around this set of products and services?” Ries therefore suggests to test the hypothesis “I’ve got a great product idea” on two fronts:
Tweak, Persevere or Pivot
It would be highly unlikely that the “great product idea” will pass both the Value Hypothesis and Growth Hypothesis on the first MVP attempt. Hence, Build-Measure-Learn iteration follows. Tweak and try again, persevere and try again, and if it still doesn’t work, have the courage to pull the plug and meanwhile if a better idea comes up, pivot.
Again, the importance is not to just prove the value of your product, but also to find a way to build a business around it. Seemingly outside-of-the-product items like product packaging, labeling, user instructions and community support are important product attributes as well, and these are things that also need to be experimented and validated. (I’ve written more about this in a previous article: “Great product, not selling”.)
Lean – the Mix
Lean, as in the singular term, is a synthesis among the two streams of Lean Manufacturing and Lean Startup and anything in between, so there’s no official definition of Lean (nor can anyone claim it). Even Wikipedia does not have a dedicated description for Lean – the page is simply a list of the various branches of Lean.
Though from observation, I think people generally associate Lean with the following three core ideals:
- Reduction of waste: Focus on value creating activity and elimination of anything that doesn’t contribute to value
- Iteration: Build-measure-learn and continuous improvement
- Localized activity: Genchi, Gemba and allowing product strategy to be determined thorough local experimentation
For the Lean professional who has learned and internalized the major tools and processes of both Lean Manufacturing and Lean Startup, it really doesn’t matter which stream of Lean they are applying to the project right in front of them. Lean Manufacturing is not exclusive to large factories – startups who are at scaling stage going into model year production will be using Lean Manufacturing. And likewise, there’s no reason why a product development unit with a large manufacturer shouldn’t be using Lean Startup. The key is contents, not labels. Even between Lean and Agile, the boundaries are blurred. Just use what works to your advantage.
The “L” in Lean is for Learning
For myself, the most important keyword that I associate with Lean is “learning”. Every activity in Lean, whether it is from Lean Manufacturing or Lean Startup, demands inquiry and learning, and that is precisely what learning organizations is about. The same can be said for Lean’s doppelganger Agile, and that is the reason why I am a big advocate of Lean & Agile.
You might also enjoy these other writings from Takeshi: