Skip to main content

Implementing Process Of On Going Improvement (POOGI) Part 2 - Introduction to Bottleneck

At the first part of Implementing POOGI , I described that in order to balance a system, market demand should not be matched to resource capacity because of the relationship of two phenomenons: Dependent Events and Statistical Fluctuation. However, you should balance the capacity of the production "flow" to market demand. In this case, some resources may have idle time and some may turn into system constraint. In fact, the capacity of the flow should be little bit less than the demand, so if demand goes down you do not loose money.

In balancing the flow, you may realize that some resource have less capacity than market demand and are impacting the entire flow. These resources are bottlenecks or to put it in a better term,system constraints. So, bottleneck is a resource whose capacity is equal to or less than demand placed upon it. And a non-bottleneck is any resource whose capacity is greater than the demand placed on it.

Here are couple of facts on bottleneck / Constraint:

  • Bottleneck or system constraint is not necessary bad or good. It is just the reality of the system. How you deal with constraint and how do you use a bottleneck to control the flow through the system and into the mark is important. So if a person happened to be a constraint or bottleneck, that dose not mean that such a person is bad or he/she is good! 
  • Because bottleneck controls the flow, an hour lost at a bottleneck is an hours lost for the entire system. Therefore, the real cost of bottleneck is equal to total expenses of the system divided by the number of hours the bottleneck produces. So, the more hours bottleneck produces the less expensive it becomes!
  •  As a general rule, make sure bottleneck works on today's throughput and not months from now.
  • One of the most effective ways of increasing the capacity of a constraint or bottle neck is to take some of the load of the bottleneck and give it to non-bottleneck.
  • In order to optimize the use of bottleneck, you first need to make sure the bottleneck/constraint's time is NOT wasted by sitting idle, working on items that you really do not need, by working on defected items.
  • Balance the flow of work against market demand and NOT capacity.
  • Bottleneck is not bad or good, it is a reality of the system, what do you do with bottleneck is important.
Similar and Related Blogs


Popular posts from this blog

Escalate, Escalate, Escalate!

What is escalation at organizations? Is it a way to solve problems? Is it a way to report things? Is it a way to put more pressure? Is it a CYA technique? What is it? How do you use it at your organization? How other colleagues of yours use escalation? Really, think about it and observe.

At IT service companies, leadership measures the performance of IT Help Desk by number of escalated work items over a period of time. The less escalation the better. The reasons are simple:

It is cheaper for companies if an IT Help Desk Specialist resolves an issue than an experienced technical specialist at one or two level higher. This is simple math, one gets $X and the other get $X*2And when client gets result fast, he/she will be happier. So, less escalation equals happier client in IT Services. Client raise an issue, IT Help Desk Specialist resolve it, BOOM, Next!

At organizations, It is amazing (sadly) to see how much lower level managers escalate problems, that they and their fellows can resol…

Multitasking Gets You There Later

A Gift from me to all people who are suffering from multitasking or low performance dilemma ;)

Modern business relies on multitasking to get work done. Employees are evaluated on their ability to multitask. IT professionals are routinely assigned to multiple projects. Did we always do this? Does multitasking work? What are the real impacts of multitasking? Is there an alternative?

Unitasking is a retronym to represent how we used to work on software before we multitasked. By multitask here, I really mean "work on multiple projects". Modern business has come to call that multitasking and considers it to be a strategy for more efficient worker output. We also multitask at a small scale in our daily lives, at work or not. There are similarities at both scales in how we do it and what it does to us.

DAD Inception Phase Workshop Agenda

Disciplined Agile Delivery (DAD) realised the reality of the projects and introduced back phases to Agile community. Whoever works in a project based company, especially a project based company where projects are usually less than one year in length and each are for different clients, understands the reality of Agile in such environment. When you start working on a new project for a new client, it is essential to go through a phase that you get to know each other better, to understand the business purpose of the project, to understand the scope of the project, to know what are the high level architecture and what technologies are going to be used and who is the initial team, and if funding is available and also when things must be delivered and to whom.
In answering these questions you may need to meet with different people, run couple of workshops and brainstorming sessions. And this is called Inception Phase. As DAD is more like a goal oriented decision framework and not a prescrip…