Equal Pay for Unequal Output: Decision Tree

Why this matters

Two techs hold the same title, started around the same time, and are paid the same rate, but one of them consistently produces more, cleaner, faster, better-reviewed work than the other. Leave the pay identical and you are quietly telling your top performer that effort and skill do not matter here, and they will eventually take that lesson to a competitor who pays for it. Equalize pay upward for both and you may not be able to afford it. This is a design question you should answer before it becomes a resignation, not a live negotiation you improvise once your best tech is already frustrated.

Start here: confirm the output gap is real, not a perception

Before changing anyone's pay, verify the gap with actual data, not impression. Pull whatever you track: jobs completed, callback rate, customer satisfaction score, revenue generated, quality of documentation. A gap that only exists in your gut, with no data behind it, is not a basis for a pay decision, it is a basis for a conversation about what you should be measuring. If the data confirms a real, sustained gap, move to the next step. If it does not, the pay stays equal and the real work is figuring out why it felt unequal.

Branch 1: The role is genuinely identical, output differs by individual performance

If both techs hold the same title, same responsibilities, same customer type, and the difference is purely how well each one performs the same job, this is the core "equal pay for unequal output" case.

• Equal pay for equal roles does not mean equal pay regardless of performance. The title being the same does not obligate identical compensation if your pay structure includes a genuine performance component. The fix is not to abandon equal base pay, it is to make sure a real performance layer sits on top of it.
• If your current structure is pure flat hourly with no performance component, this gap is a structural gap, not a favoritism problem, and the fix is adding a performance-based layer (commission, bonus, or tiered rate tied to documented output) rather than making an ad hoc exception for one person.
• If a performance layer already exists and the gap persists anyway, check whether it is actually calibrated to catch a real difference this size. A performance bonus too small to matter is functionally the same as no performance pay at all, from the top performer's point of view.

Branch 2: The output gap reflects a real difference in scope, not just skill

Sometimes what looks like a performance gap is actually a scope gap wearing the same job title: one tech is quietly handling more complex jobs, carrying more responsibility, or covering for gaps the other does not. If so, this is not really "same role, different output," it is "different role, same title," and the fix is different.

• Formalize the scope difference with a real tier or title, so the pay difference is tied to a documented, stated set of added responsibilities rather than an invisible informal arrangement that only you can see.
• Confirm the lower-output tech knows the path exists. If the gap in scope is real and visible only to you, the lower-output tech has no way to close it, and the pay gap will read as arbitrary from their side even though it is not.

Branch 3: The gap is legitimate but the lower performer is otherwise solid and worth keeping

You do not need to treat every output gap as a problem to fix on the lower performer's end. A reliable, steady, lower-volume tech can be exactly what a shop needs for certain accounts or certain days, and their pay should reflect their actual contribution, not be pressured upward to match a different profile of performer just because the title matches.

• Be honest with the lower performer, kindly, if they ask about the gap. "Your work is solid and valued here. The pay difference reflects [specific documented output measure], and here's what closing it would look like if you want to pursue that." This treats them as a professional, not as someone being quietly punished.
• Do not manufacture an excuse to avoid the honest answer. A vague non-explanation is worse for morale than a direct one, because it invites the person to assume the worst reason (favoritism, bias) instead of the true, defensible one.

Step: Decide the path forward once the gap is confirmed and categorized

1. If the structure has no performance layer, build one, calibrated to actually move pay a meaningful amount for a meaningful gap in output.
2. If the gap is really a scope difference, name and document the scope tier so the pay difference is attached to a visible standard, not an invisible arrangement.
3. If the gap is legitimate performance and the structure already accounts for it correctly, the pay difference is doing its job. Communicate it honestly if asked, and do not equalize it just to avoid a conversation.
4. In every branch, write down the criteria the same way you would for any pay-band decision, so the next output gap does not require re-litigating the whole question from scratch.

Quick recap

1. Confirm the output gap with real data before touching anyone's pay.
2. If the role is genuinely identical and the gap is real performance, the fix is a calibrated performance layer, not forced pay equality.
3. If the "output gap" is actually a scope gap, formalize it as a real tier so it is visible and earnable, not invisible.
4. A legitimate, documented performance-based gap does not need to be equalized. It needs to be explained honestly if asked.

References

• U.S. Department of Labor, Wage and Hour Division, general wage-structure guidance
• Equal-pay principle: equal pay for substantially equal work, differences must be job-based and documented
• See related: The Pay Disparity Someone Found Out: Decision Tree
• See related: Documenting Your Pay Structure So It's Consistent and Defensible