Business software and tools built for better control.office@zenboxinfinity.com
ZBI Business Control Library

Labor Productivity

Labor Productivity: plain-English definition, formula, worked example, how to interpret the result, peer-based benchmark guidance, common mistakes, and management actions in the ZBI Business Control Library.

Category

Manufacturing Control

Back to category

What is Labor Productivity?

Labor productivity counts good units finished per paid production hour—output divided by direct and line-support hours in the same period. It is not wage cost per unit and it is not OEE. At TechnoSupply d.o.o. in Zagreb, 21,000 units over 3,200 hours is 6.56 units per hour—the rate the assembly cells actually achieved, not the rate on the routing sheet.

Why Labor Productivity matters

When productivity drifts from 6.8 to 6.2 units per hour on the same mix, payroll buys fewer good units—contribution per shift falls before anyone reclassifies variances. Low productivity forces overtime to hit the schedule; overtime raises unit cost and invites setup shortcuts that show up in scrap. Supervisors spend shift change firefighting instead of standard work. A hiring plan built on last year's peak rate while kitting waits consume 140 hours duplicates labour cost without fixing the bottleneck.

Formula and variables

Labor Productivity = Output Units ÷ Labor Hours

Output units — good units finished in the period (consistent with throughput reporting).

Labor hours — paid production hours including indirect support on the floor, same period.

Excel: =IFERROR(B2/B3,0)

Real business example

TechnoSupply d.o.o., a EUR 3.5M industrial components assembler in Zagreb, records April: 21,000 good units completed; 3,200 labour hours on assembly and line support. Labor productivity = 21,000 ÷ 3,200 = 6.56 units per hour. February on the same mix averaged 6.82—April's gap traces to 140 hours of waiting on kitting and 60 hours training new operators on Cell B. The operations director sets a 30-day target to recover 0.2 units per hour from kitting alone before approving a third shift.

How to interpret the result

Productivity links people hours to physical output—track it with the same SKU mix context.

  • Compare like periods: seasonality and product complexity move the rate without 'lazy' labour.
  • Separate constraint cells from ancillary stations when diagnosing a plant-wide drop.
  • Rising hours with flat output is a productivity problem even if attendance looks perfect.
  • Pair with scrap and rework—chasing speed alone can inflate hours on rework loops.

Benchmark context

Assembly plants in the EUR 2–6M range often land between 5 and 8 units per hour on mixed lines—meaningless without your routing. Benchmark against your best month on the same product family, then against peer disclosures in metal or electronics assembly if available. A sustained +0.3 units per hour year-on-year on the constraint cell beats comparing to a single-industry average from a textbook.

Red flags

  • Productivity down 8% for two months with flat mix—margin compression incoming unless price recovers.
  • Hours up, units flat, overtime rising—you are buying output, not improving rate.
  • New line productivity 20% below legacy cell after six months—training or layout failure, not 'ramp only'.
  • Productivity hero month coincides with scrap spike—speed without quality is borrowed output.
  • HR reports full attendance while productivity falls—waiting time or material starvation on the floor.

Common mistakes

  • Dividing output by headcount instead of actual paid hours—including absenteeism and partial shifts.
  • Mixing office hours into the denominator and wondering why productivity collapsed.
  • Ignoring overtime hours in the calculation while celebrating higher output.
  • Comparing productivity across plants with different automation levels without normalization.
  • Setting bonus on units only while hours balloon on rework and material waits.

What should management do next?

  • Track productivity weekly by cell with top three non-value-added hour categories.
  • Standard work refresh after any routing or BOM change affecting cycle time.
  • Cross-train kitting and line roles to cut waiting hours documented in time studies.
  • Review productivity in the same meeting as schedule adherence and scrap—not in HR silos.
  • Set hiring triggers on demonstrated productivity trend, not on peak-week anecdotes.

Related templates & software

FAQ

6.56 units per hour feels low—should we replace the team?

Compare to your own best month on the same mix first. If kitting waits account for 140 hours, fix flow before replacing people.

Do we include indirect labour in the hour denominator?

Include floor support that scales with output—kitting, line leads, material handlers. Exclude plant management.

Automation project promised 15% productivity—how do we verify?

Measure 8 weeks post go-live on the same mix; exclude launch-week training hours from the baseline.

Can productivity rise while unit labour cost rises too?

Yes if wage rates or overtime premiums outpace rate gains—track both for pricing updates.

Sales added a complex variant—productivity dropped. Is that acceptable?

Yes if margin per hour still clears hurdle. Re-baseline targets when mix shifts, do not punish cells for commercial decisions.

Summary

Labor productivity is output per labour hour. Measure it on consistent mix and hours, fix waiting and support losses, and align hiring with demonstrated rate—not hope.

Reviewed by ZBI Business Control Library · Last updated 2026-06-15