The Manager’s Highest Performer Keeps Raising Concerns About a Colleague’s Conduct. Not Formal Complaints — Just Repeated Mentions That Make Every Interaction Feel Complicated. The Manager Has Started Routing the Best Leads and Stretch Assignments to Other Team Members. He Doesn’t Think of It as Retaliation. She Does.

Quick Answer

Can a manager’s pattern of routing stretch assignments and high-visibility opportunities away from an employee who has been raising compliance concerns constitute retaliation — even when the manager has no conscious intent to retaliate?

Yes. Retaliation under most employment law frameworks and compliance policy definitions does not require conscious retaliatory intent. It requires that a protected activity — raising compliance concerns — contributed to an adverse employment action. Systematically removing a high performer from high-visibility opportunities, the best client assignments, and stretch roles is an adverse employment action regardless of whether the manager characterized it to themselves as “managing team dynamics” or “working with people who don’t create friction.” The test is the effect on the employee’s career trajectory relative to what it would have been without the protected activity — not whether the manager had a malicious motive.

Pressure Type: Unconscious Avoidance / Opportunity Denial Retaliation

This is the subtlest form of retaliation in the leadership pressure taxonomy — not a formal adverse action, not a documented performance change, but a gradual redirection of career-building opportunities away from an employee whose protected activity has made them feel like a management complication. The manager doesn’t think “I’m retaliating.” He thinks “she’s high maintenance and I work better with people who don’t create friction.” But the effect on her career — and the legal and compliance characterization of what’s happening — is identical to conscious retaliation. This type of pressure is important to train for specifically because it is invisible to the manager but entirely visible to the employee.

The Manager’s Moment — The Assignment Meeting

Sales manager Robert Kim has a team of eight. His highest performer — Maya Chen — has been with the company for three years and has consistently produced the best numbers on the team. She has also, over the past six months, been raising informal concerns about a colleague’s sales practices: double-booking leads, inflating pipeline numbers, and claiming credit for team deals. Not formal HR complaints — just repeated mentions in 1:1s that have put Robert in an uncomfortable position.

Robert hasn’t done anything about the colleague’s practices. He’s uncertain whether they rise to the level of formal action, and he finds the conversation with Maya draining every time she brings it up. He’s started noticing that when he assigns the top strategic accounts or the high-visibility sales presentations, he’s routing them to other team members. When a leadership rotation opportunity came up last month, he submitted two other names. He tells himself Maya doesn’t need the extra exposure — she’s already the top performer. In truth, he just finds it easier to work with colleagues who aren’t creating friction.

He has never connected the assignment pattern to Maya’s concern-raising. He thinks of them as entirely separate.

Maya’s Moment — Noticing the Pattern

Maya has been with the team long enough to know who gets the top accounts and why. She’s watched the strategic account assignments for six months. Three times running, accounts she would have received based on her performance and tenure went to colleagues with lower performance scores. The leadership rotation she expected to be considered for went to someone with two years less experience. Robert’s manner with her in 1:1s has become slightly more formal — less candid than it used to be.

She knows when this started. It started when she began raising concerns about her colleague. She can’t prove a causal connection — Robert has never said anything explicitly. But the pattern is clear, and the timing is not coincidental. She has told two close colleagues on the team what she’s observed. They’ve both noticed it too.

She is deciding whether to escalate formally, raise it with Robert directly, or say nothing and start looking for another job.

Choice ASay nothing and start job hunting. Raising a retaliation concern will make the relationship with Robert even more difficult, put her in an adversarial position, and probably accelerate the assignment marginalization. The safest exit is a new employer.

Choice BFile a formal retaliation concern with HR — documenting the timeline: the concerns raised about her colleague, the date the assignment pattern shifted, the three specific accounts she expected to receive based on performance and didn’t, and the leadership rotation. Request that the matter be investigated. Preserve her own record of the concerns she raised and the timeline of the assignment changes.

Choice CRaise it with Robert directly — name the pattern she’s observed specifically, note the timing relative to her concern-raising, and ask directly whether there’s a connection. Give Robert the chance to recognize and correct the behavior before it becomes a formal complaint.

Choice AContinued assigning as he has been doing. Maya doesn’t need the extra exposure — she’s already the top performer. His assignment decisions are based on team development needs and client fit, not on Maya’s 1:1 conversations. The two things are entirely unconnected.

Choice BWhen he noticed himself gravitating away from assigning Maya to high-visibility opportunities, examined why — specifically asking himself whether Maya’s concern-raising was influencing his assignment decisions — and disclosed that question to HR. Even if he believed the two were unconnected, the combination of protected activity and changed assignment pattern warrants a documented HR review before the pattern develops further.

Choice CAddressed Maya’s underlying concerns about the colleague formally — either by investigating them or escalating them to HR — so that the unresolved tension created by her concern-raising didn’t continue to accumulate in the team dynamic and in his management of her.

The Right Calls

For Maya: Choice B — formal HR documentation. Choice C may precede it, but B is required, given the pattern’s duration.

Choice A is the chilling effect succeeding, with the organization losing its top performer, while the colleague whose practices she raised remains undisturbed. Choice C is a reasonable first step if the pattern has just begun — giving Robert an opportunity to recognize and correct the behavior before formalization. But six months of a consistent pattern is beyond the range where an informal conversation is the right first response. The pattern needs to be formally documented because it describes an ongoing adverse employment action. Maya’s documentation also protects her: if she escalates the original colleague concern, which she should, the documented retaliation pattern becomes relevant to the full picture of what her concern-raising has cost her.

For Robert: Choice B — self-examine the assignment pattern and disclose to HR before it compounds. Choice C addresses the root cause.

Choice A is the rationalization that allows unconscious retaliation to persist indefinitely — “the assignment decisions are unconnected” is a conclusion Robert reached without examining whether that was true. Choice B requires him to ask himself a question he hasn’t asked: Am I making different assignment decisions about Maya because she’s been raising concerns that complicate my management life? That question is uncomfortable precisely because the honest answer may not be fully “no.” Asking HR to examine the pattern before it develops further is the action that protects both Maya and Robert from a situation that has been trending toward a formal complaint for the past 6 months. Choice C — addressing the underlying colleague issue — would have prevented much of this from developing if it had happened when Maya first raised the concern.

The assignment pattern is visible from outside the manager’s head and invisible from inside it.

Robert makes each individual assignment decision based on a reasoning that seems legitimate in isolation: this account is better suited to someone else’s industry background; this rotation is a better development experience for someone who hasn’t had the exposure yet; this presentation needs a fresh voice. Each reason is plausible. The pattern across all of them — that they consistently route away from the person who has been raising uncomfortable concerns — is only visible when the full set is examined together. Maya can see the full set. Robert, making each decision individually in the moment, cannot see the pattern he’s creating unless he deliberately looks for it.

Unresolved concern-raising creates management friction that produces retaliation without any retaliatory decision.

Maya keeps raising the colleague’s concern because nothing is being done about it. Robert keeps finding the 1:1s draining because he isn’t addressing the concern, and the conversation keeps recurring. The friction compounds on itself, and it compounds specifically against Maya because she’s the source of the friction in Robert’s experience, even though the source is actually his own failure to address the underlying concern. If Robert had investigated or escalated the colleague issue when Maya first raised it, the recurring tension that has shaped his management of her for six months would never have developed.

The high performer leaving is the worst possible outcome for everyone, including the team’s reporting culture.

Two colleagues have already noticed the pattern. When Maya leaves — which Choice A makes inevitable — those two colleagues will update their understanding of what happens to people who raise compliance concerns on this team. The informal reporting culture is being shaped right now not by a policy but by an observable pattern that neither managers nor the compliance program is currently addressing. The best performer on the team is becoming an involuntary departure following concern-raising, which is a visible event in a way that most chilling effects aren’t, and its effect on future reporting behavior will be significant and lasting.

Does retaliation require conscious intent — or can unconscious management behavior constitute retaliation?

Most employment anti-retaliation frameworks and compliance policy definitions do not require conscious retaliatory intent. The legal test in most jurisdictions focuses on whether a protected activity was a contributing factor in an adverse employment action — not on whether the manager consciously intended to retaliate. A manager who systematically routes career-building opportunities away from an employee after that employee engaged in a protected activity may be found to have retaliated regardless of whether the manager would characterize their decisions as retaliatory. The unconscious “she’s high maintenance” pattern and the conscious “I’m punishing her for reporting” pattern produce the same adverse employment effect and the same legal exposure.

What constitutes an adverse employment action beyond formal termination or demotion?

Courts and arbitrators have found adverse employment actions to include: removal from high-visibility assignments or projects, exclusion from career-development opportunities, assignment to less desirable accounts or territories, exclusion from management rotation or leadership development programs, reduced access to information or meetings, and any action that materially changes the terms, conditions, or trajectory of employment. The test is whether the action would dissuade a reasonable employee from engaging in protected activity — a test that assignment marginalization consistently meets, particularly for high performers for whom career advancement opportunities represent a significant portion of total compensation.

What should managers do when an employee’s concern-raising is creating management friction they find difficult to manage?

Address the concern through the appropriate channel — either by investigating it yourself, escalating it to HR, or referring it to compliance — so that the source of the recurring tension is addressed rather than absorbed. When a concern is properly addressed and closed, the employee typically stops raising it. When it isn’t addressed, the recurring conversation creates the management friction that leads to the unconscious avoidance behavior described in this scenario. A manager who finds an employee’s concern-raising draining should examine whether the drain is coming from the concern-raising itself or from the unresolved underlying issue the concern points to.

How to Use This Scenario in Training

Recommended for all managers, people leaders, and HR business partners who support managers in real time. Most effective when the manager and the employee audience are trained separately: managers need to do the self-examination exercise (examining their own assignment pattern relative to any recent protected activity) without feeling accused; employees need to understand that the pattern they’re experiencing has a formal name and a protected path to address it. Cross-reference with the Reporting & Non-Retaliation cluster and the Performance Review Retaliation scenario for comprehensive retaliation coverage.

This scenario demonstrates unconscious avoidance pressure — the retaliation pressure type with no identifiable decision moment — from the Decision Readiness Engine™. Decision-ready managers recognize when management friction is influencing their assignment decisions and route that recognition to HR before the pattern creates legal exposure. Decision-ready employees recognize that opportunity denial following protected activity has a name and a formal response pathway.

More Manager & Leadership Pressure Scenarios