Anonymous peer reviews are coordinated by a coalition against one colleague, landing on the same themes in different words, so HR sees what looks like consistent feedback from across the company.
An example
A year after a logistics-software startup closed its first large funding round, it hired a head of engineering from a much bigger company to bring order to releases. She cancelled two pet projects run by early engineers and introduced code reviews. In the next 360 cycle, seven of her nine anonymous raters described her as dismissive of the company's culture, each in different words, and four mentioned that she did not listen. Two of her direct reports, who rated her well, were outnumbered. The people-operations lead treated the results as consistent feedback and recommended coaching. The chief executive was about to agree when the chief technology officer pointed out that all seven negative raters came from the original team, and that three of their comments used the same unusual phrase about tourists from big tech.
Why it works
Convergence across many anonymous raters gives HR and the manager procedural cover, which makes acting against the target easy. With the target's strengths recast as arrogance and their independence as poor collaboration, defending them seems less worthwhile, and it is expensive: a manager who pushes back on what nine anonymous people said looks biased, and investigating coordination means questioning HR's own instrument. It needs a disciplined coalition, an HR function that treats aggregate results as authoritative, a target with few supportive raters, and anonymity that blocks any audit of who said what.
The thinking behind it
Solomon E. Asch Effects of Group Pressure upon the Modification and Distortion of Judgments (1951) found that conformity to a unanimous majority fell sharply when one other person gave the correct answer. Coordinated 360 comments present HR and the manager with something close to unanimity. Supportive raters who know the person's work play the part of that dissenting partner, which is why adding them is the most practical defense.
Robert B. Cialdini Influence (1984) describes social proof: when unsure, people look to what others are doing, and the more people seem to agree, the more correct a view looks. Nine anonymous raters converging on one theme look like proof to an evaluator who cannot see how the comments were produced. Checking for clustering and source diversity tests whether the agreement is independent.
Warning signs
Several anonymous raters use the same distinctive theme about one person in a single cycle, often with unusual phrasing in common. Strengths are recast as faults: confidence as arrogance, independence as poor collaboration. The negative raters come from one group, often one the person has recently crossed. Ratings from the people who work most closely with the person diverge sharply from the rest.
How to defend yourself
Defending the substance line by line rarely works against a multi-source pattern, so challenge the pattern itself.
- Ask HR whether the results were checked for thematic clustering, and how diverse the raters were.
- Point to any recent decision that set you against one group, with its date, next to the timing of the cycle.
- Make sure supportive raters who know your work are included next cycle, and ask your manager to add them.
- Ask that the 360 be weighed as one signal among several, alongside your delivered results.
If you are the manager, read a sudden convergence of anonymous themes as a question to investigate before acting on it.
How a leader shuts it down
Have HR check 360 results for thematic clustering and source diversity before they reach a review. Treat aggregate peer feedback as one input, weighed against delivered results and the manager's own view. Require a minimum spread of raters from different groups, and look harder whenever all the negative feedback comes from one of them.