Every organization has one. The manager who drains morale, drives out talent, and somehow survives performance review after performance review. The one whose team fantasizes about quitting in unison. The one whose name triggers a collective sigh in Slack channels.
Ethan Evans spent more than two decades at Amazon, rising to the rank of vice president before retiring. He’s now offering something most corporate advice-givers won’t touch: a tactical guide for employees who want to get rid of an incompetent or destructive manager — without destroying their own careers in the process.
His framework, outlined in detail in a recent piece by Business Insider, reads less like a self-help listicle and more like a field manual for organizational insurgency. And it arrives at a moment when workplace power dynamics are shifting in unpredictable ways — with return-to-office mandates, mass layoffs, and AI-driven restructuring all reshaping who holds influence and who doesn’t.
Evans doesn’t sugarcoat it. Getting rid of a bad manager is hard. It’s risky. And most employees go about it entirely the wrong way.
Why Most Complaints About Bad Managers Go Nowhere
The conventional wisdom is straightforward: if your boss is terrible, go to HR. Or talk to your skip-level manager. File a complaint. Document everything. Wait.
Evans argues this approach almost always fails. Not because the system is inherently corrupt, but because it’s inherently conservative. Organizations are designed to preserve stability. A single employee’s complaint about their manager, no matter how well-documented, is easy to dismiss as a personality conflict or a performance issue in disguise. HR departments, Evans notes, tend to side with the existing power structure. That’s not cynicism — it’s institutional physics.
The problem compounds when employees act alone. One voice is an anecdote. Two voices might be a coincidence. But a coordinated, credible chorus of voices from high-performing employees? That’s a signal even the most conflict-averse senior leader can’t ignore.
This is the core of Evans’ thesis: removing a bad manager requires collective action, carefully orchestrated, with the right people involved and the right evidence assembled. He calls it, without irony, a mutiny. But a disciplined one.
The first step, according to Evans, is honest self-assessment. Before you organize a rebellion, make sure you’re not the problem. This sounds obvious. It isn’t. Evans has seen plenty of cases where an employee convinced themselves their manager was incompetent when the real issue was a mismatch in working styles or unmet expectations about promotion timelines. He recommends asking trusted colleagues — not just friends, but people who will be candid — whether the manager’s behavior is genuinely damaging or merely annoying.
If the consensus is that the manager is truly destructive, the next step is building a coalition. But not just any coalition.
Evans emphasizes that the coalition must consist of the team’s strongest performers. This is non-negotiable. If the people complaining are themselves marginal contributors, leadership will interpret the complaint as excuse-making. But when a company’s best engineers, top salespeople, or most reliable project managers collectively raise concerns, it creates a different kind of pressure entirely. It signals a retention risk that has direct financial consequences.
The math is simple. Replacing a high-performing knowledge worker costs between 50% and 200% of their annual salary, according to research from the Society for Human Resource Management. When three or four of those workers threaten to leave — or start interviewing elsewhere — the cost calculus shifts dramatically against keeping the bad manager in place.
Evans also stresses the importance of documentation. Not vague grievances. Specific incidents. Dates, times, witnesses, business impact. He recommends framing complaints not in terms of personal unhappiness but in terms of organizational harm: missed deadlines, lost clients, declining team metrics, attrition patterns. Senior leaders respond to business risk, not emotional appeals.
The Skip-Level Conversation and Its Discontents
Once the coalition is formed and the evidence compiled, Evans recommends approaching the bad manager’s boss — the skip-level leader — with a unified message. Not as a mob. Not with ultimatums. But with a clear, factual presentation of the problem and its impact on the business.
This is where most corporate insurgencies fall apart. The temptation is to vent. To list every slight, every passive-aggressive email, every meeting that ran 40 minutes too long. Evans warns against this. The skip-level leader doesn’t care about your feelings. They care about their own goals, their own metrics, their own reputation. Frame the problem in those terms.
He suggests something like: “We’re committed to this team and this work, but we’re losing people and missing targets, and here’s the data that shows why.” No personal attacks. No emotional outbursts. Just facts tied to outcomes.
And here’s the part most people miss: the skip-level leader already knows. In Evans’ experience, senior leaders are rarely shocked to learn that a particular manager is struggling. They’ve seen the engagement survey results. They’ve noticed the turnover. They’ve heard whispers. What they lack is sufficient justification to act — because acting means admitting a hiring or promotion mistake, managing a termination, and disrupting a team’s workflow. The coalition’s job is to make inaction more expensive than action.
Evans also addresses the nuclear option: mass resignation threats. He doesn’t recommend it lightly. But he acknowledges that in some cases, it’s the only thing that works. The key is that the threat must be credible. If top performers are genuinely prepared to leave — and have offers in hand to prove it — the organization faces an immediate, quantifiable crisis that demands resolution.
This tactic carries enormous risk. If leadership calls the bluff, the employees either have to follow through or lose all credibility. Evans’ advice: don’t bluff. Only threaten what you’re prepared to execute.
The timing of Evans’ advice feels particularly relevant. The post-pandemic workplace has created unusual tensions around managerial authority. Return-to-office mandates at companies like Amazon, JPMorgan, and Dell have reignited debates about trust, autonomy, and what managers actually do. A Gallup survey found that managers account for 70% of the variance in employee engagement scores — a statistic that makes bad management not just a team-level problem but a company-wide strategic liability.
Meanwhile, the labor market, while cooler than its 2022 peak, remains tight in specialized fields like AI engineering, cybersecurity, and healthcare technology. Skilled workers in these areas have options. They don’t have to tolerate a bad boss. And they increasingly won’t.
Recent reporting from multiple outlets underscores the growing tension. Companies are simultaneously demanding more in-office presence and struggling to retain the talent that makes that presence worthwhile. A bad middle manager in this environment isn’t just a morale problem — they’re a competitive vulnerability.
Evans’ framework also implicitly acknowledges something that corporate culture rarely says out loud: the formal mechanisms for addressing bad management are often performative. Annual reviews are backward-looking. 360-degree feedback is easily gamed. HR investigations are slow and frequently inconclusive. The real power to remove a bad manager lies not in process but in collective economic leverage — the ability of a team to credibly demonstrate that the manager’s continued presence will cost the company more than their removal.
This is uncomfortable territory for organizations that pride themselves on meritocratic structures and transparent governance. But Evans, drawing on his Amazon experience, is blunt about the gap between corporate ideals and corporate reality. Amazon’s famous leadership principles — customer obsession, ownership, bias for action — don’t automatically prevent bad managers from thriving. No set of principles does. People are promoted for the wrong reasons, protected by political alliances, or simply overlooked because their teams haven’t yet collapsed visibly enough to warrant intervention.
What Happens After the Mutiny
Suppose the mutiny works. The bad manager is reassigned, demoted, or let go. What then?
Evans warns that the aftermath is often messier than people expect. The team may feel relief, but it also faces a leadership vacuum. The skip-level leader who acted on the coalition’s concerns may resent the disruption, even if they agreed with the diagnosis. And the employees who led the effort may find themselves quietly labeled as troublemakers — not officially, but in the informal reputation economy that governs career advancement.
His advice: once the manager is gone, shift immediately from opposition to contribution. Volunteer for the transition. Help onboard the replacement. Demonstrate that the mutiny was motivated by commitment to the work, not personal grievance. The narrative matters enormously. If you’re seen as the person who saved the team, your career accelerates. If you’re seen as the person who caused chaos, it stalls.
There’s a deeper lesson here, one that extends beyond any single bad-boss scenario. Organizations that make it structurally difficult to remove ineffective leaders are organizations that accumulate dysfunction over time. The bad manager who survives year after year doesn’t just damage their own team — they drive away the kind of employees who refuse to tolerate mediocrity, leaving behind those who’ve learned to keep their heads down. The result is a slow, invisible degradation of organizational capability.
Evans’ mutiny playbook is, in a sense, a workaround for a systemic failure. In a perfectly functioning organization, it wouldn’t be necessary. Bad managers would be identified early, coached effectively, and removed promptly when coaching failed. But perfectly functioning organizations don’t exist. So employees are left to do the work that institutions won’t.
That’s the uncomfortable truth at the heart of Evans’ advice. The systems designed to ensure good management often don’t. And when they fail, the burden falls on the people with the least formal power — the individual contributors who show up every day, do the work, and wonder why the person in charge seems determined to make everything harder than it needs to be.
So what do you do when the system fails? According to a retired Amazon VP, you organize. You document. You build a coalition of your best people. And you make the business case so clearly that doing nothing becomes the most dangerous option of all.
It’s not elegant. But it works.
The Quiet Art of Deposing a Bad Boss: An Ex-Amazon VP’s Playbook for Corporate Mutiny first appeared on Web and IT News.