Jan 30 2014
The Limits of Imitating Toyota | Bill Waddell
See on Scoop.it – lean manufacturing
“I recently received an email from a guy challenging the legitimacy of organizing into value streams and lean accounting. The linchpin of his argument: ‘I can’t find anything saying Toyota has done any of that.’
[…] Seems to me if we want to get all Toyota-y about things we have to take Shingo’s words to heart when he wrote, ‘We have to grasp not only the Know-How but also Know-Why.’
[…]Using Toyota as the acid test for whether something is lean or not is rather naive and intellectually lazy. In most companies and most plants, asking ‘what would Toyota do?’ is the appropriate question – not ‘what did Toyota do?’”
Learning by imitation
Imitation is effective for learning. We condemn outright plagiarism, despise imitation, and value creativity. Yet even an original and unique artist like Pablo Picasso learned as a child by copying paintings. In Karate, you learn a new kata by following others. As you memorize the sequence of moves, you learn to perform them with speed and power. Then, as Jim Mather teaches, you learn the underlying self-defense principles embedded in the kata.
Until the 1970s, many Americans and Europeans dismissed “the Japanese” as imitators who copied what they saw and then competed with the original creators through low wages. But I have not heard this in decades. A principle behind the way Japanese traditional arts are taught is that know-how precedes and leads to know-why. Once you have assimilated techniques to the point that they are second-nature to you, your mind suddenly understands how they fit together as a whole and why they are necessary.
While this approach works not just for Karate, but also for sumi-e, sushi, flower arrangement, and even machining, it can be abused. I would not recommend it, for example, to teach math. Sometimes, what you ultimately achieve as a result of going through motions is only an illusion of understanding that rationalizes the years you have invested in training.
For Lean or TPS, there is no alternative to learning by doing. There is no way to gain an understanding of cells or the Kanban system without living through implementation on an actual shop floor. As a consequence, the first time you do it, you are following along and imitating. Once you understand what you are doing, however, it behooves you to add your own twist and adapt the concepts to your needs.
When brute force imitation works
On the scale of an entire company, we should also not forget that brute-force imitation sometimes works. Once I had in one of my Lean classes a student who was a former plant manager in a large, European auto parts company known for its successful implementation of Lean. “Everything you taught,” he told me,”I used in the plant, but I never knew why, until today.” As he explained to me, the company’s top management issued “guidelines” to plant managers that were specific on which tools to use, regularly audited the plants, and routinely fired the managers who did not comply, regardless of results.
It sounds wrong, but how do you argue with success? In retrospect, it worked for that company because it was in the industry for which TPS had been developed and, at least initially, creativity was not necessary to improve on the existing system. Where brute force imitation fails is in new and different industries.
How do you know “what Toyota would do”?
Either you are steeped in Toyota’s ways as a result of being an employee of the company for 10 years, and you have an idea of what its management might do outside of its core business — including the ways it might misunderstand it — or you have studied Toyota’s system from the outside, and you don’t really know what it would do.
On the other hand, you may have a deeper understanding of the challenge at hand than any Toyota manager. Rather than trying to figure out what Toyota would do, I would rather follow Soichiro Honda’s advice to his engineers: “Solve your own problems.” Learn everything relevant that you can, then use your own judgement. You will be responsible for the outcome anyway.
Divergence and accurate representation
The whole Lean movement started from people learning about the Toyota Production System (TPS). That Lean should diverge from TPS was inevitable, but the Toyota connection remains the key reason business professionals pay any attention to Lean. Given that the vocabulary itself has changed, making the connection on specifics is not always obvious. “Value Stream” or “Lean Accounting,” for example, are not Toyota terms, which does not make it easy to gauge the extent to which Toyota uses the concepts.
There is nothing wrong with Lean professionals inventing approaches beyond TPS, but it must be clear and the tools must stand on their own merits. Business executives assume that what they are being sold as “Lean” is what Toyota does. Where it is not the case, they must be told upfront.
See on www.idatix.com
Sid Joynson
January 31, 2014 @ 1:01 am
I find two quotations help us understand the copying/learning process. Too often people copy blindly. This works until there is a problem and they and then they will say it doesn’t work. We must understand the thinking behind the doing. The two quotes are;.
“Don’t be a collector of facts. Try to penetrate to the secret of their occurrence, persistently search for the laws that govern them”. Pavlov. —
“Understanding is my favourite word. I believe it has a specific meaning. To approach an object/subject positively and comprehend its nature”. Ohno.—
When lean thinking (1996) was being extracted from TPS not enough emphasis was given to Shigeo Shingo’s original thinking on the structure of productive activities. This created a serious flaw in lean thinking. —
In 1989 I had a one hour session by myself with Shingo and his interpreter. The major part of the time was Shingo explaining his concept that the production mechanism should be seen as a network of two flows; Processes and Operations. My reason for asking him about this subject was the fact that the same two pages on this subject appear in all his books. When I asked him how important this concept was he said it was fundamental that these concepts and their relationships were understood in order to make effective improvements in productive activities. The comments below are based on the notes I took at the time and my subsequent experiences.—-
He explained; Production is a network of two activity flows. Processes and Operations. —-
Processes. These are the sequence/flow of events that products and services pass through on their journey from raw material/information to being finished items. —
I.e. Storage —Transportation — Storage/delay —transformation — storage/delay —- transportation. Repeat —
Within the process flow there are two types of storage/delay; Lot Delay and Process Delay. —
Lot Delay. An item is delayed while the rest of the lot/batch is produced.
Solution —One piece flow. —
Process Delay. An item is delayed while it waits for previous items to be processed through the next machine/activity. Solution — Synchronise cycle times. —-
Operations This is the sequence/flow of activities conducted by people, machinery and systems on the raw materials/information and products at each process stage. —-
I.e. Set-up — Essential motion — Auxiliary motion — Marginal allowances. Repeat—S.E.A.M
(Essential motions are those that produce what the customer requires; are valuable to them. i.e. P.S.E. P — Product- the physical item. S — Service to support the product. E — Experiences the customer enjoys acquiring, using and maintaining the product/service). —-
If you see processes as the vertical flow and the operational one as a horizontal flow along from each process stage you can see his network. —-
What then becomes obvious is that only the essential step of the transformation process is valuable to the customer, everything else is waste and is a candidate for elimination. —
His fundamental rule is to improve the process before the operation. Don’t improve transportation eliminate it. —
The ultimate goal is one piece flow with synchronised cycle times that represent customer demand rate. —-
When you see all these elements you can appreciate Shingo’s genius for simplicity. They should be the basic principles for all lean thinking and waste elimination activities.—
When you understand Shingo’s network, it becomes easy to see the waste in any system.
Sid joynson
January 31, 2014 @ 1:00 pm
My previous comments were Shingo’s basic principles for removing waste from the production flow. The following are on his Poke-Yoke system for achieving zero defects. Understanding the basic principles for achieving waste free flow and zero defects is the foundation of a lean operation.—
I had an opportunity in 1989 to discuss Poka-Yoke with Shingo himself. Below are extracts from my notes on his comments, and my own experiences over the last 25 years. Initially he chided me for talking about it as an individual technique, and said it should be seen as the tool for implementing his system of ‘source inspection’ and guaranteeing zero defects.—
Shingo explained that traditional ‘long cycle’ inspection systems wait until an error in action produces a defective item, the defective item is then found by inspecting the output. His concept of source inspection uses the ‘short cycle’ inspection system. In this system the action itself is checked 100% using mechanical means. If an error occurs, immediate action is taken to correct it before a defect is produced. With this methodology we can guarantee zero defects to the final customer.—
The basic system is simple;
The Poka-Yoke methods/devices should be designed to detect deviation from the standard actions and outputs required to satisfy the customer’s requirements.
This can be done in three ways;
a) Physical contact.
b) Fixed values.
c) Motion steps.
In some cases at the original design stage the part can be made a Poka-Yoke device by ensuring it can only be assembled/used in the correct way.—
They should also check for deviation in the 3M’s of actions and items;
Missing. Action or item not there.
Misplaced Action or item there, but in wrong position.
Malformed. Action or item are there but wrong, size, shape, colour, temp etc.—
When designing Poka-Yoke devices they must check for specific deviations in the 3M’s using; a, b and c. This can be done with a ‘what can be’ 3 M’s analysis.—
The Poka-Yoke device should then;
1) Control the operation. Stop the process when an error or defect occurs.
2) Warn the operator.Signal to the operator that an error or defect has occurred.—
They should be applied at the following check points;
1) The source action. (source check) This is the ideal as it gives zero defects.
2) Output of the action. (self check) .This is our second choice as the output will be defective if the PY device is activated, but it will not be passed to the internal customer.
3) Before the next process. (successive check). At this stage the item will be defective if the PY device is activated, but it cannot go to the final customer.—
With this system in place it is now possible to consistently achieve; ‘Zero Defects in our activities and production processes’. —
This was Shingo’s original goal in 1965.
If applied to safety it is possible to achieve ‘Zero Accidents’. I do not understand why this methodology is not more widely used in this area. —
The most impressive example of Shingo’s system I have experienced was on an assembly line for inlet manifolds in Japan. We were allowed to work on the line and challenged to produce a defective assembly. It was impossible to produce one, and we had some very talented people trying. —
Once our front line people understand this system they become some of the best designers of Poka-Yoke devices.—
The goal is to identify deviation from the desired conditions or actions in any situation.—
A good example is the selector stick on an automatic car gearbox. If the stick is not in the park position the poke-yoke switch is not activated and the engine will not start. Zero defects in all situations. Shingo pointed out to me that this would be impossible to achieve with statistical techniques.—
Having had the privilege to study with the Shingo, I do enjoy sharing his thinking .