Department-Wise Productivity: Measuring What Matters on the Floor

"Our productivity is 82%." Numbers like this are everywhere in factory MIS reports and they're almost useless. A factory-wide productivity number averages over wildly different departments, shifts, and operators — hiding the 60% drag in one corner under the 95% star performer in another. The aggregate looks fine while specific parts of the business bleed.

Productivity that's actually actionable lives at three levels: department, shift, and operator. Each level answers a different question, and each one drives a different fix.

Department-Level: Where Is the Drag?

Measured as `actual output ÷ standard output` for each department. The standard isn't a theoretical maximum — it's a reasonable benchmark you set from a good week. Run this weekly. A department persistently under 75% has either a capacity problem (need more headcount or equipment) or a process problem (handovers, material delays). The number tells you something is wrong; the conversation with the supervisor tells you what.

Shift-Level: When Are You Losing Hours?

The second shift is almost always worse than the first. The question is by how much, and why. Compare output-per-hour across shifts in the same department. A 10–15% gap is normal. A 25%+ gap is a signal — usually inadequate supervision, missing setup support, or material not being staged for the next shift by the previous one. The fix is rarely "work harder"; it's almost always upstream coordination.

Operator-Level: Who Needs What?

The most sensitive metric — handle carefully. Track output, quality (first-pass yield), and attendance per operator monthly. The point isn't ranking; it's matching. Low-output / high-quality operators are precision workers — assign them to tight-tolerance jobs. High-output / lower-quality operators are speed workers — assign them to volume runs with looser specs. Operators who score low on both need training or reassignment, not pressure.

The One Metric Most Factories Skip: Idle Time

Productivity ratios capture what people did. They miss what people couldn't do because something else was missing — a machine, a material, an instruction. Idle time per station, by reason, often reveals more about what's broken than any output number. Fix idle time first; output follows.

How to Act on What You Find

Department-level data drives capacity decisions. Shift-level data drives handover and supervision decisions. Operator-level data drives training and assignment decisions. Idle-time data drives process decisions. Confusing the levels — using operator data to make capacity decisions, or department data to manage individual performance — is how productivity programs become demoralizing without improving anything.

A Working Rhythm

Department numbers reviewed weekly with supervisors. Shift numbers reviewed monthly with shift leaders. Operator numbers reviewed quarterly, one-on-one, with the worker. Idle time reviewed daily by floor supervisors. That cadence — the right number at the right level at the right interval — is what turns productivity from a slide deck into a steering wheel.