Tag Archives: Lean

Some Thoughts on the Toyota Production System


The Toyota production system (TPS) was not designed.

The technique we call the Toyota production system was born through our various efforts to catch up with the automotive industries of western advanced nations…
— Taiichi Ohno, Foreword to Toyota Production System[1]

It grew out of “various efforts.” Often these efforts were “trial and error.” Experiments were run, lots of them. Some yielded desirable results, others did not. But lessons could be learned from every experiment—What worked? What didn’t? Why?

What made an outcome of an experiment desirable? What was the purpose of these efforts?

Above all, one of our most important purposes was increased productivity and reduced costs.

So how was productivity increased and costs reduced? Toyota guessed (or hypothesized) this could be done by “eliminating all kinds of unnecessary functions in the factories,” what we’ve come to term as waste. We all recognize there are many ways to produce the same result. However, some are less wasteful than others. They are efficient.

By attending to what is actually happening, by observing the real process, a worker could identify waste in various forms. Observation comes before understanding.

Our approach has been to investigate one by one the causes of various “unnecessaries” in manufacturing operations…

One by one!

If we take a minute to think about how many different operations—small and large, localized and cross-functional—take place in factories, we start to understand the scale of Toyota’s effort. That takes patience, discipline and perseverance i.e. grit. The image of a bee hive or a migrating wildebeest herd or a flock of starlings comes to my mind. There is no centralized design or control, nevertheless all members work with the same purpose.

…and to devise methods for their solution…

To eliminate the causes of different types of waste, i.e. the unnecessary functions in the factories, Toyota devised solutions such as kanban, just-in-time, production smoothing, and autonomation. These methods are outcomes of a way of thinking and being. Experimentation through trial and error. They are the means Toyota developed to achieve its purpose of increasing productivity and reducing costs. They could be spread within Toyota, but can they be used elsewhere? Many examples exist of attempts to incorporate them in companies here in the West. I’ve had a front row seat to many of them. Few, if any, show the type of sustained benefits seen by Toyota. Why is that? Context!

Although we have a slight doubt whether our Just-in-time system could be applied to the foreign countries where business climates, industrial relations, and many other social systems are different from ours, we firmly believe there is no significant difference among the final purposes of the firms and the people working in them.

All companies operate within an environment: business climates (e.g. the regulatory environment), industrial relations (i.e. how companies relate to their peers and their suppliers, their communities, and the natural environment), and social systems (such as local traditions and customs). These will necessarily affect the type and form of tools that emerge from experiments that (should) happen in support of a particular company’s purpose. By the way, contrary to Ohno’s point, and as irrational as it seems, not all companies have the same final purpose as Toyota—to increase productivity and reduce costs. Similarly, people in the West have different objectives, different worldviews, than those in the East.

The Toyota production system, and perhaps even lean, is a way of being in pursuit of certain purpose(s). They are not a set of tools to copy and deploy independent of and indifferent to the context where they are deployed. It shouldn’t surprise anyone that efforts to unthinkingly copy and apply them fail more often than succeed.

[1] Monden, Yasuhiro. Toyota Production System. Norcross, GA: Industrial Engineering and Management Press. 1983. Print. ISBN 0-89806-034-6

The Context for Concepts

In my last post I might have left the impression that conceptualizing the real place is bad or that we should avoid it. This is not a correct impression.

We cannot avoid conceptualizing the real place. It’s automatic; part of our biological structure and the structure of our language. Concepts are how we make sense of the real place. They provide insights into the real place. We need those insights to respond appropriately to the real place. But we shouldn’t lose sight of the fact that concepts are the mind’s representations of the real place and not the real place itself! We can call them images, idols, models, data, or symbols.

D. T. Suzuki[1] shared, “To point at the moon a finger is needed, but woe to those who take the finger for the moon…” Alfred Korzybski[2] wrote in Science and Sanity, “A map is not the territory it represents, but, if correct, it has a similar structure to the territory, which accounts for its usefulness.” George E. P. Box[3], in Statistics for Experimenters, put it pithily that “all models are wrong; some models are useful.” These reminders, to be consciously aware of the difference between the real place and our mind’s abstractions of it, is the thread that runs through science and religion.

Problems only arise when we hold onto a concept long after it has stopped representing the real place and a gap has developed between what is and what we conceptualize it to be. To know what is, we must first “go and see” the real place. Without that direct experience with the real place, we cannot hope to act in ways appropriate to it. This is my understanding of what Zen and lean teach.

[1] D.T. Suzuki
[2] Alfred Korzybski
[3] George E.P. Box

The Real Place

My study of Buddhist thought, and especially Zen, have so far taught me that I am often unaware of the real place. Decades of schooling and acculturation to society have taught me to ignore the real place in favor of concepts manufactured by the human mind; to create and be hypnotized by images and models. Right, wrong, god, devil, me, you, husband, wife, mother, father, boss, servant, friend, enemy, success, failure, good, bad, us, and them are all concepts. These are all creations of the mind. It gives them meaning. They’re not real.

Concepts are static–unchanging and easy to grab a hold of and cling to, while the real place is dynamic–ever changing; sometimes in predictable ways, most times in unpredictable ways. The real place offers nothing to grab on to; nothing to cling to. It is inevitable then that the two will eventually diverge from one another. I believe that that gap between what I see and what I think I see is the source of much, if not all, my suffering–frustration, anxiety, feelings of helplessness, exhaustion, and such. To experience the real place, I must let go of concepts, or rather I should not cling to them. Only then will my actions be appropriate or right for the real place.

Zen has been useful in ferrying me back to the real place every time my mind drifts to concepts.

My most direct experience of this gap, or at least one that I am most aware of, has been in the workplace. Data, charts, procedures, policies, concepts abound. Again, most, if not all, are disconnected from the real processes and systems. How work actually happens. However, like me, organizations remain mostly unaware of the disconnect. They thus suffer in a mire of internal conflict and frustration, too.

Lean can be useful to get organizations back to the real place.

A Very Cool History of the Toyota Production System

The Toyota Production System was born out of necessity. These two videos show its evolution.