Quiet Firing

A simple explanation

There is being told you are no longer needed, and there is being slowly removed from the conditions under which you can do well — the meetings you used to be in, the projects you used to lead, the feedback that used to come, the eye contact that used to be there. The first is a firing. The second, when it happens deliberately or when it happens through accumulated managerial neglect, is quiet firing. The exit is engineered without being declared.

It is not always cynical. Sometimes a manager has lost interest in a worker and acts on the loss without ever having a conversation about it. Sometimes the practice is more deliberate — a way to avoid severance, documentation, or the difficulty of saying no. The worker, inside it, often cannot tell the difference, and the inability to tell is itself part of the cost.

An everyday example

You used to be cc'd on the strategic email thread. Now you are not, and when you ask, the reply is we just streamlined the list. You used to lead the quarterly review. Now you are presenting a sub-section, and the lead is someone newer. Your one-on-ones, which used to run thirty minutes, now run ten when they happen and get cancelled when they do not. Performance feedback is fine. Specific opportunities are not the right fit at this time. No one has said anything is wrong. Something is wrong.

You start working harder, because that is the move you know. You ask more questions. You volunteer for more. The pattern does not change. By month four, the question you cannot stop asking is whether you are imagining the entire thing.

What does quiet firing look like?

It looks like a slow withdrawal of the conditions under which the worker was previously able to do well — visibility, feedback, opportunity, social presence — combined with a steady refusal of any direct conversation about it. The cancellations are small. The exclusions are explainable. The feedback gap is framed as not having anything specific to address. Each individual instance has a non-malicious reading. The accumulation describes a pattern that the individual instances cannot.

The diagnostic is the response to inquiry. A worker who asks directly — what could I be doing differently, what opportunities am I being considered for, why was I not in that meeting — and who receives consistently vague, deflecting, or recursive answers is reading a pattern that is more than coincidence. The vagueness is the message.

The behavioral loop

A loop that runs on absence rather than presence:

1. Withdrawal begins — a meeting cancelled, an email thread shrunk, a project reassigned without explanation.
2. First confusion — the worker registers the change but cannot interpret it. Charitable readings dominate.
3. Reach for explanation — the worker increases effort, asks more, volunteers more, tries to find the diagnosis through behaviour.
4. No diagnosis returns — the feedback gap persists. Specific opportunities are deflected. Direct questions get vague answers.
5. Self-blame supplied — the Threat System, unable to locate the danger, locates it in the worker. The Belonging System, unable to locate the exclusion, treats it as deserved.
6. Performance degradation — the worker, now anxious and over-monitoring, makes errors they would not have made before. The errors are then read as evidence.
7. Confirmation loop — the degradation is used, sometimes explicitly, as the basis for further withdrawal. The worker now has a documented reason for what was already happening.
8. Re-entry or exit — the worker either leaves on their own, often blaming themselves, or stays in a role that has been hollowed out around them.

Emotional drivers

Four feelings, often stacked:

• A pervasive confusion — the worst feeling of the loop, because confusion blocks every response that would otherwise be available.
• A creeping self-doubt that surfaces in unrelated parts of the worker's life — their parenting, their friendships, their judgement on small decisions.
• A faint shame about being unable to fix it, often metabolised by working harder, which the loop is calibrated to absorb.
• A delayed anger that arrives late and often after the exit, when the worker can finally see the pattern from outside it.

What your nervous system does

The body responds to the social withdrawal the way it responds to other ambiguous social threats — with chronic, low-grade activation that the worker often cannot name. Cortisol stays elevated. Sleep loses depth. The morning routine acquires a dread that the worker attributes to the work itself, when the work is the surface and the social field around it is the source.

Over months, the body's reading of the workplace shifts. The building, the meetings, the colleagues, the manager — each becomes a low-grade danger cue. The worker walks in carrying physiological data their conscious mind is still arguing against. By the time the conscious mind catches up, the somatic load has often produced real health costs that outlast the role.

The DojoWell interpretation

Quiet firing is one of the more corrosive patterns the modern workplace produces, and the MDT reading does not soften it. The Threat System's role is to locate danger; when danger is real but unnameable, the System defaults to the only locatable target — the worker themselves. The Belonging System's role is to maintain inclusion; when exclusion is being delivered without being declared, the System often supplies the interpretation that the exclusion is deserved.

The substitute is self-blame as explanation. This substitute is not cynical on the worker's side — it is the body's attempt to convert an incoherent situation into a coherent one. A workplace that is mistreating you is harder to bear than a self that is failing. The Systems, asked to choose between an incoherent threat and a coherent self-fault, default to the self-fault. The substitute closes the cognitive loop and opens a larger somatic one.

The density signature is residue_accumulation. The effort is real and continuous — the effort of trying to discover the diagnosis, of working harder against a pattern that does not respond to effort, of holding a coherent self under steady invalidation. The deposit is near-zero, because the role has stopped depositing in any way that the worker can carry. The residue accumulates across multiple registers: somatic, motivational, self-conceptual, sometimes relational and financial.

The closure pattern is no-closure because the practice depends on the absence of closure. A declared firing closes a loop, however painfully; quiet firing keeps it open. This is part of what makes the pattern uniquely corrosive — there is no event to grieve, no boundary to mark, no clean version of the story the worker can later tell themselves.

The intervention is rarely try harder. The intervention is to read the pattern accurately, to test it directly, and to plan an exit on the worker's own terms rather than the employer's. Sometimes the testing produces an honest conversation that changes the trajectory. More often it confirms the diagnosis. Either outcome is information the worker can use; the alternative is staying inside the loop with the Systems supplying self-blame to make the staying bearable.

How do I leave a job I am being quiet fired from?

You leave deliberately, with the next move staged, and with the framing of the leaving owned by you rather than supplied by the loop.

Three moves, in order of difficulty:

1. Stop arguing with the body. The somatic data has been honest. If your chest tightens at the office door and your sleep has thinned, those are findings, not failures. Let them count.
2. Test the pattern explicitly once. A direct, written request for specific feedback and a specific opportunity. The response — or the non-response — is data the worker can act on without ambiguity.
3. Exit on your timeline, not theirs. The practice is calibrated to make the worker leave on their own under their own bad story. Leaving on the worker's timeline, with the next role secured and the story owned, denies the loop its design.

Practical steps

1. Document the pattern as you live through it. Specific exclusions, specific deflections, specific gaps. Not as a grievance — as an anchor. Memory degrades inside the loop; the document survives.
2. Get one outside read. A trusted friend in your field, a mentor, sometimes a therapist or lawyer. The single most useful function of the outside read is breaking the self-blame substitution by introducing a coherent alternative reading.
3. Re-establish evidence of competence outside the role. A side project, a community contribution, a colleague network reactivated. The Belonging System needs counter-evidence to the exclusion, and the workplace will not supply it.
4. Plan the financial runway. Quiet firing often ends in a worker-initiated exit without severance. Build the runway deliberately so the timing of the exit can be yours.
5. Refuse to inherit the story. The exit is real and may be necessary. The framing that you failed is not yours to carry. Mark the difference, in writing if needed, before the leaving.

Reflection questions

• When did the conditions for doing well start being withdrawn, and what changed?
• How do I know if it is me or the workplace, and what evidence would change the answer?
• What does the body have to say about Monday mornings that the mind is still arguing against?
• What would leaving on your timeline, with the story owned by you, look like?

Frequently Asked Questions