KPI Library / Labor
Labor Productivity
Formula: Units produced ÷ total labor hours
Typical range: No universal target; track trend against your own baseline, ideally normalized to standard hours earned rather than raw units
Labor productivity measures output per hour of labor worked, calculated as units produced divided by total labor hours over the same period. Raw units per hour is the simplest version and the easiest to misread, because it treats every unit as equally labor-intensive, which is almost never true across a mixed product line.
What good looks like
There’s no external benchmark worth quoting here, because labor content per unit varies too much between products and industries for a cross-company comparison to mean anything. The useful version of this metric compares actual labor hours against standard hours earned, the engineered labor content of whatever was actually produced, which normalizes for product mix automatically. A plant holding labor efficiency (standard hours earned divided by actual hours worked) at or above 100% consistently is performing to its own engineered standard, regardless of what raw units per hour looks like on a mix-shifted week.
The trap with raw units per hour is treating a change in product mix as a productivity win or loss. A week that runs more of the simple, low-labor-content SKU will show higher units per hour with zero actual change in how efficiently anyone worked, and a manager who doesn’t know the mix shifted will draw the wrong conclusion from it.
Labor Productivity in Power BI (DAX)
With an hourly production fact, a labor hours fact, and a part dimension carrying standard labor content:
Units per Labor Hour =
DIVIDE (
SUM ( fact_production_hourly[units_produced] ),
SUM ( fact_labor_hours[actual_hours] )
)
Standard Hours Earned =
SUMX (
fact_production_hourly,
fact_production_hourly[units_produced] * RELATED ( dim_part[standard_hours_per_unit] )
)
Labor Efficiency % =
DIVIDE ( [Standard Hours Earned], SUM ( fact_labor_hours[actual_hours] ) )
Lead with Labor Efficiency % on any dashboard that gets compared across weeks or
lines. Raw units per hour is fine as a supporting number, but it shouldn’t be the
headline when product mix moves week to week.
Common mistakes
- Comparing raw units per hour across different product mixes. It rewards running easy parts over hard ones, not actual labor efficiency.
- Using headcount instead of actual hours worked. Headcount hides absenteeism, overtime, and part-time schedules, all of which change true labor input without changing the headcount number.
- Excluding indirect labor that’s required to run the line. Material handlers and line-side quality techs are often necessary to hit the output number; leaving them out of the denominator overstates true productivity.