Quiet firing is when a manager makes someone's job steadily worse until they resign, rather than managing or dismissing them honestly. It is common, damaging, and legally riskier than most managers realize. Here are the signs, the causes, and the fix.

Quiet firing is the practice of pushing an employee out without ever telling them they are being pushed. Instead of a difficult conversation, a performance plan, or an honest dismissal, the person is slowly starved of the things that make a job worth having: interesting work, recognition, development, a manager's attention, sometimes hours or pay. The intent is that they read the signals and resign, sparing the organization the discomfort and cost of a termination. It is the mirror image of quiet quitting, and it is far more common than most companies admit. This guide covers what quiet firing looks like, why managers resort to it, the real risks it creates, and what both employees and employers should do instead.

What quiet firing means

Quiet firing describes a pattern rather than a single act: a manager systematically degrades someone's experience of their job until leaving feels like the only option. Nothing is ever said directly, no formal process is opened, and the departure is recorded as voluntary, which is precisely the point.

It is the counterpart to quiet quitting, where an employee withdraws discretionary effort without announcing it. Both are avoidance behaviors that substitute silence for an honest conversation, which is why they so often appear together, as our guide to quiet quitting explores from the other side of the relationship.

The crucial distinction is between quiet firing and legitimate performance management. A manager who names a problem clearly, sets measurable expectations, offers support, and documents the process is managing performance. A manager who says nothing and quietly withdraws opportunity is doing something else entirely, and the difference matters both ethically and legally.

It is worth naming the cost to the manager as well, because the behavior is rarely painless for them either. Quiet firing drags out over months, occupies mental energy that honest resolution would have freed in a week, and frequently ends in exactly the confrontation the manager was avoiding, only now with a worse factual record and an employee who has documented everything. The avoidance that feels easier at the start reliably produces a harder ending than the conversation would have.

The signs of quiet firing

The most common signal is the withdrawal of meaningful work. Interesting projects go to others, responsibilities quietly shrink, and the person is left with routine tasks that use none of their strengths. Nothing is announced; the scope simply narrows month by month.

Exclusion follows: being dropped from meetings that matter, left out of decisions in their own area, or removed from the informal conversations where direction is actually set. Alongside it, access to development dries up, no training budget, no stretch assignments, no promotion conversation, while colleagues keep moving.

Then come the relational signals. One-to-ones get cancelled or become perfunctory, feedback stops entirely or turns to unexplained criticism, and requests for clarity go unanswered. In harder cases it extends to material terms: reduced hours, unfavorable shifts, a relocated desk, or a sudden demand to return to an office when the role was agreed as remote.

Why managers do it

Conflict avoidance is the largest single cause. Telling someone their performance is not good enough, or that their role no longer fits, is genuinely uncomfortable, and a manager who lacks the skill or the stomach for that conversation may drift into making the job unpleasant instead, often without consciously deciding to.

Process and cost pressure account for much of the rest. Where dismissal requires documentation, notice, severance, or legal review, a resignation is cheaper and faster, and in organizations with headcount freezes a voluntary departure can be the only way to change a team. The incentives quietly reward the behavior.

Sometimes it is not deliberate at all. A manager who has privately concluded someone is not working out may disengage from them without any plan, and the effect on the employee is identical whether the intent was strategic or simply avoidant. That is why the pattern matters more than the motive when assessing it.

eMonitor — Signals

A Role Quietly Hollowing Out

-64%

Meaningful work

-48%

Meetings included

0

1:1s held

6mo

Pattern length

Assignments over six months

M1

M2

M3

M4

M5

What the pattern shows

Scope shrinkingYes

Exclusion risingYes

Feedback givenNo

▲ A steady six-month decline in assignments with no feedback given: the shape quiet firing leaves in the record.

Illustrative eMonitor dashboard.

The risks quiet firing creates

The legal exposure is the part most managers underestimate. In many jurisdictions, deliberately making working conditions intolerable so that someone resigns can amount to constructive dismissal, meaning the resignation is treated in law as a termination. If the treatment correlates with a protected characteristic, or follows a complaint, it can also support discrimination or retaliation claims.

The organizational damage is broader and more certain. Quiet firing is never as invisible as the manager believes: colleagues watch someone be frozen out and draw the obvious conclusion about how this employer behaves when it wants rid of you. Trust drops across the whole team, and the strongest people, who have options, start using them.

There is a competence cost too. Because the process is never made explicit, the organization loses the chance to find out whether the problem was fixable. Sometimes the person being quietly pushed out was mismanaged, mismatched to a role, or struggling with something temporary, and an honest process would have recovered a capable employee rather than losing one.

What to do if it is happening to you

Start by documenting rather than reacting. Keep a dated, factual record of the changes: projects removed, meetings you were excluded from, cancelled one-to-ones, requests that went unanswered. Patterns are far more persuasive than impressions, and a contemporaneous record is the single most useful thing you can hold.

Then force the conversation into the open. Ask directly and in writing for feedback on your performance and clarity on your role and priorities. A manager engaged in quiet firing relies on ambiguity; a specific written request for clarity removes it, and the response, or the absence of one, tells you a great deal.

If nothing changes, escalate deliberately, to HR or a skip-level manager, presenting the documented pattern rather than a complaint about feeling unwanted. Take advice on your position before resigning, since resigning may forfeit rights a constructive-dismissal claim would preserve. And in parallel, start looking, because in many cases the honest conclusion is that this relationship is over and the healthiest move is a deliberate exit on your own terms.

How employers should prevent it

The prevention is structural, not exhortative. Managers quietly fire people when honest alternatives feel harder than avoidance, so make the honest route easier: train managers to hold direct performance conversations, provide a clear and usable improvement process, and make it normal to raise a problem early rather than let it fester into resentment.

Then make the pattern visible. Quiet firing thrives on invisibility, so the countermeasure is oversight that notices when someone's role is quietly hollowing out. Regular skip-level conversations, exit-interview analysis by manager, and attention to workload distribution all surface it, and workload data in particular shows when a person's assignments have been shrinking for months, a pattern our guide to workload balancing examines.

Above all, treat an honest ending as a legitimate outcome. Not every hire works out, and an organization that can say so plainly, run a fair process, and part company with dignity has no need for quiet firing at all. The cost of that honesty is one difficult conversation; the cost of avoiding it is measured in claims, attrition, and a team that has learned exactly what your company does when it wants someone gone.

Best practices

How to keep quiet firing out of your organization:

• Train managers to have the hard conversation: avoidance is the root cause.
• Provide a usable improvement process: make the honest route the easy one.
• Hold skip-level conversations: they surface exclusion a manager will not report.
• Watch workload distribution: shrinking assignments are the earliest signal.
• Analyze exits by manager: patterns cluster around individuals.
• Document performance concerns properly: ambiguity is what enables it.
• Treat honest endings as legitimate: not every hire works out.
• Check your incentives: if resignations are cheaper, expect quiet firing.

Quiet firing is what happens when honesty is harder than avoidance, so the fix is to make honesty easier: clear processes, trained managers, and enough visibility that a hollowing-out role gets noticed before the person resigns.

Organizations that manage this well are not the ones that never part with people. They are the ones that can do it openly, fairly, and quickly, which costs one uncomfortable conversation and saves a great deal of trust.

Spotting the pattern early with eMonitor

Quiet firing is difficult to see from above precisely because nothing is ever announced, and the affected person rarely reports it. What it does leave is a shape in the record: assignments shrinking month over month, focused work declining, involvement narrowing. eMonitor's workload and activity trends make that shape visible at the team level, so leadership can ask about a role that is quietly hollowing out.

Used this way the data protects employees rather than policing them, which is the posture eMonitor is built for: aggregate team trends rather than individual scoreboards, employee self-access to their own data, and work-hours-only tracking. Trusted by 1,000+ companies worldwide and rated 4.8/5 on Capterra, it starts at $3.90 per user with a 7-day free trial.

If you want to know whether quiet firing is happening in your organization, look at whose workload has been quietly shrinking. Start a free trial and see the pattern in your own data.