Lessons from the Floor: How Do You Incentivize When There Is No Incentive?

Every operation that installs engineered standards eventually has the same conversation. It usually starts with a high performer holding a printout of their own numbers.

For most of my career, especially once labor management systems and engineered standards became standard tools, the incentive question crept up from the floor on a schedule you could set your watch by. The feeling was fair and plainly stated: I'm being held accountable to a number now — shouldn't I make more money when I beat it? The high performers would look at their performance scores and ask why the person running at 85% took home the same paycheck. A valid point. I never had a good answer for it, and I ran those buildings.

What happened next was just as predictable. The CFO wanted to understand the cost. HR wanted to understand how it would be fair. Legal wanted to understand the exposure. And before long, the plan died on the vine — not because anyone killed it, but because nobody could carry it across three departments at once.

Here's what makes the question genuinely hard, and it starts with being honest about where the productivity gains actually come from. The industry numbers credit labor programs with big lifts — engineered standards typically boost productivity 15 to 35 percent, and most operations implementing a labor management system see 15 to 30 percent improvement in the first year. But read those numbers carefully: that gain comes from the standards and the tracking, before a dollar of incentive is paid. Measurement itself does the heavy lifting. The incentive layer on top is worth something real — in my experience roughly 6 to 12 percent of additional lift, and even the firms selling these programs put the incremental gain around 15 percent — but it's the second lift, not the first. So the CFO's question isn't "does pay-for-performance work?" The standards already banked the big win. The real question is narrower: is another 6 to 12 percent worth the payout, the administration, and the ways the plan can go wrong?

And here's the trap nobody warns you about: the sequencing kills the incentive almost every time. You'd never roll out standards and an incentive plan together — the standards rollout is difficult and high-risk enough on its own, and if you get the standards wrong with pay already attached to them, you've turned an engineering correction into a labor dispute. So the incentive waits. But by the time the standards are in and stable, the operation has already banked the big gain — and now the incentive plan has to justify its cost against the modest lift that's left. In my career, it never cleared that bar. Not once. The plan doesn't die because someone kills it. It dies because the only safe time to launch it is after its best justification is gone.

And when plans do launch, they can go wrong in ways you can predict before day one. I know companies that implemented individual pay-for-performance and got mixed results at best. Teamwork broke down as individuals skipped difficult orders for what we called gravy orders — high volume, little effort. Finger-pointing over who did what. Arguments at the end of every shift. The research says the same thing in drier language: incentives that reward quantity alone typically boost quantity alone, and quality pays the bill. Reward the pick rate and watch the accuracy slide. None of this is bad luck. It's design.

Where we landed, after watching the individual plans eat themselves, was the building. A collective goal — one team, one scoreboard, clear parameters — with tiered rewards at different achievement levels rather than all-or-nothing. Tiers matter more than they look: an all-or-nothing target that slips out of reach in November stops motivating anyone in December. The research backs the design choices too — pair quality gates and safety thresholds alongside the productivity number so the plan can't be gamed into a mess, and get the reward close in time to the performance. A bonus paid ninety days later buys you nothing on the floor tonight. The honest trade-off: building-level plans carry their own known weakness — the free rider who coasts on the team's effort. You manage that with visibility and supervision, not by abandoning the plan. Every incentive structure has a failure mode; you're choosing which one you can manage.

Which leaves the high performer with the printout, because the building-level plan still doesn't fully answer them. What I learned is that it comes down to meaningful and timely recognition — genuine, specific,