This blog has moved. Go to SoftwareDevelopmentToday.com for the latest posts.

Monday, January 05, 2009

What is a bottleneck? (TOC)

When faced with a problem in a process, the first step you should take is to identify the process map and bottleneck.

This is nothing new, TOC people have been advocating this for a very long time as part of their "
5 focusing steps". But if it is why don't we do it?

Well, because it is hard work. To identify the bottleneck you can't just sit around a table and have a meeting with the managers to define what is the bottleneck. You have to go to the Gemba and analyze the process "as is", not as "it should be" and make some actual work on data collection and analysis.

Once you have done that you are then equipped to start searching for the bottleneck, it's location is buried in the data and process map you just collected.

To find the bottleneck you have to work hard, but finding it is just the first step! Much more is to come...

Labels: , , , , ,

at 17:53
RSS link

Bookmark and Share

0 Comments:

Post a Comment

Links to this post:

Create a Link

<< Home


 
(c) All rights reserved