Ask the owner of a 25-person warehouse how productive their pickers are and you'll usually get one of two answers. "Pretty good, I think." Or a long story about one person who's great and one who isn't.

Neither helps you staff next month or have a fair conversation with someone who's struggling. A simple labor standard does.

What a standard is

A labor standard is an expected rate for a task. Picking might be 60 lines an hour. Receiving might be 12 pallets an hour.

Large distribution centers use engineered standards. An industrial engineer breaks every task into motions, times each one and builds a target for every order from its exact travel and handling. It's accurate and expensive, and it usually needs labor management software to run.

At 10 to 40 people you don't need that. I've set up standards in warehouses of a dozen people with a spreadsheet and a few weeks of data. What you need is a reasonable number per task, built from your own history, that you check and adjust. Treat it as a baseline.

One unit per task

The hard part is choosing what to count. Pick a unit that tracks the effort and that your system already records.

  • Picking: order lines per hour. Units mislead, because grabbing 48 of one item takes about as long as grabbing one, and orders per hour is too coarse if order sizes vary.
  • Packing: orders per hour, or cartons if most orders ship in several boxes.
  • Receiving: pallets or line items per hour. Use lines if you get a lot of mixed pallets.
  • Put-away: locations per hour.

If a task varies wildly, like custom kitting, leave it out for now. Start with the work that repeats.

Getting the numbers

You probably have most of what you need already. Most ERPs timestamp pick confirmations, shipments and receipts with a user ID. Pull two to four weeks of it, and for each person and task, compare lines completed to hours on that task.

The hours are the tricky part. If people switch between picking and packing during a shift, ask them to jot down switch times on a sheet for those weeks. Rounding to the nearest 15 minutes is fine.

If your system doesn't record who did what, watch instead. Count the lines three or four people pick over a set hour, on a few different days. You aren't timing motions, just counting output.

Then line the rates up. Set aside the top and bottom performers and look at the middle of the group. That's your starting standard. The best person's rate sets most of the team up to fail, and an average of everyone drags in new hires and bad days. The middle is what a trained person does on a normal day in your building.

Adjust for harder work

A flat number feels unfair when the work isn't flat. Two adjustments cover most small warehouses.

Zone or product type. Picking small parts from shelving is faster per line than picking cases off pallet rack. If you have both, set a standard for each.

Order profile. A day of single-line e-commerce orders isn't a day of 40-line wholesale orders. If your mix swings, track standards by order type, or at least note what kind of day it was.

Stop there. Every adjustment makes the number harder to explain, and a number nobody understands won't get used.

Keeping it from hurting morale

This is what most owners worry about, and they're right to. Rolled out badly, a standard feels like surveillance. Rolled out well, it can make the floor feel fairer.

Tell people before you measure. The honest reason is usually something like "we need to know how many people to schedule, and we want to see where the process slows you down." Say that. If you collect data quietly and then announce targets, you'll spend months earning trust back.

For the first 60 days, use the standard to find problems in the work, not in the people. When someone's rate is low, ask what got in their way. You'll hear about missing labels, empty locations, a printer that jams, items stored in the wrong place. Fix those. In my experience the first round of fixes moves the team's rate more than any amount of pushing, and the team sees the numbers bringing help instead of blame.

Post the team's rate against the standard on a whiteboard each day. Talk about individual numbers one on one, in private. Public rankings push people toward speed at the cost of accuracy, and you pay for that in returns and reships.

Track accuracy right beside speed. A picker at 75 lines an hour with a 2 percent error rate isn't outperforming someone at 60 with almost no errors.

Revisit it

Standards drift. You change the layout, add a product line, or take on a customer with a different order profile. Look at the numbers every quarter and adjust when the work has changed.

If everyone beats the standard by a wide margin, that's good news, and it also means the standard is stale. If nobody can hit it, something in the work changed, and it's worth finding out what.

What it gets you

With a simple standard, next week's order forecast turns into a staffing number. A layout change shows up in real output instead of opinion. And a coaching conversation can start from something firmer than a gut feeling. It takes a few weeks of counting and an honest talk with your team, and then the habit of looking at the numbers.