The Danger of Pay That Rewards Volume Over Craftsmanship

Why this matters

A pay plan that only counts jobs closed, tickets billed, or hours turned is a plan that quietly tells your best techs to slow down and think less. Volume-only pay does not announce itself as a problem. It shows up months later as a rising callback rate, a tech who used to double-check now guessing, and a customer who says "the last guy just wanted to get out of here." By the time the damage is visible in your numbers, it has already cost you the reputation. Understanding exactly how volume pay corrodes craft is the first step to designing a plan that does not.

What "volume over craftsmanship" actually looks like

It rarely looks like laziness. It looks like a competent tech making a series of small, individually defensible shortcuts that add up to worse outcomes:

• Skipping the five-minute diagnostic step that would have caught the real cause, because a callback three weeks from now does not cost them anything today and a faster close does.
• Reaching for the part that is in the truck instead of the part that is correct, to avoid a supply-house trip that eats into billable time.
• Quoting the fix that gets a signature fastest rather than the fix that lasts, because a fast close counts the same as a thorough one on the pay stub.
• Under-explaining the work to the customer, because a five-minute walkthrough is five minutes not spent on the next ticket.

None of these show up as a rule violation. Each one is a rational response to a pay signal that says: speed and count are what get counted, everything else is invisible.

Why the incentive is stronger than the tech's character

This is not a story about dishonest people. It is a story about incentives being gravity. A tech who is paid the same whether the job takes forty minutes done right or twenty-five minutes done fast will, over enough repetitions, drift toward twenty-five minutes, because the pay plan told them that was the goal. A tech paid per unit closed with no quality counterweight will start seeing every job as a unit to close rather than a problem to solve. Your best people are not immune to this. In fact they often feel the pull hardest, because they are the ones fast enough to hit high volume and still look competent doing it.

The signals that tell you it is already happening

Watch for these together, not in isolation, since any one alone can have another cause:

• Callback rate climbing on techs whose ticket count is also climbing, especially if the climb tracks a specific tech more than the crew average.
• Diagnostic time trending down on jobs that should take roughly the same time regardless of who is on them.
• Customer comments that mention rushing ("he was in and out," "didn't really explain anything") even when the fix technically held.
• Parts returns or wrong-part-installed incidents rising, a sign someone grabbed what was on hand instead of confirming the right component.
• Senior techs starting to behave like rookies, cutting corners they used to catch, which tells you the plan changed their behavior, not their skill.

The fix is not "pay less for volume," it is "pay for more than volume"

The answer is never to strip out productivity pay entirely. A shop that pays flat regardless of output gets the opposite problem: slow, unmotivated work. The fix is to make sure volume never wins alone. Put a real cost on the shortcut, in the pay math itself, not just in a talking-to after the fact.

• Tie a callback or rework penalty to the productivity bonus, so a fast tech whose callback rate exceeds your threshold loses part or all of the volume bonus for that period. Now speed without quality actually costs money instead of only risking a conversation.
• Weight a quality signal alongside a volume signal, such as customer satisfaction score or a documented diagnostic step, so gaming one does not maximize pay.
• Make the quality gate simple and visible up front, stated as a plain rule the tech can calculate themselves: "the productivity bonus pays only when your callback rate stays under the line this period." A gate discovered after the fact reads as a punishment. A gate stated in advance reads as the rule of the game.

The mental model to keep

Whatever you pay for, you get more of, including the version of it you did not intend. A pay plan that only measures output is not neutral, it is actively teaching your crew that thoroughness is optional. Design pay so that cutting corners costs more than it saves, and craftsmanship becomes the profitable choice instead of the sacrificed one.

References

• Society for Human Resource Management (SHRM), incentive and pay-for-performance design guidance
• U.S. Department of Labor, Wage and Hour Division, general pay-structure guidance
• See related: Paying for Performance Without Gaming It
• See related: Documenting Your Pay Structure So It's Consistent and Defensible