Work
Share this article
A viral complaint exposes the gap between what performance systems promise and how managers actually use them.
An Amazon employee's post went viral last week. The claim was simple and devastating: a new manager arrived and suddenly years of solid performance reviews meant nothing. Intensive scrutiny appeared overnight. The employee concluded they were being "quietly managed out." Whether the allegation is accurate matters less than the conversation it sparked. Thousands of people recognized the pattern instantly. They'd seen it. They'd lived it. Some had done it.
Performance management was supposed to solve a problem. How do you help people grow, align their work with company goals, and make fair decisions about compensation and promotion? The theory is clean. Set clear expectations. Give continuous feedback. Review regularly. Adjust and improve. In practice, the system becomes something else entirely when trust breaks down or incentives shift.
The Amazon story resonates because it reveals a truth many HR teams would rather not discuss. Performance systems can be weaponized. Not always. Not everywhere. But often enough that employees have developed a shared vocabulary for it. "Managed out." "Put on a plan." "Documentation phase." These phrases signal that performance management has stopped being developmental and started being procedural. The goal is no longer improvement. It's exit.
The Architecture of Quiet Exits
Let's map the pattern. A manager decides, for whatever reason, that an employee needs to go. Maybe the decision is fair. Maybe it's not. The employee hasn't committed a fireable offense, so termination requires documentation. What follows is a sudden shift in management style.
Expectations that were previously implicit become rigidly explicit. Work that was once acceptable is now scrutinized for minor flaws. Employee feedback, which should flow naturally as part of healthy workplace culture, transforms into a one-way channel of criticism. Recognition for contributions stops. Every interaction gets documented. The performance improvement plan arrives, dressed up as support but functioning as countdown.
According to Gallup's research on employee engagement, only 23% of employees globally are engaged at work. When employees feel their manager is actively working against them, that number doesn't just drop. It inverts. Active disengagement takes root. Productivity collapses not because the employee lacks skill, but because the psychological contract has been shredded.
The employee typically has three options. Resign and save face. Fight through the performance improvement process and hope to survive. Or lawyer up and claim discrimination or retaliation. None of these outcomes serve the company well. The first costs institutional knowledge. The second destroys team morale. The third risks litigation and reputation damage.
Why Managers Choose the Quiet Path
Before condemning managers who use performance systems this way, it helps to understand the incentives. Direct confrontation is hard. Telling someone "you're not a fit for this role anymore" requires emotional labor most managers haven't been trained for. It risks conflict, tears, arguments, and potential legal exposure if the reasoning isn't airtight.
The performance management process offers a structured alternative. It feels more defensible. There's paperwork. There are improvement plans. HR teams are involved. If the employee eventually leaves, whether by resignation or termination, the documentation trail suggests the company did everything right. The manager followed the process.
But this path confuses process compliance with good management. Harvard Business Review's research on performance management shows that traditional annual review systems already struggle to improve performance. When those systems are deployed primarily to justify predetermined outcomes, they fail completely at their stated purpose.
The uncomfortable question: if a manager has legitimately concluded an employee isn't working out, what's the right way to handle it? Pretending everything is fine for months while building a case feels dishonest. But abrupt termination without any feedback history feels arbitrary and cruel.
The answer lies in the quality of continuous feedback long before things go wrong. When feedback is truly continuous, not just documented for legal purposes, problems surface earlier. Course corrections happen in real time. An employee who isn't meeting expectations knows it, because their manager has been clear and specific about what success looks like and where the gaps are.
The Role of Company Culture in Performance Abuse
Individual manager behavior matters, but workplace culture determines what becomes normal. In companies where "up or out" is the default, where stack ranking forces managers to identify bottom performers each cycle, where headcount reduction targets land quarterly, performance systems inevitably become tools of attrition management rather than development.
Amazon's culture has been documented extensively, sometimes celebrated for high performance standards, sometimes criticized for burnout and churn. The viral post doesn't exist in a vacuum. It emerges from a culture where performance pressure is intense and employee sentiments about job security run high. When that's the context, even well-intentioned performance conversations can feel threatening.
Culture shapes how managers interpret their role. In a company that celebrates "raising the bar," a manager might genuinely believe they're improving team performance by pushing out anyone who doesn't meet increasingly stringent standards. In a company that values psychological safety and development, that same manager might invest time in coaching and skill building instead.
The difference isn't just values on a poster. It's what gets rewarded. Do managers get promoted for developing their people, or for maintaining high performance metrics regardless of turnover? Are retention and employee engagement weighted in leadership assessments, or treated as HR's problem? Company culture answers these questions through action, not policy documents.
What Pulse Surveys Actually Reveal
Many organizations deploy pulse surveys to track engagement and catch problems early. The theory is sound. Regular check-ins can surface issues before they escalate. But pulse surveys face a credibility problem when employees suspect their responses might be used against them.
Imagine you're the Amazon employee from the viral post. Your new manager has started scrutinizing everything. An engagement survey arrives in your inbox. One question asks: "Do you feel supported by your direct manager?" What do you answer? Be honest and risk confirming you're a "problem employee"? Give high marks to avoid attention? Skip the question and hope someone notices the pattern of non-response?
This is where anonymity and aggregation become critical. Surveys need to be genuinely anonymous, with clear communication about how data gets reported. If responses are only shared at the team level when there are at least five respondents, people are more likely to be honest. If individuals worry their writing style or response timing might identify them, honesty disappears.
Even when surveys are well-designed, they only work if action follows insight. McKinsey's research on employee surveys emphasizes this point. Surveying without acting breeds cynicism faster than not surveying at all. Employees need to see that feedback creates change, or they stop believing the process has any purpose beyond checking a box.
Recognition as a Cultural Signal
One detail often overlooked in stories like the Amazon case: recognition stops. The employee who was previously acknowledged for contributions suddenly finds their work goes unnoticed. This isn't accidental. It's part of the pattern.
Recognition serves multiple functions in a healthy workplace. It reinforces desired behaviors. It signals what the organization values. It satisfies the human need to feel seen and appreciated. When recognition disappears selectively, it sends a clear message: you no longer belong here.
The absence of recognition can be more damaging than direct criticism. Criticism at least engages. It suggests the relationship still has potential for improvement. Silence suggests the decision has already been made. The employee has been written off.
Organizations serious about healthy performance cultures build recognition into their regular rhythms. Not just annual awards or formal programs, but everyday acknowledgment of good work. This doesn't require expensive platforms or elaborate systems. It requires training managers to notice contribution and say something about it. Publicly when possible, privately when that's more appropriate, but consistently either way.
Key insight from organizational psychology:
Employees don't leave jobs, they leave managers. But that oversimplifies. Employees leave cultures that allow bad management to persist unchecked. A single toxic manager is a management problem. A pattern of toxic management is a culture problem.
The HR Team's Dilemma
HR teams sit in an uncomfortable position when performance management gets weaponized. They're often aware of the pattern. They see the documentation that appears suddenly after years of satisfactory reviews. They watch managers who never previously engaged with performance processes become meticulous about every policy detail.
What should HR do? Push back and risk conflict with line managers who control hiring, budgets, and team performance? Comply with the process and become complicit in what might be unjust terminations? Try to coach the manager toward better practices while the employee's career hangs in the balance?
There's no clean answer, but there are better practices. HR teams can require that performance conversations happen regularly, not just when problems arise. They can audit performance review data for patterns like sudden shifts in ratings or managers who consistently rate certain demographic groups lower. They can insist on action plans that include specific, measurable goals rather than vague improvement demands.
Most importantly, HR can ask hard questions. When a manager suddenly wants to put someone on a performance plan, ask about the history of feedback. What conversations happened before this point? What documentation exists of prior concerns? What support has the manager provided? If the answers reveal that performance issues are being raised for the first time in a formal improvement plan, that's a red flag.
Communication Tools and the Illusion of Transparency
Modern workplaces overflow with communication tools. Slack, Teams, email, project management platforms, dedicated performance systems. Every conversation can be documented. Every interaction leaves a trail. This should make performance management more transparent and fair. Sometimes it does. Sometimes it makes the weaponization more sophisticated.
A manager building a case can point to timestamps showing an employee missed a message. They can highlight a thread where the employee asked a clarifying question as evidence of confusion or inability to follow instructions. They can screenshot a casual comment and reframe it as insubordination. Communication tools create evidence, but evidence requires interpretation, and interpretation depends on intent.
The same tools can protect employees. Written feedback creates a record of what was actually said versus what a manager later claims was said. Public channels make it harder for managers to gaslight employees about expectations or prior agreements. But only if the culture supports employees who document conversations to protect themselves, rather than viewing that behavior as suspicious or adversarial.
Real time analytics from these platforms can surface concerning patterns. If an employee who previously collaborated actively suddenly stops engaging, that's visible. If a manager's response time to one team member's questions increases dramatically, that's measurable. The question is whether anyone is looking at those patterns and asking why they exist.
What Action Plans Should Actually Accomplish
Performance improvement plans have a reputation problem. Employees see them as terminal diagnoses. Managers sometimes use them that way. But the concept itself isn't flawed. When someone genuinely struggles in their role, a structured plan to close skill gaps or clarify expectations can help. The problem is execution and intent.
A legitimate action plan starts with diagnosis. What specifically isn't working? Is it a skill gap that training could address? A misalignment between the role's requirements and the employee's strengths? A communication breakdown that's created confusion about priorities? Different problems require different solutions, and not all problems are the employee's to solve alone.
Good action plans include mutual commitments. Yes, the employee needs to demonstrate specific improvements. But the manager also commits to providing resources, removing obstacles, and offering regular feedback. The plan should be realistic. Demanding someone transform their performance in 30 days when they've been in the role for years and received no prior coaching isn't a plan. It's a countdown.
Most importantly, action plans should be rare. If a manager needs to put multiple team members on improvement plans, the problem probably isn't the individuals. It's the manager's hiring, onboarding, or feedback practices. HR teams should watch for this pattern and address it directly.
Building Systems That Resist Weaponization
Can performance management systems be designed to resist abuse? Not entirely. Any system operated by humans can be manipulated. But some design choices make weaponization harder.
Frequent feedback cycles help. When feedback happens monthly or quarterly rather than annually, sudden shifts in manager assessment become more visible. An employee who received positive feedback last month and scathing criticism this month raises obvious questions. What changed? Is the shift justified by performance, or by something else?
Multi-source feedback adds perspective. If an employee's peers and cross-functional partners consistently rate them highly while only their direct manager sees problems, that discrepancy deserves scrutiny. Peer feedback isn't perfect and can reflect popularity rather than performance, but it provides data points beyond a single manager's view.
Calibration processes, where managers discuss their assessments with peers and leadership, can catch outliers. If one manager consistently rates their team lower than similar teams, or if ratings shift dramatically when an employee changes managers, calibration conversations should address those patterns.
Transparency about process helps. Employees should know how performance reviews work, what goes into assessments, and what their rights are if they disagree with feedback. Mystery breeds suspicion. Clarity builds trust, even when the news isn't good.
The hard truth about employee sentiments:
Most employees don't expect perfection. They expect fairness. They can accept tough feedback if it's consistent, specific, and offered with genuine intent to help. What destroys trust is the sudden shift from acceptable to inadequate with no clear explanation except a change in management.
What the Amazon Story Should Teach Us
The viral post about being "quietly managed out" resonated because it named a pattern many people recognized. Whether this specific case represents unfair treatment or legitimate performance management gone defensive, we'll never know from outside. But the conversation it sparked matters more than the individual case.
Performance management sits at the intersection of individual relationship and organizational system. When either breaks down, the process fails. A great system can't overcome a manager determined to push someone out. But a weak system makes it easier for managers to abuse the process, even unintentionally.
The solution isn't to abandon performance management. Organizations need ways to assess contribution, develop talent, and make personnel decisions. The solution is to build systems that assume good intent but include checks against bad intent. Make feedback truly continuous. Train managers to have hard conversations early. Create multiple data sources beyond a single manager's opinion. Audit for patterns that suggest bias or weaponization. And most critically, build a company culture where developing people matters as much as delivering results.
When employee engagement is genuine rather than performative, when workplace culture values honesty over politeness, when HR teams have both authority and courage to challenge questionable management decisions, performance systems can work as intended. They become tools for growth rather than weapons for exit.
The Amazon employee's experience, real or perceived, reveals what happens when those conditions don't exist. A new manager arrives. The relationship starts wrong or sours quickly. Neither party knows how to repair it or wants to try. The performance system becomes the mechanism for separation rather than the framework for success. Everyone loses.
We can do better. Not by pretending performance problems don't exist or that every employee deserves to stay regardless of contribution. But by building systems and cultures where performance conversations happen continuously, feedback flows honestly in all directions, and managers face real consequences for weaponizing systems meant to develop people.
The uncomfortable questions remain. How many employees are currently experiencing what the Amazon worker described? How many managers are building documentation cases right now? How many HR teams are watching it happen and feeling unable to intervene? The answers matter because they reveal whether our performance systems serve their stated purpose or function primarily as legal cover for decisions already made.
Every organization needs to answer those questions honestly. Not with policy documents or values statements, but by examining what actually happens when a manager decides an employee needs to go. Is the process genuinely developmental, giving people a fair chance to improve? Or is it performative, creating a paper trail while the outcome was predetermined?
The Amazon story went viral because thousands of employees saw themselves in it. That's the real signal. Not whether one case was handled fairly, but that the pattern is common enough to be instantly recognizable. Until organizations address that pattern systemically, individual employees will keep sharing their stories, and the credibility of performance management as a development tool will continue to erode.
Ready to build performance management that develops people instead of managing them out?
Kodecrew helps organizations create cultures of continuous feedback, genuine recognition, and transparent performance conversations. Our platform gives HR teams the real time analytics and communication tools they need to spot problems early and support healthy manager-employee relationships.
Learn How Kodecrew Works
