"They are completely different indeed. They differ in their purpose, their practice and their outcomes. Lean is about self-reflection and seeking smarter, less wasteful dynamic solutions together. Taylorism is about static optimization of work imposed by 'those who know' on 'those who do.'"
Sourced through Scoop.it from: www.lean.org
Michel Baudin's comments:
Yes, "Scientific Management" was just a marketing label for theories that weren't truly scientific but were instead based on a simplistic view of human nature. And Taylor's stopwatch time studies were just aimed at increasing production at every operation with no consideration of flow. I would, however, ask for a more accurate and complete story
"It seems to be popular these last years and more recently to explicitly state that Lean is not (only) about cost reduction or cost cutting. See the recent posts by Mark Graban or Matt Hrivnak. So let me be somewhat controversial in this post (which I think is allowed to spark the discussion) and drop a bombshell: I think Lean is about cost reduction."
Sourced through Scoop.it from: www.linkedin.com
Michel Baudin's comments:
I know that much of the TPS literature is about "reducing costs," but it never includes any discussion of money! Ohno is even quoted as saying "Costs are not there to be measured, but to be reduced." On the face of it, it makes no sense, because cost is an accounting term intended to represent the monetary value of all the resources spent to achieve a result.
Can Lean do a do-over? Nearly 30 years after the start of the Lean movement, there is widespread agreement that things have not gone according to plan.
Sourced through Scoop.it from: www.bobemiliani.com
Michel Baudin's comments:
Bob's title for the article is just "What Went Wrong?" which I feel needs to be set in context.
I agree with him that the most popular "Lean tools" are peripheral at best. None of the ones he mentions -- 5S, visual controls, value stream maps A3 reports, or gemba walks -- would make my list of what should be taught and applied first in a Lean manufacturing implementation. I would, on the other hand, include SMED, cell design, assembly line design based on takt time, etc.
Philip Marris and I got to know each other on line, by participating in the same discussion groups, and met in person last year. The following conversation was recorded a month ago, in the Marris Consulting office in Paris:
Philip Marris: Hi, Michel, welcome to Paris! I am glad to take this opportunity to ask you about one of your books that I love, called Working with Machines. As far as I know it is one of the rare books on that subject, at least in terms of treating it in as much detail as you do, and it is about a subject very close to my heart, which is the relationship between the worker and the machine. Can you tell me what made you want to write the book and what the main messages are?
Michel Baudin: Well, what made me write it is that putting together systems of people and machines is central to manufacturing, and one of the things I learned from Kei Abe early in my career in consulting. There are a number of techniques like the work-combination chart, which is a typical tool of this area, and there is not very much written about it in English. You have books about automation, but the American books about automation say nothing about people. It's like people are an afterthought. You get books about FMSs, and you see diagrams of machines, but you never see information about what people are supposed to be doing.
Seen this morning in a Lean consultant's blog:
"Two decades later, VW has topped Toyota as the world’s number one automaker, but Toyota generally is considered to be [...] far more productive. In 2015, VW employs 600,000 people to produce 10 million cars while Toyota employs 340,000 to produce just under 9 million cars..."
Is it really that simple? VW produces 10 million/600,000 = 16.67 cars/employee/year, and Toyota 9 million/340,000 = 26.47 cars/employee/year. Ergo, Toyota is 60% more productive than VW -- that is, if you accept cars/employee/year as an appropriate metric of productivity. Unfortunately, it is a bad metric that can easily be gamed by outsourcing.
Akio Toyoda is rolling out an aggressive overhaul of Toyota Motor Corp. that aims to improve everything from manufacturing and product planning to design and human resources.
Sourced through Scoop.it from: www.autonews.com
See on Scoop.it - lean manufacturing
Abstracting underlying principles from practices is essential when you are trying to learn from the way an organization works, for the purpose of helping other organizations, engaged in different activities in different contexts. Unless you can do it, you are reduced to just copying practices without understanding what problems they were intended to address.
Unfortunately, articulating a set of principles is hard because they must be (1) understood, (2) actionable, and (3) memorable. Here are a few meta-principles on how to achieve these goals:
- Banish words like "thoroughly," "rigorous," "towering," "powerful", or "fully." If the meaning is in the eye of the beholder, it doesn't belong in a statement of principle.
- Express principles as an action verb followed by a single object. "Develop," "create," "cancel," or "hire" are all appropriate action verbs in a statement of principle. If you have multiple objects, you need a statement of principle for each.
- Keep the number of principles down to a maximum of five. Otherwise, they won't be remembered. Most Jews can't recite the 613 commandments in the Torah; most Christians, their 1o commandments; most Americans, their bill of rights. If you want principles to be remembered, make a shorter list.
"Obeya" (大部屋) is Japanese for "Big room." The term has been getting attention lately in the Lean community as a solution for service operations or project teams and is even conflated by some with production teams' daily meetings on the shop floor, which don't take place in a room other than the production shop itself.
On the other hand, the idea of bringing together in one room all the stakeholders in an issue, problem, or project to communicate face to face, find solutions and make decisions is not exactly new. It's called a meeting, and those who wish to sound "Lean" without changing anything can call their meeting rooms "obeya." Those who wish to dig deeper, however, find a more specific -- and useful -- concept, if not a panacea.
Carl von Clausewitz, writer on military strategy and tactics
Originally "the art of the general," strategy is about which armies or fleets you deploy where and for what purpose. It goes hand in hand with tactics, which is the way each unit then engages the enemy. Always fond of military metaphors, business people have chosen to use the term"strategy" for their plans and decisions on products or services, markets, promotion methods, technology, organization, and financing. To Harvard Business School's Michael Porter "the essence of [business] strategy is choosing what not to do."
Toyota's Japanese documents and their English versions often mean different things. Recently, looking at the Japanese version of The Toyota Way 2001, I was surprised to find that what is translated into English as "Continuous Improvement" is "Chie to Kaizen" (知恵と改善), which means "Wisdom and Continuous Improvement." In the English version, "Wisdom" was not only dropped from the main header, it appears nowhere. Continue reading