Is Lean Scientific?
Dear Gemba Coach,
I often hear that lean is like the scientific method. As a lean consultant, I facilitate kaizen events, and find it hard to see the parallels. Could you clarify what people mean when they say this, and how it applies to our work?
Thank you for this very fundamental question. It is clear that the founders of lean thought they were applying the scientific method (in the form of Deming's PDCA cycle) to business problems. As Art Smalley and Durward Sobek point out in Understanding A3 Thinking, their great book on A3s, on page three of the first leaflet ever produced by Toyota on TPS, it says: "TPS is founded upon a scientific mindset. It is important to start with those phenomena and search for the true cause by tracing things to their origin. In other words, we place heavy importance upon getting the facts." Indeed, many misguided Gemba implementations can be linked to a failure to realize kaizen in the spirit of the scientific method. Still, the term "scientific method" is often vague and open to interpretation (for instance, Taylorism is also known as "scientific management," which is both true and untrue, but confusing). So, what are we talking about?
There are many aspects of the scientific method, but I would summarize (and over-simplify) it as follows:
- Observation: The first step of any scientific investigation is observing a phenomena in reality (as opposed to philosophy, which is essentially about mental arguments), which is to say in context.
- Formulating a theory: Putting down on paper a clear cause-effect link that explains whatever you are observing. This is never easy because many phenomena seem complex. There are many causes and effects happening at once, so there is an art to reducing it to a simplified "this happens because of this …" Unless this phenomenon is well known previously, a theory is often nothing more than an educated guess on why things work out this way.
- Look for anomalies: This is where scientific thinking goes against common sense. Finding cases where our pet theories are shown to be correct is the easy part. True scientific thinking, however, is about finding conditions in which the theory doesn't work. Anomalies flag areas we can learn from, because they reveal where our model of reality is not good enough to explain what really happens.
- Defining the problem: Expressing specifically how anomalies diverge from the stated theory is the real lynchpin of scientific thinking - this is where learning starts.
- Formulating hypotheses: Once the problem has been clearly stated, several hypotheses can be explored to explain this problem. The idea at this stage is not to find a quick answer, one which makes the problem go away, but to find the right answer, which reconciles (or not) the anomaly with our general theory.
- Experimenting to test hypotheses: Repetitive testing of the various hypotheses in live conditions is what leads to solving the problem.
- Reformulating the general theory to incorporate the newly validated hypothesis, which is, by and large how our learning grows.
- Sharing this knowledge, not just by explaining the results, but by allowing others to replicate the experiment in different conditions in order to replicate the learning and further the understanding of the new theory.
This sounds terribly cumbersome (and is), but since the late eighteenth century, this process, and the interaction between scientists and engineers has been the main source of industrial productivity. And this is the approach that Toyota production engineers adopted when they heard it from Professor Deming. In lean terms, this is how it is applied:
- Go and see: Genchi genbutsu is the foundational practice of lean management - going to see the facts for yourself at the source. When problem solving fails, more often than not, this is a failure of "go and see." We have not spent enough time at the real place watching the process unfold to figure out what is really going on. Just recently, I was discussing with a problem-solving team how to solve a complex quality problem, and as we discussed the problem in the production cell, we saw the operators being interrupted almost every five parts by something or other. A third of these interruptions occurred at the workstation where the quality problem occurred. We had been trying to figure out where the machine cycle went wrong, but then we focused on looking at how the operator started working again after just being interrupted in her cycle. Just by observing in this way, we could see several quality risks happening as she picked up the work and finished the cycle - none of which had anything to do with the machine's process.
- Write the standard: Writing a standard in lean terminology is the equivalent to formulating a theory. Writing the standard means putting down on paper the theoretical sequence of operations necessary to do the work right. This is not so easy. In many cases, we have to look for the original documentation, and we immediately see that many parameters have drifted from what was specified in start-up conditions. The first step here to solve the problem is to bring the process back to initial conditions (fit to the theory) and see what happens.
- Look for variation: Any variation from standard is an anomaly in the process. Once the standard is clear, rather than tell ourselves that "normally" the process is this or that, we focus on every variation that we spot, anomalies in scientific terms, and try to understand them.
- Defining the problem: A problem, in lean, is a gap with a standard. This gap is expressed in two ways: first, as a performance gap with a standard (such as the best day, or the best plant) and second as a variation from the standard process (what we need to do for the work to be right). In practice, there are often all kinds of variation, and the skill in defining the problem often lies in identifying which variation has the greatest impact on the performance gap. This is not done by thinking hard, but by testing every factor of variation until we're quite sure which of them has the biggest impact.
- Seeking the root cause: Once we've figured out (through trials) the most important source of variation, we must determine the root cause of this variation. This is where the '5 why?' method is so powerful. It enables us to move away from superficial explanations and delve deeper in our understanding of the process.
- kaizen: kaizen is often nothing more than "try it!" The purpose for kaizen is to try various things to figure out the real cause of the problem - and so be able to fix it once and for all. Although the scientific process is cumbersome, the experimentation par of it needs to be quick, plentiful, and tireless. In his attempts to create a light bulb, Edison is supposed to have quipped: "I have not failed. I've just found 1,000 ways that won't work."
- Reformulate the standard: Once the problem has been solved, because the root cause has been identified and the proper countermeasure implemented, the new standard is formulated and put in place. As with scientific experimentation, a new standard often also means changing the organization around the activity.
- Yokoten: In this, lean practice is remarkably similar to the scientific method. Rather than spreading the "best practice," Yokoten is more about replicating the study in other processes rather than applying the solution. One need not start from scratch, but by reproducing the same experiment (kaizen) in different conditions, one is likely to end up with different applications – and hence better local learning.
One of the more frustrating aspects of working with old style sensei is that they never seem to be interested in the solution - the improvement actions. All their questions are about understanding the problem. At first, I thought that this was a kind of trick to impress the troops. But as time went by I came to accept that they were genuinely not interested in any solution per se: they trusted people to come up with what they thought was best. They really were interested in understanding the root cause better, in learning by deepening the collective understanding of the situation.
Shades of Gray
Realizing how much lean draws from the scientific method has profound Gemba implications. Lean practice is mostly about finding and addressing gaps between our current processes and our ideal ones; and not about spreading solutions. One typical example is stock. Management wants to reduce inventory. Lean thinkers want to reduce lead-time. Reducing inventory can be achieved by decree (with sometimes dire results in terms of on-time delivery). Reducing lead-time can't be forced: the causes of lead-time (large batches, planning issues, complex flows, poor logistics, etc.) must be understood and tackled one by one on specifics. If this misunderstanding is not cleared up, many people look for answers that aren't there. Lean "solutions" tend to be no more than generic ways of solving generic problems (use a small train to deliver parts to the line), but specific solutions (here are the wagons you should use) are rarely workable in real life circumstances. Trying to apply literally solutions from other sites or companies often leads to bitter disappointments (as well as unnecessary expenditures).
Lean answers are seldom black and white. When people catch religion from reading the lean literature, they try to apply across the board lean "practices." Because it follows the scientific method, by their very nature lean countermeasures (no one ever believes in full blown "solutions") tend to be context dependent and, essentially, shades of gray. For instance, in the case of bought-out-parts inventory, people who've convinced themselves of the superiority of "flat storage" often want to pull all the racks down. It's sometimes hard to convince them that pulling racks down to store components in supermarket-like shelves is a great idea, but some parts do have long lead-times if they come halfway across the globe, and some other parts are dead stock but not chalked up for destruction yet and so on. So a few racks are necessary, and these racks will probably be managed with a traditional computer ordained address system, contrasting with the supermarket-type handling of the flat storage. It's true that the full gain will only appear when all forklifts can be pulled out of the hall, but this requires solving the problem of long lead-time parts and slow moving parts. Different principles apply in different conditions.
There are three broad practical consequences from trying to apply lean in the spirit of the scientific method. First, we need to spell out our theories about how things work continuously, whether as standards or causal relationships. We must see the cause-and-effect relationships within processes. As the first TPS leaflet states: "in problem solving, the purpose must be made clear ... in kaizen the needs must be made clear." This is not always obvious, but it's a worthwhile exercise, and key to progress over time. Secondly, we need to increase the rhythm of kaizen activities and events. If learning is about failing, we must fail more, and quicker. People must learn how to try things out right away in a safe manner – with cardboard cutouts, duct tape, whatever. Quick experiments yield far much more knowledge than hours of discussion. Finally, we must abandon our belief in cookie-cutter solutions and accept that if we want another group of people to apply a specific improvement it's both safer and quicker to get them to replicate the analysis and kaizen process rather than to impose our specific solution for implementation. All knowledge is contextual, and no conditions are ever exactly the same.
kaizen, kaizen, kaizen. I can't stress enough the need to maintain a high rhythm of kaizen activity. The industrial revolution became a revolution (as opposed to slow evolution since the thirteenth century) when the rate of theory formulation and experimentation skyrocketed. The same is true of lean progress within one company. Lean transformation becomes a transformation (as opposed to business as usual with a little continuous improvement thrown in) when the rate of kaizen and problem solving explodes. At the very least, every supervisor conducts a kaizen event a month, and every middle-manager works on one A3 always. Lean is work! To quote Edison again: "Opportunity is missed by most people because it is dressed in overalls and looks like work." So is improvement.
Lean Lessons from Cobra Kai(zen) and the Karate Kid
The unexpected wake-up call of the modest perfection of the original Karate Kid movie was that we need to move beyond defending this or that method of work and look to highlight opportunities of improving things beyond monetization, says Michael Balle in this reflection on the meaning of this classic movie.
How Using Kanban Builds Trust
Kanban functions as a trust machine because everyone using it must understand what they have to do and why, says Michael Balle: "Our purpose here is to share our ideas on what we believe is important in lean thinking."
The Sanity of Just-in-Time
Path dependence is the worst enemy of smart resolution, argue the authors, who suggest greater "frame control" with enabling tools such as just-in-time to respect people on the frontline and respect the facts they share about what is happening to them. "Mastering the path as opposed to being led by it, means looking up frequently to reevaluate both destination and way as new information comes to light."