作為全球兩大熱門管理方式6sigma與lean模式, 近年來國(guó)內(nèi)眾多大型企業(yè)先后導(dǎo)入這些管理模式, 取得的實(shí)際改善成果是多了一堆虛偽的6sigma或lean改善報(bào)告? 還是產(chǎn)生了實(shí)際的改善成果, 或許只有那些企業(yè)的CFO們知道了, 在2006年, 美國(guó)生產(chǎn)運(yùn)營(yíng)管理權(quán)威機(jī)構(gòu)—美國(guó)運(yùn)營(yíng)管理協(xié)會(huì)APICS抽查了21家企業(yè)的100多個(gè)改善項(xiàng)目, 其中有11家導(dǎo)入了6sigma, 4家企業(yè)導(dǎo)入了lean, 6家企業(yè)在導(dǎo)入前面兩種管理模式后,又導(dǎo)入了TOC管理模式, 結(jié)論得出TOC的改善效果是6sigma的20倍, 是lean的9倍, 并將研究結(jié)果在2006年五月的APICS雜志進(jìn)行發(fā)表. 相關(guān)原文請(qǐng)參考下面網(wǎng)站鏈接: (A study released in the May, 2006 APICS magazine demonstrates that TOC is twenty times as effective as Six Sigma, and nearly ten times more effective than lean at causing cost savings. I find this remarkable result especially interesting because cost savings are a side benefit of TOC...TOC focuses on increasing Throughput. This is the only scientific double-blind study of its kind performed "in the wild", i.e. in actual business plants. The authors summarize the results of over 100 improvement projects, where: 11 plants applied Six Sigma 4 plants applied Lean 6 plants applied TOC, Lean and Six Sigma The results are unequivocal:
A little further analysis shows: If we assume linearity (i.e. that the treatments are additive), we can estimate TOC alone. The 11 six sigma plants saved 0.63% per plant, and the 4 Lean plants saved 1.5% per plant. So, we subtract 6x(.63+1.5) = 13% for the 6 plants that did the combined, the estimated TOC alone savings is 76%, or ~13 % per plant. So, TOC is twenty times more effective than six sigma, and around nine times more effective than lean. Lean Project Management (LPM), API's extension of CCPM, takes the same approach as the workers in these plants: combining the synergistic effects of the three improvement approaches. The combination caused savings of 14% (of the total saved) per plant, or 24 times more effective that six sigma alone, and ten times Lean alone. Pirasteh, R. and Farah, K. (2006). Continuous Improvement Trio: The top elements of TOC, lean, and six sigma make beautiful music together. APICS magazine, May, 2006 pp. 31-36
|