| This art: Velocity - Combining Lean, Six Sigma and TOC |
World Class: The value adding, smooth & perfect organization |
Review of the book “Velocity”: combining methods accelerates process improvement
In my opinion, this book about achieving breakthrough performance is also a breakthrough in manufacturing theory. However, there is also a minus: The examples of Lean and Six Sigma are weak and don’t show how these methods can really accelerate a TOC implementation. This is a missed opportunity. | |
|
By Gerritjan van der Ven, plant manager Balchem Italy, august 2011
One of the authors of the business novel Velocity, Jeff Cox, was also co-author of Eli Goldratt’s bestseller The Goal. This book of the founder of the Theory of Constraints (TOC) is the mother of all business novels. If you are familiar with The Goal, you know what kind of plot to expect in such a book: A business under pressure, and a new manager who needs to realize a turnaround before it is too late. Cost cutting
Bottleneck Corporate Program Title: Velocity Subtitle: Combining Lean, Six Sigma, and the Theory of Constraints to Achieve Breakthrough Performance Authors: Dee Jacob, Suzan Bergland and Jeff Cox (co-author of The Goal) Additional information: 310 pages, Free Press January 2010, ISBN 978-1-4391-5892-0 + Velocity is a business novel in the style of the famous bestseller The Goal of Eliyahu Goldratt, founder of the Theory of Constraints. Velocity is very readable, and a pleasant way to get familiar with the idea to join the merits of TOC, Lean and Six Sigma. Another similarity with the books of Goldratt: Velocity is a book that makes you think & reflect. +- The purpose of Velocity is to get inspired. For a real understanding of the different improvement theories, a more profound study of the individual methods is required. The examples of Lean and Six Sigma in the book mainly stress the pitfalls of these methods. Therefore, a follow-up study may help to envision how a combination of Lean, Six Sigma and the TOC can really accelerate improvement. Then, what is promised in the book title - Velocity - could become a reality. - The fact that the book is a novel facilitates the access to the ideas, but it is difficult to find key concepts back for re-reading and reference. Besides that, with 300 pages the book is rather thick. In an equivalent textbook the same ideas could have been presented in a more compact way.- In the end TOC emerges as the superior theory. This is no surprise, since the authors are consultants of the AGI Goldratt Institute. The examples of Lean and Six Sigma in the book are weak and don't show how these methods can really enhance a TOC implementation. This is a missed opportunity. In the end, the authors stress that TOC can strengthen an existing Lean Six Sigma implementation. The reason for this line of approach might wel be that there are far more existing Lean Six Sigma then TOC implementations. However, in my opinion, it is far better to formulate it the other way around. Use TOC to develop your strategy, then implement this strategy by applying practical Lean and Six Sigma tools. A solid ISO-system supports this approach. Key Concepts 1. Throughput Profit = Throughput – Operating Expenses
with Throughput = Volume Sold x (Selling Price - Variable Costs) In applying the TOC, it is determined first what the current bottleneck is, which stands in the way to make more profit. Next, all the improvement efforts are focused on this business constraint. Implementation of the drum-buffer-rope principle, in which a bottleneck dictates the planning, is a good way to do this. Apart from that, the TOC does in my opinion not provide many practical tools to relieve or elevate a bottleneck. In my experience, this is where Lean and Six Sigma can be applied to strengthen the TOC! “Because of time, Mr. Reese. Time within the overall flow. That is why we subordinate all other processes to Godzilla. Because the productivity of ‘Zilla determines the productivity of the entire production system – and so determines our throughput”
2. Value “From our VSM, we generated a very long list of potential projects. Let me assure you, we have many, many years of project opportunities ahead of us. But of course we need to select for this year only those that will have the greatest impact on waste elimination with the largest potential gains in our journey to Leanness.”
3. Variation “Yeah, this sounds like a job for Six Sigma, said Kurt. “That spread from fifty-two minutes to … what was it? Fourteen hundred minutes … man, that’s what I call variation. That’s just going to kill us.”
Excuse me, said Jayro, but you do realize we’re talking about a specification here? Kurt regarded Jayro with a blank look. “The range from fifty-two minutes to fourteen-ten is not statistical variation”, said Jayro. Missed opportunity As I said before, it is my personal experience that Lean and Six Sigma can be used to really accelerate a TOC implementation, as the book title Velocity suggests. Therefore it is a pity that there isn’t a story line in which Murphy (TOC) and Wayne (Lean Six Sigma) patch up their quarrel and start to work together! The strength of TOC is that it identifies autoclave Godzilla as the key operation within Hi-T. It is however strange that the people in the book decide “to live with this constraint”, instead of using Lean and Six Sigma tools to elevate it. For example, they could have used a SMED-analysis (from Lean) to accelerate loading/unloading of the autoclave. This would have reduced the set-up times. In addition, the R&D department could apply Design for Six Sigma to define minimal “soak-times” for the different products to be processed in the autoclave. That way, the reader would have seen how Lean and Six Sigma can be used to accelerate the throughput! Comments by the authors, Dee Jacob and Suzan Bergland, on the review
Don’t elevate the constraint immediately, but stabilize the system first Thank you for reviewing Velocity. Our background, which is rich in both TOC and Lean Six Sigma (LSS) methodologies, drives us to take a systems view. As Dr. Juran emphasized, the first step to improve a system is to stabilize it, while recognizing that there is variation in it. This stabilization can be done quickly by implementing a constraint-based architecture. As outlined in Goldratt’s book The Goal, after identifying the constraint, TOC "exploits" the constraint and subordinates everything else to it. Exploiting the system constraint means that we take advantage of it. We use it as an instrument to control and stabilize the system, rather than trying to eliminate the constraint immediately, which is the inclination of many people. If you do that, the opportunity to stabilize is lost. This is why elevating the constraint comes later (as fourth step in TOC's five focusing steps). There is a tendency among many to view the system constraint as an obstacle to productivity and throughput, but as long as the system constraint's capacity is equal to market demand, there will be no loss of potential throughput. More than that, a system with a constraint can be more productive. In many systems, exploiting the constraint is sufficient to meet the market demand, and LSS brings great value at this stage. With a stable system, improvements using Lean and Six Sigma can be targeted to have the maximum bottom line impact. If this is not enough, then the next step would be to elevate the constraint. Finally, our TOC-LSS methodology is based on cause-and-effect logic. In the book, Amy Cieolara and her management team develop their strategy for turning around the business using logic diagrams. Initially, these maps show that Hi-T should implement a constraint-based system architecture. Once Hi-T has stabilized the system that way, there is concern within the story that LSS will no longer be used. However at the end of Chapter 16, the management team adds the following into their logic map: “Prior to approval, we evaluate all improvement projects based on their ability to increase T, and to reduce I and OE – and on their ability to advance overall system performance.This leads to focused improvement projects, that have significant impact with increases in T and reductions in I and OE. The examples that the review provides of using SMED on Godzilla and DFSS to improve the product specifications could be excellent examples of such focused improvement projects! - Dee Jacob & Suzan Bergland, july 2011 Need help to implement World Class Operations Management? Here's a list of our sponsors/advertisers of the site-section 'WorldClass'. Referral to this article on the internet? Use as link: http://www.business-improvement.eu/worldclass/Velocity.php |
|
| © C.J. van Ede 2006-2011 (NL/Europe/Worldwide) Last update: 24-08-2011 | |