Paying for Performance Without Gaming It
Why this matters
Pay-for-performance is supposed to reward your best people and push the rest to step up. Done wrong, it does the opposite: it rewards corner-cutting, breeds callbacks, and teaches your crew to chase the number instead of doing right by the customer. The trades are full of incentive plans that blew up because the owner measured the easy thing instead of the right thing. Get the design wrong and you pay more money for worse work.
The core problem: you get what you measure
Whatever you put money behind, people will optimize for it, including the parts you did not think through. Pay only on revenue per ticket and you will get oversold customers and quoted repairs they did not need. Pay only on jobs closed per day and you will get rushed work and callbacks. Pay only on speed and quality drops. This is not because your techs are dishonest. It is because incentives are gravity, and people slide downhill toward the reward.
The fix is not to abandon performance pay. The fix is to measure a balanced set of things, so that gaming one metric tanks another.
Build a balanced scorecard, not a single lever
Tie pay to two or three metrics that pull against each other, so no single shortcut wins.
| Metric | What it rewards | What it can corrupt if used alone |
|---|---|---|
| Revenue or billable hours | Productivity, upselling real value | Overselling, padding, unneeded work |
| Callback / rework rate | Doing it right the first time | Slowness, over-engineering |
| Customer satisfaction score | Treating people well | Buying ratings, avoiding hard jobs |
| Membership or maintenance-plan signups | Recurring relationships | Pressure-selling reluctant customers |
A tech who games revenue will see their callback rate spike and their pay take the hit. A tech who games speed will see satisfaction fall. The metrics police each other.
Quality gates are non-negotiable
Before any performance bonus pays out, it should pass a quality floor. If a tech's callback rate is above your threshold, the productivity bonus is reduced or zeroed for that period, no matter how much they billed. This single rule prevents the most damaging failure mode: paying a fast tech for work you have to send someone back to fix.
State the gate up front. "You earn the productivity share only when your callback rate stays under the line." Now speed and quality are linked in their head, the way they should be.
Spiffs versus structural pay
Know the difference between a spiff and your base structure.
- A spiff is a short, targeted bonus to push one behavior right now. "Extra pay for every duct cleaning booked this month." Use spiffs for short campaigns, not as the backbone of someone's income.
- Structural performance pay is the ongoing formula that determines real take-home. This needs to be stable, understandable, and fair, because people make life decisions around it.
The danger with spiffs is they teach the crew to ignore anything you are not currently paying a spiff on. Use them sparingly and rotate what you reward so no single area gets starved.
Make it simple enough to explain on a napkin
If a tech cannot calculate roughly what they will earn, the plan does not motivate, it just confuses and breeds suspicion that you are hiding the ball. A plan with seven tiers and four multipliers fails because nobody trusts what they cannot follow.
Aim for a formula a tech can do in their head on the drive home. The simpler it is, the more it changes behavior, because they can see the connection between the choice in front of them and the money in their pocket.
Protect the base
Performance pay rides on top of a fair base wage, it does not replace it. A plan where someone's rent depends on hitting an aggressive number creates desperation, and desperate people cut corners and burn out. Pay enough base that a decent month is comfortable and a great month is excellent. The incentive should feel like a reward for winning, not a threat of losing.
This also protects you legally. Pay structures intersect with minimum wage, overtime, and worker-classification rules that vary by state and change over time. Before you roll out a new commission or piece-rate plan, run it past an employment attorney or your state labor office. Keep this article's guidance general and confirm the specifics for your location.
Review and adjust openly
No incentive plan is right forever. The market shifts, the work mix changes, and people find the seams. Review the plan once or twice a year. When you change it, explain why in plain terms and give notice. Quietly moving the goalposts is how you lose trust and your best techs at the same time.
References
- U.S. Small Business Administration (SBA), guidance on employee compensation
- U.S. Department of Labor, Wage and Hour Division, overtime and pay-structure rules
- Society for Human Resource Management (SHRM), incentive and pay-for-performance design
- See related: The Tech Who Wants a Raise: Decision Tree