A director I worked with stopped giving honest performance reviews after his third year in the role. Not because he didn't care about his team. Because he had learned, precisely, what happened when he did.
Two years prior, he gave a straight assessment to a low performer. Within three weeks there was a complaint filed with HR about his management style, two teammates had become unavailable for projects he led, and a rumor was circulating that he was difficult to work with. The low performer got transferred to another team. The director got a reputation that followed him into his next role review.
He was not conflict-averse. He was educated.
What the Research Actually Says
New HBR research published this month confirms what that director already knew from experience. Negative performance evaluations frequently trigger retaliation from the people who receive them. The retaliation takes recognizable forms: gossip, deliberate work slowdowns, or coordinated sabotage of the evaluating manager's standing. The research finds that the financial and cultural damage from that retaliation can outweigh the benefits of strict enforcement. The authors frame manager leniency not as a failure of character, but as a rational response to a genuinely costly problem.
That framing matters because it changes the diagnosis entirely. Most organizations treat the accountability gap as a development problem. Managers need better coaching skills. They need to practice giving harder feedback. They need to be trained on difficult conversations and psychological safety and feedback models. The diagnosis is psychological. The prescription is training.
The accountability problem isn't that managers lack courage. It's that the organization has taught them, correctly, that courage is costly.
But if the behavior is rational — if managers are accurately reading their environment and making a sound cost-benefit calculation — then training them to be braver will not fix it. You are asking people to absorb a real, documentable cost on behalf of a system that has given them no protection for doing so. The courage they expend gets used up once. Then they remember what happened.
The Structural Problem Nobody Wants to Name
Performance accountability systems are designed with enforcement mechanisms and almost no retaliation protection. The person who holds someone accountable takes on risk. The person who does not takes on none. This asymmetry does not stay hidden for long. Managers who enforce honestly learn to stop, or they leave. Managers who do not enforce generate less friction, receive fewer complaints, and are often perceived as better people managers by the metrics that track complaints and turnover.
Over time, the organization selects for a specific kind of manager: one who has learned that honesty is expensive and has adjusted accordingly. This is not a character problem. It is an outcome the system produced deliberately, even if nobody designed it that way.
The downstream cost is specific. Low performers stay. High performers can see exactly what the accountability ceiling is, and they calibrate their own engagement to it. Some leave. The ones who stay often stop doing the discretionary work that nobody measures but everyone depends on. The manager who enforced and got burned is now managing a team whose most capable members are watching to see if it will happen again.
The Question Senior Leaders Are Not Asking
The diagnostic question most senior leaders reach for is "why aren't my managers having harder conversations?" It is a reasonable question with an unreasonable answer, because it assumes the barrier is internal to the manager rather than external to the system.
The more useful question is: what happens in this organization when a manager gives an honest review and the employee pushes back? If the answer involves reputational risk, HR complaints, and social isolation from peers who see enforcement as aggression, then the performance data coming out of your review cycles is not measuring team performance. It is measuring what your managers have calculated they can afford to say.
The organizations that produce real accountability are not the ones with better feedback training programs. They are the ones that have made honest enforcement survivable for the person doing it. That means visible organizational backing when someone holds the line. Real consequences for retaliation that are applied consistently and visibly. A track record, built over years, that tells managers what actually happens when they tell the truth about performance.
Without that track record, silence is the rational move. The director who stopped giving honest reviews after year three was not failing his organization. He was reading it accurately. That is the more uncomfortable truth for the leaders at the top of the system he was reading.
In Agile Sucks! (When You Do It Wrong), Chapter 1 documents what we call "Successful Failure" — roughly 70% of Agile organizations report positive metrics while producing no real business outcomes. The same pattern appears here: performance review cycles run on schedule, feedback conversations happen, the system looks like it is working. The output the system is actually producing is a measure of what managers are willing to absorb, not a measure of team performance. The transformation looks fine on paper.
Read Agile Sucks! (When You Do It Wrong) →