Process Bloat, a Hidden Indigestion
The Hidden Factory is a term that refers to activities in an operation that were not designed into it, but grew over time as workarounds for the current process. Most organizations have some form of a Hidden Factory and being able to “see” these hidden factories in an organization requires learning to see what waste is and understanding that waste in any operation — service or manufacturing — can be a substantial drain on the bottom line, top line, on employee morale, shareholders and, most importantly, the customer.
In fact, one very important litmus test for an activity is this:
If the customer knew the details of process x, would she be willing to pay for it?
In other words, suppose substantial rework was required to manufacture a widget and that rework cost was baked-into the cost of 1 unit of a widget, would the customer be willing to pay for the firm’s defects? Would the customer be willing to pay for the firm’s internal inefficiencies?
What is a Process?
A process is an systematic activity comprising of smaller activities that culminate in an outcome — service or product. A process can take up time, space, and resources. All processes can be categorized into the following categories: Value-added, Non-value added but necessary, and Non-value added.
From the Customer’s Perspective:
- Value-added: This step in the process adds form, function, and value to the end product and for the customer.
- Non-Value-Added: This step does not add form, function, or assist in the finished goods manufacturing of the product.
- Non-Value-Added-But-Necessary: This step does not add value, but is a necessary step in the final value-added product.
(2) & (3) naturally create waste, of which there are 7 types:
- Over-Production: Producing more than is needed, faster than needed or before needed.
- Wait-time: Idle time that occurs when co-dependent events are not synchronized.
- Transportation: Any material movement that does not directly support immediate production.
- Processing: Redundant effort (production or communication) which adds no value to a product or service.
- Inventory: Any supply in excess of process or demand requirements.
- Motion: Any movement of people which does not contribute added value to the product or service.
- Defect: Repair or rework of a product or service to fulfill customer requirements.
It’s important to understand “Value” in terms of the customer. From the customer’s perspective, “Value” could be defined in the form of a question:
Which process steps (and associated costs) do our customers not have to bear?
It’s a revealing question — most companies are glad that they do not have to reveal how their product or service is created, for fear of their inefficient processes and wasteful operations revealed to the customer. This stance is sometimes aptly called “not revealing how the hot dog is made”, amicably referring to the unknown contents of the hot dog.
Process Cycle Efficiency
There is a metric that helps to identify how much of a process is actually value-added. It requires a few things:
- Map the process.
- Identify the Value-added steps, non-value added steps, and the non-value added but necessary steps.
- Stratify your map according to the items in #2
- Add a time dimension to the process steps.
Once you have completed steps (1) – (4), then you can simply calculate how much is actually value-added, as a percentage. The time for the entire process — end-to-end — is called a cycle time. To identify the Process Cycle Efficiency, you just divide the value-added time by the cycle time for the process.
Process Cycle Efficiency = (Value-added Time / Cycle Time)
For example, take the hypothetical process below:

The process above has a cycle time of 860 seconds. So, the Process Cycle Efficiency could then be calculated by doing the following:
Process Cycle Efficiency = 182 / 860 = .21, or 21%
In other words, only 21% of the process above is considered value-added to the customer.
the customer would consider 79% of the process above as waste
Put another way, the customer might be bearing 79% of the cost associated with the waste above. Knowing this, the firm should aim to increase the Process Cycle Efficiency of the process by eliminating or reducing the waste.
Data like this can help the firm increase their value-added percent to the customer by eliminating or reducing the waste in their process. Doing this would put the customer first and allow the firm to “get their house in order.” I consider the above exercise to be simple, yet incredibly helpful for the firm to make sure that they provide maximum value to the customer; it’s a fiduciary duty to the customer.
Think about your processes? How much is really value-added to the customer?
WP Cumulus Flash tag cloud by Roy Tanck and Luke Morton requires Flash Player 9 or better.
If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.
Comments
Previous post via @shmula “Process Bloat, a Hidden Indigestion” http://tr.im/jn3o Excellent info on understanding process efficiency
This comment was originally posted on Twitter
Short and to the point RT @shmula blog post: Process Bloat, a Hidden Indigestion http://tr.im/jn3o
This comment was originally posted on Twitter
Great post as usual. I’m in the semiconductor industry and I’d say lots of our waste is due over-production. And the conventional wisdom for the most part is we have to live with it. Some major obstacles that prevent reduction in over-production are: 1) Immense pressure to keep capital utilization high – $3B investment in a fab that will be obsolete in less than 5 yrs. 2) When production starts, it is not known what the exact products will be at the end of fabrication (due to semiconductor process, different CPU speeds is the end result even though each die is the same). Thus keep the tools running and scrap what we don’t need in the end is the prevailing mantra. Talking about cost accounting gets nowhere because of the sheer expense of fabrication investment. Would be interested in your thoughts on tackly over-production in this respect.
http://www.shmula.com/1322/process-bloat-a-hidden-indigestion on hidden factory waste. How does this apply to software? Agile?
This comment was originally posted on Twitter
Most software companies have complete systems dedicated to the management of bugs … the developers introduce them – but don’t know how many – then we have a game: How many bugs can the testers and customers find? We also have whole process segments and supporting tools dedicated entirely to handling bugs. Do we produce products for customers to use – or are products just hosts to bugs? … Either way we seem to spend more time on the bugs than we do on the products. So if we are talking about Hidden Factories then the Bug Factory has to be the mother of them all … Value to the customer? Well, I am sure they would rather have a product that worked …
Leave a comment
Additional comments powered by BackType


blog post: Process Bloat, a Hidden Indigestion http://tr.im/jn3o
This comment was originally posted on Twitter