A reward doesn’t just tell one person their behavior was fine. It tells everyone watching what actually gets tolerated, and people are watching closely. GCheck’s The Consequence Gap Report found that when a difficult coworker was rewarded rather than addressed, the people around them started copying that behavior at roughly two and a half times the rate seen when the organization actually acted.
Key Takeaways
- GCheck’s The Consequence Gap Report found that 36% of workers exposed to a rewarded, difficult coworker began adopting that coworker’s behavior themselves, compared with 14% when the coworker was removed.
- The same reward-status split shows up across every measure: workers were about twice as likely to say the experience changed them for the worse (42% vs. 20%) and to say they watched the behavior spread to others (58% vs. 27%).
- A promotion or bonus is a public signal, visible to an entire team. A conduct complaint is usually private, visible to almost no one. The signal nearly always wins.
- Workers who pick up a rewarded coworker’s behavior are overwhelmingly coping, not admiring: 94% cite a reason like stress, self-protection, or refusing to keep being taken advantage of.
- The fix isn’t a values poster. It’s checking whether specific performance-management mechanisms, bonus criteria, promotion committees, recognition programs, can be met by someone the rest of the team already knows is difficult to work with.
What the Data Shows
The Outcomes Split by Reward Status
Performance-management systems are usually built to answer one question well: did this person deliver. This article is about the question those same systems almost never ask, and what happens to everyone watching when nobody does.
| Outcome among exposed workers | Coworker rewarded or protected | Coworker removed |
| Began adopting the behavior | 36% | 14% |
| Changed for the worse | 42% | 20% |
| Saw it clearly spread to others | 58% | 27% |
| Came through unchanged | 28% | 55% |
Every row moves in the same direction, and none of the gaps are small. Adoption of the behavior runs roughly two and a half times higher when the organization rewards the coworker instead of addressing them. The share who say the exposure changed them for the worse roughly doubles. The share who came through completely unaffected falls by half. This isn’t one surprising number in an otherwise noisy dataset. It’s the same pattern, repeated across four different ways of measuring harm.
What “Reward” Actually Covers Here
GCheck’s research defines a rewarded outcome broadly: promoted, given a raise or bonus, publicly praised, or simply protected from any consequence while continuing to perform well. The common thread isn’t the specific mechanism. It’s that the organization did something, or conspicuously did nothing, that signaled the coworker’s standing was intact or improved despite the behavior everyone around them had already noticed.
This matters for how narrowly or broadly a company should read its own exposure to this pattern. An organization doesn’t need a formal bonus program or a promotion cycle to produce this effect. Simply leaving a difficult top performer in place, unaddressed, while their peers watch nothing happen quarter after quarter, functions as a reward in every way that matters to the data above. The absence of a consequence reads the same as the presence of one, to anyone trying to work out what the actual standard is.
That’s worth sitting with specifically because it means the fix can’t be scoped to formal compensation events alone. A company that carefully audits its bonus criteria and promotion committee but leaves an unaddressed conduct complaint sitting in someone’s inbox for eight months has not actually closed the gap this article describes. It has closed one visible channel while leaving the largest one, simple, ongoing inaction, wide open.
Why a Reward Is a Louder Signal Than a Complaint
A performance review, a promotion announcement, or a bonus isn’t a private event. It shows up in a shared calendar, a team-wide email, a compensation band everyone eventually hears about, or simply the visible fact that someone difficult is still there, still senior, still getting the good projects. A conduct complaint runs the opposite path: filed privately, investigated privately, resolved (or not) with no announcement either way. Even coworkers who filed the complaint themselves often never learn what happened to it.
That asymmetry means a team can be highly confident about what got rewarded and almost entirely uncertain about what got addressed. When those two signals conflict, when the same person who’s been difficult all year is also the one getting promoted, there’s no real contest about which message lands. The promotion is a fact everyone can see. The correction, if it happened at all, is a rumor at best.
This is also why “we handled it quietly” is close to the worst possible response to a conduct problem in a valuable performer. Quiet handling might be appropriate for confidentiality reasons, but it guarantees the only visible signal the team receives is the reward, since the correction, by design, stays invisible. A team watching a difficult coworker get rewarded with no visible counterbalance isn’t failing to notice the correction. There usually isn’t one to notice.
This Isn’t About Admiration
Coping, Not Copying to Get Ahead
It would be easy to read “people start copying the rewarded coworker” as a story about ambition, that workers are chasing the same reward by mimicking the same behavior. The data says the opposite. Among workers who admit adopting a rewarded coworker’s behavior, 94% cite at least one coping motive: coping with stress, protecting themselves, or refusing to keep being the one who absorbs the cost while someone else gets away with it. Competitive motives, copying the behavior specifically to get ahead, barely register.
That distinction matters for how this pattern gets discussed internally. Framing it as “people are learning to be difficult to get promoted too” blames the wrong party and misses the actual mechanism. The more accurate frame is closer to a rational adaptation: if the standard a team can observe is “difficult but valuable gets protected,” some portion of that team will, consciously or not, decide that being valuable enough to be protected is a safer strategy than continuing to absorb the cost of someone else’s unaddressed behavior.
A Third Isn’t a Small Number
Worth stating plainly, since it’s easy to lose in a discussion of aggregate percentages: most exposed workers don’t adopt the behavior at all, even when it was rewarded. Roughly two-thirds came through changed for the worse or unaffected rather than becoming a copy of the person who caused the problem. The finding here isn’t that reward guarantees contagion. It’s that reward measurably raises the odds, in a way an organization can actually see and act on, rather than leaving it as an unmeasured cultural assumption.
That said, “most people don’t adopt it” is a low bar to feel reassured by. A workplace where roughly a third of the people closest to a rewarded, difficult coworker start behaving more like them isn’t a workplace with a contained problem. It’s a workplace where the contagion rate would be treated as an emergency in almost any other context, a product defect, a safety incident, a compliance failure, if the number involved anything other than something as hard to quantify as “how people treat each other.”
Which Performance-Management Mechanisms Carry the Signal
Three Places the Signal Travels
The reward that trains the rest of a team rarely arrives through one obvious channel. It usually travels through the ordinary mechanics of performance management, which makes it easy to miss until the pattern is named directly:
- Bonus and compensation criteria that are purely output-based. If a bonus formula has no conduct component at all, it cannot distinguish between someone who hit their number cleanly and someone who hit it while making three coworkers’ jobs harder. The formula itself is silent on the question, which is functionally the same as answering it doesn’t matter.
- Promotion committees that review output but not peer feedback. A promotion packet built from a manager’s assessment and a metrics dashboard can clear every bar without a single input from the people who actually work alongside the candidate day to day, the population most likely to know about a conduct problem in the first place.
- Recognition programs that spotlight results publicly with no corresponding visibility into conduct. An “employee of the month” post, a shoutout in an all-hands, a leaderboard, these are designed to be seen by everyone, which is exactly why they carry so much signal when the person featured is also someone the team has quietly stopped trusting.
Peer feedback is the common thread missing from all three. A metrics dashboard has no way to register red flags about how someone treats their team, because it was never built to ask that question in the first place. The people closest to the work are the only ones who reliably see them.
Why Naming the Channel Matters
None of these mechanisms is badly designed for its original purpose. A bonus formula tied to output is a reasonable way to reward output. The problem is narrower and more specific: none of them were built with a conduct check anywhere in the process, so none of them can fail to reward difficult behavior, because none of them were ever asked to evaluate it in the first place.
That’s a useful reframe for anyone who feels defensive on behalf of their own performance-management system when they first hear this argument. Naming the gap isn’t an accusation that the system was designed carelessly. Most reward mechanisms were built at a point when conduct and output weren’t in tension for the people involved, and they simply never got revisited once that stopped being true. The fix, correspondingly, isn’t a redesign from scratch. It’s adding the one check the system was never asked to run.
Naming which specific mechanism is carrying the signal also does something else useful: it turns an abstract culture problem into a concrete, ownable fix. “Fix the culture” is not a task anyone can complete on a Tuesday. “Add a conduct field to the Q3 bonus calculation” is.
Decoupling Output From Conduct Tolerance
The Fix Is Structural, Not Cultural
A values statement doesn’t change what a bonus formula, a promotion packet, or a recognition program actually measures. Three specific changes address the mechanisms directly:
- Add a conduct gate to every reward mechanism that currently has none. This doesn’t require a complex rubric. A simple, binary check, no active or unresolved conduct concern, reviewed independently of the performance number, at the point a bonus, promotion, or public recognition is finalized, closes the gap in most of these systems without redesigning them from scratch.
- Route peer feedback into promotion decisions as a required input, not an optional one. If a promotion can clear a committee without any input from the candidate’s actual peers, the committee is structurally blind to exactly the population most likely to know about a conduct pattern. Requiring that input, and requiring the committee to address it rather than simply file it, closes that blind spot directly.
- Make the correction as visible as the reward, wherever confidentiality allows. This doesn’t mean publicizing a personnel matter. It means, at minimum, that a manager who addresses a conduct problem should say so to the team in whatever general terms are appropriate, rather than leaving the reward as the only visible data point. A team that never hears about a correction will act as though one never happened, because as far as they can tell, it didn’t.
Worth being clear about what this fix is and isn’t. A background check does real, necessary work at the point someone is hired, confirming who they are and what’s on record. It was never going to be the tool that surfaces a conduct pattern that develops on the job and gets rewarded years later, because that isn’t the question a background check is built to answer. The conduct gate described here picks up exactly where hiring-stage screening leaves off, inside the performance-management system, not outside it.
What This Doesn’t Require
This isn’t an argument for punishing high performers or treating strong output with suspicion. A gate that only ever asks “is there an active, unresolved conduct concern” doesn’t slow down or complicate a clean promotion in the slightest; it only ever engages when there’s something for it to flag. The goal isn’t to make rewards harder to earn. It’s to make sure a reward can’t happen by accident, silently teaching an entire team what a values statement already claims isn’t true.
It’s also not a claim that every talented, demanding employee is one bad quarter away from becoming this article’s subject. Plenty of high performers are exacting, blunt, and occasionally hard to work with in ways that never rise to a documented, repeated pattern of harm. The conduct gate proposed here is deliberately narrow, an active, unresolved concern, not a vague vibe check, precisely so it never becomes a tool for penalizing directness or high standards. A gate built to flag a real pattern and a culture that punishes bluntness are two different systems, and conflating them would undermine the argument this article is making, not support it.
What This Costs Beyond the Copying Itself
The People Who Don’t Copy Still Leave
Adoption is only one half of what the reward-status data shows. The same research found that where a difficult coworker was rewarded rather than addressed, exposed workers left the job before that coworker did at roughly four times the rate seen when the organization actually acted. Some of the people who don’t adopt the behavior leave instead, which means a reward mechanism with no conduct check doesn’t just risk teaching people the wrong lesson. It risks losing the people who refused to learn it, while keeping the person the lesson was about.
That’s a specific, avoidable version of a familiar problem: the exit interview that blames “culture fit” or “wanted a new challenge” almost never names the actual reason, because the departing employee has usually already concluded that naming it won’t change anything. A company that only tracks why people say they’re leaving, rather than what they watched happen to a rewarded coworker beforehand, will keep missing the connection between the two.
The two costs compound each other in a way that’s easy to miss looking at either one alone. The people who adopt the behavior stay and spread it further. The people who don’t adopt it often leave, taking their institutional knowledge with them, which means the team that remains skews, over time, toward people who either learned to tolerate the behavior or learned to imitate it. Neither outcome improves the situation the reward was supposed to be silent about in the first place.
What This Means for Compliance
Transparent by Design, Fair by Application
Everything in this article is really one argument about Transparent Compliance: a performance-management system communicates its real standard whether or not anyone intended it to, and the honest fix is making that communication deliberate rather than leaving it to accident. A reward mechanism with a conduct check says, clearly and in advance, that conduct is part of what’s being evaluated. One without a check says the opposite, just as clearly, without anyone having to write it down.
Fair Compliance is the natural second half. A conduct gate only earns its keep if it applies the same way regardless of how much revenue, code, or output the person in question produces. A gate that quietly gets waived for the team’s best performer isn’t a gate. It’s the exact problem this article describes, just moved one step further into the process instead of solved by it.
Held together, the two pillars describe a single, testable standard: does this organization’s reward system say the same thing about conduct, out loud, that its values statement already claims. If the honest answer is that the reward system has never actually been asked the question, that’s the starting point, not a reason to conclude the culture is fine.
Frequently Asked Questions
Why do companies reward toxic employees instead of addressing their behavior?
Often because the reward, a promotion, a bonus, public recognition, moves through a performance-management process with no conduct check built into it, while a conduct complaint moves through a separate, usually private, process. The two rarely intersect, so a coworker can clear every bar in the reward process without the process ever having a chance to weigh their conduct.
Does rewarding a toxic employee actually cause other people to copy them?
Research on this pattern found that among workers exposed to a difficult coworker, 36% began adopting that coworker’s behavior themselves when the coworker was rewarded, compared with 14% when the coworker was removed, roughly two and a half times higher. The same gap shows up across multiple measures of harm, not just one.
Are people who copy a rewarded coworker’s behavior just trying to get ahead the same way?
Usually not. Among workers who admit adopting the behavior, 94% cite a coping motive, handling stress, protecting themselves, or refusing to keep absorbing the cost while someone else gets away with it, rather than a competitive motive. It reads more like a rational adaptation to an observed standard than an attempt to copy a strategy for success.
How can a company stop a reward system from accidentally signaling that toxic behavior is fine?
Add a simple conduct check to any bonus, promotion, or recognition process that currently has none, require peer feedback as part of promotion decisions rather than leaving it optional, and make corrections as visible as rewards wherever confidentiality allows, so a reward isn’t the only signal a team ever sees.
Does fixing this mean performance should matter less?
No. A conduct gate that only engages when there’s an active, unresolved concern doesn’t slow down a clean promotion or bonus at all. The goal isn’t to weaken performance-based rewards; it’s to make sure they can’t be granted by accident to someone; the reward system was never built to evaluate conduct in the first place.
ABOUT THE CREATOR
Charm Paz, CHRP
Recruiter & Editor
Charm Paz is an HR professional at GCheck, specializing in background screening, fair hiring, and regulatory compliance. She holds from the Professional Background Screening Association (PBSA) and helps organizations navigate employment regulations with clarity and confidence.
With a background in Industrial and Organizational Psychology, she translates policy into practice to build ethical, compliant, human-centered hiring systems that strengthen decision-making over time.
