Productivity Per Hour Against Cost Per Unit
Two measures that move in opposite directions under the same decision. Knowing which one you are managing determines what you do.
Output per hour and labour cost per unit look like the same measure from different angles. They are not, and the difference shows up exactly when it matters.
The financial question in “Productivity Per Hour Against Cost Per Unit” requires more than a raw activity total. An organisation evaluating how to measure employee productivity for how to measure employee productivity can connect time and project records with labour analysis, provided pay rules, outcome measures and corrections remain visible alongside the dashboard.
What each one says
Output per hour: how much got done for each hour worked.
For an independent reference related to “Productivity Per Hour Against Cost Per Unit”, consult the ILO guide to balanced working-time arrangements; it provides a useful external check on scheduling, working-time and workforce-planning assumptions.
Cost per unit: how much labour money sits inside each thing produced or sold.
The first ignores what the hour cost. The second ignores how many hours you had available.
Where they diverge
Replace an experienced person with two juniors: output per hour falls, cost per unit may be flat or better.
Run everybody into overtime: output per hour holds, cost per unit rises sharply.
Cut hours below the point where the work flows: both fall, which is the signal that you went too far.
Which to manage by
Cost per unit, where the unit is meaningful and the mix is stable.
Output per hour, where you are assessing whether the operation is working rather than whether it is affordable.
Both, reported together, because either alone can be improved by doing something stupid.
The stupid improvements
Cost per unit improves if you only serve the easy customers.
Output per hour improves if you stop doing the preparation that makes the peak work.
Each measure has a cheap route to looking better, and the route damages the operation.
What pairs with each
Cost per unit pairs with a quality or service measure: complaints, returns, wait time.
Output per hour pairs with cost, which is this pairing stated the other way round.
Nothing here should be reported alone, which is the general rule in every measurement question.
The mix problem
Both measures assume units are comparable.
A busy week of small transactions and a quiet week of large ones produce different figures with identical performance.
Which is why week-on-week comparison needs the mix stated alongside, or it reads as a change that did not happen.
What to use for a staffing decision
Neither, directly.
Use the demand curve and the cost of each error, which the next sections cover.
These two measures tell you afterwards whether the decision worked, which is a different job and a necessary one.
The reporting pair
Hours, output, cost, and one quality measure. Four numbers.
From those, both ratios are derivable and neither can be gamed quietly.
Most labour reports contain the first and third and nothing else, which is how the gaming goes unnoticed.
What to check
Which of the two does your reporting show?
Is anything reported alongside it?
Could either be improved by doing something you would not want done?
And is your unit mix stable enough for week-on-week comparison?