The 1944 manual for sabotaging an organization reads like the minutes of your last meeting.

In 1944 the Office of Strategic Services published a classified field manual teaching ordinary citizens in occupied Europe how to sabotage organizations from within. Its advice for meetings and offices runs like this. Insist on doing everything through channels, and never permit shortcuts. Refer all matters to committees for “further study and consideration,” and make the committees as large as possible, never fewer than five. Bring up irrelevant issues. Reopen matters decided at the last meeting. Advocate “caution” and urge colleagues to be “reasonable” and avoid haste. Multiply the procedures and clearances so that three people have to approve where one would do.

Anyone who has worked in a large organization recognises this list, and not as sabotage. It reads like an ordinary week. The tactics needed no special skills, no equipment and no risk of detection, because the most effective sabotage is indistinguishable from the normal behavior of a dysfunctional organization. That raises an awkward question for the usual view, which holds that procedures are neutral and the trouble comes from bad actors abusing them. If a deliberate saboteur and a conscientious employee produce the same output, what exactly is the difference?

Why the committee makes a good weapon

Follow one decision into the committee. A saboteur sitting on it does not have to break anything. They raise one more consideration, ask whether last week’s decision was really final, and counsel patience. Each move is defensible, so nobody can accuse them of anything. A sincere colleague who worries about risk makes the same moves for honest reasons, and the decision is delayed just as long.

The reason both get the same result lies in what committees, channels and approvals are for. They are technologies of legibility: they make activity visible, controllable and auditable, which is useful to whoever sits above the system and costly to whoever is trying to get work done inside it. They were designed for control, not for output. Following them faithfully therefore slows the work whether or not anyone intends it, because the rules were never optimized for the work. The saboteur only needs to invoke the ritual at every opportunity, which is also what a careful bureaucrat does.

peopleware makes the same point from the other side with malicious compliance. If people followed the Methodology exactly as written, process would grind to a halt. An organization whose rules stop it when obeyed to the letter has already written a sabotage manual against itself.

Bad actors or bad procedures

The obvious objection is that procedures exist for good reasons. A committee catches errors one person would miss, and a second signature stops fraud. That is true, and it is why “just cut the red tape” is too crude. But the manual suggests a sharper test. A procedure that a saboteur can weaponize without anyone noticing is already sabotaging the organization in its normal operation. In that sense the procedures are the sabotage, regardless of intent. The manual taught saboteurs nothing new. It taught them to do what the organization already did, more consistently and with greater enthusiasm.

The fix that follows is fewer procedures, which means accepting some illegibility and disorder that the people above the system find uncomfortable. Better enforcement makes things worse, since enforcement is the very thing the saboteur exploits.

Read this way, the manual becomes a diagnostic. Count how many of its tactics describe your normal workflow. Each match is evidence of a system that has evolved the dysfunction a saboteur would have introduced on purpose, not of a hidden saboteur. Organizations do not need enemies to fail. Robert Jackall’s Moral Mazes is the ethnographic proof: the normal rules of corporate life, such as avoiding decisions, involving as many people as possible and never going around your boss, amount to the sabotage manual executed in good faith by people who believe they are being professional.

The OSS had to smuggle its instructions into occupied territory. The committee at your next meeting needed no smuggling, because someone convened it in order to be careful. The hard question is how anyone in that room would notice if it had stopped being careful and started following the manual.

References:

  • Office of Strategic Services, Simple Sabotage Field Manual (1944), declassified