Value Added per Employee Hour: Best Agile Metric? Part Five
I've been going on (and on) about Value Added per Labor Hour and how it drives (or ought to drive) manufacturing improvement. If you've read the first four posts you've probably seen some things that strike you as really old school ("Scrap is bad? Wow! There's something new!) and other things that are newer but fundamental agile concepts (Don't run product that's not scheduled to be delivered and don't run above rate.) that you probably agree with because you're tuned into lean ideas but that some manufacturing managers might quibble with.
In this post, I want to go a bit farther looking into how the metric ought to be driving manufacturing practice, if it's taken seriously.
Let's take one of the elements of the formula that, I'm guessing, no one finds controversial: scrap is the enemy.
I had a client that had a number of plants around the country. Two had serious scrap problems, so I was sent to form employee teams (to it's credit, the company had good success with and was committed to employee involvement) that would, it was hoped, solve these scrap problems. Over several months, here's what I found out as I worked with the teams, focusing on scrap more carefully and more intently than we ever had before.
Remember, I picked this particular element because it's probably the least "controversial". The point is that, even in the case of an element as apparently straightforward as "reduce scrap", there can be difficulty in changing the culture and behavior of the organization. Imagine how tough it is with something like "Run at rate. Not above. Not below."
The story has a happy ending. As the plants addressed the issues above (and their overall cultures regarding scrap and other elements of performance) the scrap problems went down.
In this post, I want to go a bit farther looking into how the metric ought to be driving manufacturing practice, if it's taken seriously.
Let's take one of the elements of the formula that, I'm guessing, no one finds controversial: scrap is the enemy.
I had a client that had a number of plants around the country. Two had serious scrap problems, so I was sent to form employee teams (to it's credit, the company had good success with and was committed to employee involvement) that would, it was hoped, solve these scrap problems. Over several months, here's what I found out as I worked with the teams, focusing on scrap more carefully and more intently than we ever had before.
- Operators tracked scrap. Data were entered in to the company's very capable ERP database. I found that it was possible to identify scrap by line, by type of scrap, by shift, by type of equipment, and by plant. I also found out that, for the most part, no one had ever dug into any of this data beyond the point of looking at the scrap rate for the entire plant each month.
- The equipment wasn't in terrible shape but it wasn't difficult at all to find C-clamps, duct tape, and binding twine holding things together. The teams went down each line and made long lists of minor repairs, fixes, improvements. These lists were treated (initially) as "not addressing the real problem of scrap".
- There had been attempts to develop setup sheets and run sheets but they weren't in regular use.
- Initial employee training focused on quality and spent a good bit of time making sure operators knew how to inspect the product they were making. Operators were responsible for checking their own quality.
- There was a strong QA function at the plants, in that QA inspectors also carefully checked product. The relationship between QA and production was usually fairly testy and it got worse as scrap problems got worse.
- When a problem with the line occurred, lead technicians made valiant efforts to fix the problem without shutting the line down. In part this was because, often, it helped to have the line running as adjustments and repairs were being made (so long as it could be done safely). In many cases, though, it was because shutting the line down and starting it back up was a pain, and lead techs were perenially hopeful they could solve the problem before they needed to shut the line down. So they'd work on the problem, running scrap the whole time for six, ten, twelve hours.
- Setup scrap was a big part of the problem. Changing tooling was quick and easy enough, but getting good product often took a long time. Changeover times (last good part to first good) weren't measured. Setup scrap was measured but, insofar as I could tell, no one looked at it apart from the overall scrap measure.
- The product was plastic so scrap was immediately re-usable. It was simply ground up and put back through the manufacturing process. In fact, high scrap in one periond led to low material costs in the next period.
- The raw material (plastic resins) was tough to work with because it was so variable at its best. (Changes in humidity could change the characteristics of the material.) The company used lesser grades of raw material as cost savings.
- There was little collaboration between the folks in charge of raw materials and the operating folks. Some of the worst "scrap days" came when the characteristics of the raw material changed, the raw material folks knew of the changes, but they didn't tell anybody in operations. Lines that had been running perfectly good product one minute, started running unusable scrap the next. Supervisors and lead techs would run around madly looking for causal tooling or equipment issues only to learn, perhaps hours later, that changes to the raw material had taken place.
Remember, I picked this particular element because it's probably the least "controversial". The point is that, even in the case of an element as apparently straightforward as "reduce scrap", there can be difficulty in changing the culture and behavior of the organization. Imagine how tough it is with something like "Run at rate. Not above. Not below."
The story has a happy ending. As the plants addressed the issues above (and their overall cultures regarding scrap and other elements of performance) the scrap problems went down.


Hello George
I have some general questions that you might please answer: the worked hour that you consider is it actual or just an average based on headcount or is it derived from the bom (bill of material)? Because you might find strange differences- I encountered that - btw I am using the same metric produced hours to cost and I agree that is the best way to describe and compare business. Please feel free to e-mail me at nicoara.bogdan@yahoo.com
Reply to this
Bogdan, thanks for the comment.
The Total Labor Hours would be actual Total Labor Hours. It wouldn't be be average hours or derived from the BOM. On the other hand, my experience is that hours derived from the BOM generally are developed with at least some of the wastes I mentioned in mind. For example, change over times are often on the BOM at a greater time than is actually required.
Reply to this
Hi George, I came across your helpful series of posts simply because I was looking for reliable information to confirm what I thought was meant by a client who recently asked us to use their given 'Return on Value Added Hour' $ number in our ROI calculation for the impact of our Priority Management with Outlook training for their sales team.
Like you said in your first post, it is a metric I too was familiar with but had managed to forget.
When we run ROI calculations we usually run cost of training and measured productivity gain against total cost of employment per person, and that's impressive enough. This very large IT industry client is using a Value Add Hour figure as a measure of overall individual salesperson contribution to the business, so it does not include other costs. It is still a useful metric and not one I have seen used very much here in UK outside the Manufacturing sector.
Your first post says you recently came across it, I am running a report on it as I write this post for a recent training for this client's sales team. Do you recall where you recently picked up on this metric?
Thanks for your helpful posts,
Richard
Reply to this
Richard,
I got it from a booklet (that I can't find at the moment) put out by Working for America Institute (workingforamerica.org).
Interestingly, WFA is an AFL-CIO supported organization.
Reply to this