How to detect and eliminate organizational sabotage

Executive overview

Everyday behaviors that grind organizations to a halt — endless committees, CC-everyone emails, haggling over wording — were documented in a 1944 CIA predecessor manual as deliberate tactics to destroy enemy organizations from within. These same behaviors now happen organically, without bad intent, making them hard to name and harder to fix.

The saboteur's advantage: every destructive behavior is an excess of something genuinely good.

Bob Frisch, Cary Greene, and Rob Galford adapted the Simple Sabotage Field Manual into a modern framework for identifying, naming, and eliminating these patterns before they calcify into culture.

The original eight sabotage rules

1. Insist on doing everything through channels; never permit shortcuts.
2. Refer all matters to committees; make committees as large as possible.
3. Haggle over precise wording of communications, minutes, and resolutions.
4. Refer back to matters decided at earlier meetings; reopen settled questions.
5. Give lengthy speeches; repeat points already made.
6. Bring up irrelevant issues as often as possible.
7. Demand written confirmation of every verbal decision.
8. Never make a decision — always ask for more information or study.

Sabotage by committee

Committees are unavoidable, but most are too large, too vague in purpose, and too undefined in authority.

Three fixes:

• Clear charter up front: Are you making a recommendation, a decision, or an advisory input? Define it before the first meeting.
• Closure mechanism: If seven people split 4–3, what happens? Does it escalate? Does the chair break the tie? Decide in advance.
• Small core, peripheral experts: Add legal, finance, or HR as consultants — consulted before major decisions, not permanent seats. Keep the working group tight.

On leader authority: when a committee chair's role is undefined, the chair defaults to either coordinator (buys donuts, distributes agenda) or full decision-maker — and nobody knows which. Make the chair's scope explicit to the chair and to every member.

Survey data: 55% of respondents said referring matters to committees happens frequently or constantly in their organization.

Asking for clarity on charter and closure is not pushback — it is the job. Once these questions become culturally normal, committees start functioning quickly.

Sabotage by haggling

Haggling over wording explodes in proportion to the number of communications an organization produces. Three saboteur archetypes:

• The defender: Won't release a point even when the group has moved on.
• The wordsmith: Must tweak every sentence in every draft.
• The grammarian: Catches typos but derails the meeting doing it.

All three are doing something valuable — until the volume tips into obstruction.

Three fixes:

• Define the process before drafting: Who reviews, in what sequence, and what kind of input is needed from each person.
• Ask specific questions, not open ones: "What feedback do you have?" opens the floodgates. Ask about the one thing you're actually unsure of.
• Name the final decision-maker: Someone must have the call. In journalism this is the editor. In most organizations it is undefined — define it.

Before circulating broadly, route the draft through one or two trusted reviewers with no stake in the outcome. They clear most of the friction before it hits the group.

Sabotage by carbon copy

CC overload is the highest-ranked sabotage behavior among senior executives in organizational surveys. At one airline workshop, 90% of the top 40 executives said CC-everyone happens frequently or constantly.

Why it happens: the sender feels they have done their duty the moment they hit send. The receiver is buried.

Key finding: for most senior leaders, less than half of incoming email is addressed directly to them — the majority is CC.

Three fixes:

• Proactively unsubscribe from distribution lists you don't act on.
• Default to phone or in-person for anything that genuinely needs a person's attention; don't use CC as a substitute for a real conversation.
• Use the subject line as a signal: Flag emails requiring action or a specific read differently from informational ones.

On the illusion of informing: being CC'd alongside 150 others is not being informed. If something needs to land, tell the person directly. The Murdoch phone-hacking trial illustrated this — an executive was shown to have "received" a critical email but had read only the first paragraph of a multi-paragraph thread.

Leaders can set explicit norms: define what "informing me" means on their team and what it does not mean.

Why these behaviors are so hard to root out

Each sabotage behavior is a strength overused:

• Committees → good input, multiple perspectives
• Precise wording → accuracy, no embarrassing errors
• CC lists → transparency, keeping people informed

Because every behavior has a plausible defense, calling it out feels like attacking a virtue. This is why the 1944 manual rated these tactics so highly — a saboteur caught is a dead saboteur, and these behaviors carry no fingerprints.

Naming the pattern (using a shared reference like the book) gives teams permission to have conversations they could not have before. The conversation becomes about the pattern, not the person.