Colleagues stop responding to one person, cutting them off from information and coordination until they give in or resign, and winning the underlying argument does not bring the replies back.
An example
In March, the purchasing manager at a family-owned building-supply distributor raised a question about rebates one supplier was paying to branch managers. The head of sales, who was close to the supplier, never mentioned it to her. Within two weeks, branch managers stopped answering her emails about stock levels, the weekly inventory call went ahead without her invitation, and her requests for sales forecasts sat unanswered while a colleague's went through the same day. Nothing was ever said or written. Her orders, built on stale numbers, produced two stockouts in May, and the owner asked what was going wrong in purchasing. In June an outside auditor confirmed her concern about the rebates. The emails still did not come back.
Why it works
Nothing is offered and no one is persuaded. It makes staying worse: being informed, influencing decisions, having a network, all hollowed out while the title remains. It makes staying costlier: monitoring who is speaking, tasks stalled for lack of input, metrics degrading through no visible attack. Because it works by attrition, winning the dispute does not end it. Coalition discipline holds it together, along with a workflow where the person depends on the group, asynchronous work where non-response is deniable, and enough ambiguity that it never becomes a formal grievance.
The thinking behind it
Solomon E. Asch Asch's Effects of Group Pressure upon the Modification and Distortion of Judgments (1951) found that a single ally sharply reduced conformity to the majority. A freeze-out depends on uniform silence, and one colleague who keeps working openly with the person gives others permission to do the same, which is why finding that colleague is among the strongest defenses.
John M. Darley Darley and Latané's Bystander Intervention in Emergencies: Diffusion of Responsibility (1968) found that people were less likely to help when they believed others were also present, each feeling a smaller share of the obligation. In a freeze-out every non-response is shared across the group, so no one feels responsible for the isolation. Traceable channels and response-time expectations put a name on each silence.
Warning signs
Emails and invitations from one person go unanswered by the same cluster of colleagues for weeks, while peers' requests move normally. Meetings they used to attend happen without them. Work that depends on their input stalls, and the stall shows up in their metrics, with no visible attack. No instruction to ignore them exists in writing.
How to defend yourself
Turn the silence into a record. Deniability is what keeps it going, and documentation ends that.
- Keep a log of non-responses: what you asked, whom, when, and what happened to the work.
- Move requests to written channels and ask for written confirmations with dates.
- Force formal sign-offs where your work requires them, so any bypass becomes visible.
- Copy outside allies whose acknowledgment the group cannot suppress, and build ties beyond the local network.
- Look for one colleague willing to keep working with you openly. One person breaking the silence often brings others back.
If the substance of the role is gone, decide whether to leave, and take the log with you.
How a leader shuts it down
Set response-time expectations and use traceable channels, which leave the freeze-out little room to hide. Require written feedback, and give an ombuds office real reach. When one person's work stalls for lack of replies, find out who stopped replying and why.