I would be surprised if folks in operations have NOT heard the old story about filling a 5 pound bag of potatoes with 10 pounds of potatoes always results in mashed potatoes.
And I would bet that most operations people understand that releasing more work into production than what is coming out will, invariably, lead to more work in process inventory (WIP) and longer lead-times not to mention the mess and chaos creates for the organization.
You knew this, right? Either through formal education, your intuition or your experience, you realize that there is a direct relationship between production lead-time, work in process and throughput (i.e. output). Perhaps you already knew that queuing theory explains this behavior. Little’s Law states that in a stable operation, the amount of work in process (WIP) is equal to the average Throughput of the resource multiplied by the lead-time or if you like math:
WIP = Throughput x Lead-time
While this relationship is well-known and intuitively obvious, it’s still amazing that in the dawn of 21st century, how many organizations seem to ignore this little inconvenient truth. If I had a nickel for every time I observed an organization releasing more work into the system than its output, I would have long retired.
The typical excuse I hear is that we are just trying to keep our people busy. A very innocent and worthy goal, right? And yes, the premature release of work is extremely effective in keeping people busy.
But keeping ‘busy’ and being ‘productive’ are two different things. Releasing work at a rate faster than what’s coming out of the system will indeed keep people busy. They will be busy looking for missing material, busy looking for required tools, busy rescheduling orders, busy expediting materials, busy explaining to other customers while orders relate, busy explaining to finance why costs are so high, busy explaining the sales why lead-times are so long, busy explaining why service-level stinks. I’m sure you get the point since you most likely have been this routine at least a few times in your career.
So why do we continue to do something that we know is stupid? Obviously it must be satisfying some human emotional need, since it cannot be justified by any rational basis. And we already suspect the likely answer - the opposite of busy is perceived as doing nothing and doing nothing is viewed as waste. And, in these days, who wants to be viewed as waste?
We need to understand that there is a fundamental conflict at play. On one hand, in order to be productive we should not release work early, while on the other hand, in order to be perceived as being valuable we should release work early.
This is where the art and skill of the operations professional must come into play. Your challenge is to provide the leadership to assure that work will be released only when it’s time to be released and at same time, provide assurances to your staff that pacing release to output is not in anyway going to negatively impact their careers. In other words, sometimes it’s okay to be idle. Take this time for cross training, conduct some 5S tasks, perform some preventative maintenance etc. You can still get some value out of the idle time.
As an operational professional, you must have a clear understanding of why this vicious cycle has to be broken – this is why you get paid the big bucks to run the operation!

Recent Comments