It was 6:40 in the morning and I had barely walked through the warehouse door when Old Wang from the picking team blocked my office doorway, waving a printed LMS report.
"Chen, explain this to me. Yesterday I was at 112 percent. Today I'm at 87. I didn't work less. I didn't pick fewer orders."
One look told me the story. Yesterday's orders were small items in tight locations. Today's were all big, heavy stuff parked in the farthest aisle. The LMS warehouse standard time had done its math. It just didn't know Wang had walked two extra kilometers today.
Here's the honest truth: with an LMS, whether it helps or hurts comes down to one thing — whether your engineered labor standards are fair. Get the ruler wrong, and the harder you manage, the messier the floor gets.
What an LMS Warehouse Standard Is Actually Made Of
Let's get the concept straight first. An engineered standard is the time a trained worker, using the standard method, should need for a task at a sustainable pace. It is not a number someone guessed in a meeting. It is not last month's average dressed up as a target.
In practice a standard is built from four pieces. First, the observed base time — what the stopwatch actually measured. Second, a performance rating, where the engineer adjusts the observed pace back to a "normal" pace. Fast doesn't mean standard. Third, the PFD allowance — personal needs, fatigue, and unavoidable delays — which in industry practice usually runs around 12 to 15 percent, higher for freezer work or heavy cases. Fourth, travel time, calculated from distance divided by walking speed. Farther location, longer standard time.
The formula is one line: standard time = observed time x rating factor x (1 + PFD allowance) + travel time.
If you want the full picture of how a labor management system fits together, the LMS warehouse labor management system overview lays out the system side. This piece is about the floor side: how a standard is born, and how it gets challenged.
And here is the counterintuitive part up front: a standard set too loose hurts more than one set too tight. A tight standard gets complaints, but people grit their teeth and work. A loose standard teaches your fast workers that extra effort buys nothing and your slow workers that coasting is fine. Three months later the whole shift's rhythm has collapsed. A loose standard doesn't buy harmony. It punishes your best people until they quit.
How to Run a Time Study Without Getting Hated
In the fall of 2024, when we rolled out our LMS, the vendor sent an industrial engineer to run time studies. On day one he made a classic mistake: he studied only our fastest picker, Xiao Li. The numbers looked beautiful. Management loved them. At that rate, we'd ship a dozen more orders per hour.
Complaints exploded in the first week of go-live. Veterans said the standard was built for a superhero. New hires cried on the floor. Our turnover that month more than doubled.
We fixed it with three rules that are now written into our operating manual.
First, pick the right people to study. Only workers who are fully trained and at least a month on the job. Study three of them and take the middle value — never the fastest, never the slowest. Studying a new hire means turning the learning curve into a standard, and that is just bullying.
Second, lock the method before you measure. For the same pick, one person scans first then grabs, another grabs first then scans. Different sequence, up to 20 percent difference in time. If the method isn't standardized first, you are measuring personal habits, not a standard.
Third, tell the team before you show up with a stopwatch. A worker with an engineer staring at them gets nervous, hands shake, pace goes weird. Our rule now: announce it a day ahead. Say clearly that we are measuring the process, not the person, and that once the standard is set, everyone gets measured by the same ruler.
The hardest part of a time study is trust. Once workers believe the ruler exists to punish them, nothing you say afterward gets heard.
How Fast Is Too Fast for an LMS Warehouse Standard
There are reference ranges out there. Manual picking in a well-run warehouse typically lands around 80 to 120 picks per hour, according to published industry benchmarks. But that's a range, not a target. Your number depends on item size, location density, and order profile.
Our approach now is tiered standards, not one flat number. Every pick task gets scored on three things: travel distance, item weight, and lines per order. Cross those three and tasks fall into fast, medium, and slow tiers, each with its own standard time. When the LMS assigns work, it scores by tier, so a worker's performance percentage is comparable whether they spent the day on fast picks or slow ones.
Here's a worked example — clearly labeled as a hypothetical illustration, not our real data. Suppose a pick task has an observed base time of 25 seconds, a rating factor of 1.0, a PFD allowance of 13 percent, and 8 seconds of travel. Standard time = 25 x 1.0 x 1.13 + 8 = 36.25 seconds, roughly 99 picks per hour. Move the same task to the farthest aisle and travel becomes 20 seconds: standard time rises to 48.25 seconds, roughly 75 per hour. Same ruler, different number. Workers don't argue with the number. They argue with whether the reasoning behind it is fair.
We've tried the main methods for setting standards. Each has its place:
| Method | How it works | Strength | The catch |
|---|---|---|---|
| Stopwatch time study | Engineer measures on the floor | Closest to your actual operation | Labor-intensive, and it starts going stale the day it's done |
| MOST predetermined times | Standard motion tables assembled into tasks | Works before the operation even exists | The motion library may not match your real process |
| WMS data mining | Reverse-engineer standards from system scan history | Huge sample size, no stopwatch needed | Only validates what already happens, not whether the method is right |
| Historical averages | Last month's per-person average | Fastest and easiest | Bakes your inefficiency into the standard |
Our combination: use MOST for a first draft before a new process launches, validate against WMS data after a month of running, and send an engineer for spot re-studies where the variance is large. No single method survives on its own.
What to Do When Workers Challenge an LMS Warehouse Standard
Standards will get challenged. A standard nobody challenges is either too loose or everyone has given up arguing.
Last winter, a night-shift lead came to me about the freezer picking standard. Winter gear slows you down, he said, and hands go stiff after long stretches in the cold. The allowance should be wider. My first instinct was to say "stop making excuses." I swallowed it.
We run a fixed appeal process. Step one, the worker or lead submits it in writing: which task, which standard, exactly what's wrong. Step two, we re-study within a week, and the person who appealed watches the engineer do the measuring. Step three, whatever the result — changed or not — we post it to the whole team, with the reasons written out.
That re-study moved the PFD allowance from 13 to 18 percent, widening standard time by about 5 percent. A small change, but the effect was outsized: turnover in that group dropped over the next three months, and the performance pass rate went up. People believed the ruler was alive and that making a reasoned case actually worked.
Sometimes appeals get rejected, and that matters too. One worker said the putaway standard was too tight. The re-study found he was skipping the scan-confirmation step — the time he "saved" was his own shortcut, not a problem with the standard. The rejection reasons get posted as well, or people assume the appeal process is theater.
Here's what I tell every new supervisor: a standard is a management tool, not a punishment weapon. When the LMS spits out a daily percentage, the first question is "did the conditions behind this number change," and only then "does this person have a problem." Get the order backward and nobody on the floor will trust you.
Our standards get reviewed every quarter, and the triggers are: major slotting change, product mix shift, equipment change, or two straight weeks where the pass rate drops below 80 percent or climbs above 110 percent. Any trigger fires a re-study. A ruler you don't recalibrate starts drifting within three months. Keep the ruler honest, and the team stays steady.
By Chen Feng, Warehouse Operations Manager







