In 1944, the Office of Strategic Services published a classified field manual teaching ordinary citizens in occupied Europe how to sabotage organizations from within. The tactics require 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.
Simple Picture
Imagine an enemy agent infiltrates your company. Their mission: make the organization as slow, frustrating, and ineffective as possible without anyone suspecting sabotage. They would insist on following every procedure to the letter. They would refer every decision to a committee. They would give long speeches in meetings. They would haggle over wording. They would demand written orders for everything.
Now look around your actual workplace. The saboteur is already there — except nobody sent them. They arrived organically, promoted by a system that rewards compliance over competence. The orphaned responsibility mechanism ensures that raising the problem makes you own the problem — so nobody raises it, and the sabotage continues unopposed.
The Tactics
The manual’s organizational sabotage instructions fall into three categories, each targeting a different layer:
Decision Sabotage
Insist on doing everything through channels. Never permit shortcuts. Refer all matters to committees for “further study and consideration” — make the committee as large as possible, never less than five. Bring up irrelevant issues as frequently as possible. Refer back to matters decided at the last meeting and attempt to reopen them. Advocate “caution” and urge fellow conferees to be “reasonable” and avoid haste.
The Systems Bible names the structural version: perfection of planning is a symptom of decay. When the planning apparatus grows more elaborate than the thing being planned, the organization has shifted from doing to managing. The sabotage manual simply describes what that shift looks like from inside — and the point is that it looks exactly like conscientiousness.
Work Sabotage
Work slowly. Contrive interruptions. Do your work poorly and blame it on bad tools. Pretend instructions are hard to understand and ask to have them repeated. In making work assignments, sign out the unimportant jobs first and assign important jobs to inefficient workers. Insist on perfect work in relatively unimportant products.
This is tempo destruction — the saboteur’s goal is to decouple effort from output, ensuring that maximum activity produces minimum result. The Theory of Constraints explains the mechanism: every non-constraint team “staying busy” sends more work to the bottleneck, reducing the only throughput that matters. The saboteur does not need to slow the bottleneck directly — they just need to keep everyone else frantically active. The Expert Beginner achieves the same effect without trying: by defining mastery as the current plateau, every push toward genuine improvement becomes “unnecessary” or “not how we do things here.”
Morale Sabotage
Be pleasant to inefficient workers; give them undeserved promotions. Never pass on your skill and experience to a new or less skillful worker. Demand written orders. Multiply the procedures and clearances involved in everything — see that three people have to approve where one would do. Code review antipatterns are the engineering-specific version: each one weaponizes an approval gate while looking like legitimate thoroughness — the reviewer is “just doing their job.”
This last category is the most revealing. The Dead Sea Effect operates on exactly this mechanism: the talented evaporate because they will not tolerate the dysfunction, while the residue — grateful to have a job, entrenched in maintenance roles — becomes the permanent population. The Gervais Principle explains why: the Clueless, loyal to the organizational abstraction itself, implement these policies sincerely. The saboteur does it deliberately. The output is identical.
The Core Insight
The manual’s power is not in the tactics but in the recognition test. Every tactic maps to behavior that any corporate worker has witnessed, and most of it was never deliberate sabotage. The question this forces: if deliberate sabotage and normal institutional behavior produce the same output, what exactly is the difference?
The answer, structurally, is nothing. The software political axis reveals the mechanism: conservative engineering philosophy — where safety always trumps progress — produces the same output as the sabotage manual when taken to its logical extreme. The sincere conservative and the saboteur both insist on more process, more review, more safety checks. Legibility explains why. Procedures, channels, committees, and approvals are power technologies. They make activity visible, controllable, and auditable — which is useful for whoever sits above the system and destructive for whoever is trying to get work done inside it. The saboteur exploits the system’s own control mechanisms against it. But so does every sincere bureaucrat who insists on following the rules. The rules were designed for control, not for output. Following them faithfully is indistinguishable from sabotage because the rules were never optimized for the work.
The priesthood dynamic completes the picture: ritually pure communication (papers in journals, memos through channels, decisions by committee) solves a coordination problem but also creates an attack surface. The saboteur does not need to break the ritual — they just need to invoke it at every opportunity. peopleware names the resulting pathology malicious compliance: if people followed the Methodology exactly as written, process would grind to a halt — which means the Methodology is already a sabotage manual that the organization wrote against itself.
Dimwit / Midwit / Better Take
The dimwit take is “bureaucracy is stupid — just cut the red tape.”
The midwit take is “procedures exist for good reasons — the problem is bad actors exploiting them.”
The better take is that the procedures are the sabotage, regardless of intent. A procedure that can be weaponized by a saboteur without anyone noticing is a procedure that is already sabotaging the organization in its normal operation. The manual does not teach saboteurs to do anything new. It teaches them to do what the organization already does — just more of it, more consistently, and with greater enthusiasm. The fix is not better enforcement of procedures but fewer procedures — accepting the illegibility and disorder that the powerful find intolerable because the alternative is an organization that sabotages itself.
Main Payoff
The Simple Sabotage Field Manual is the most efficient organizational diagnostic ever written. If you want to know whether your organization is healthy, read the manual’s tactics and count how many describe your normal workflow. Each match is not evidence of a saboteur — it is evidence of a system that has evolved the same dysfunction that a saboteur would deliberately introduce.
The deepest lesson: organizations do not need enemies to fail. The system develops goals of its own the instant it comes into being, and those goals increasingly favor self-preservation over output. The procedures that were created to organize work become the work. The channels that were created to route information become the obstacles. The committees that were created to improve decisions become the delay. No saboteur required. The system does it to itself. Moral Mazes is the ethnographic proof: normal corporate behavior — avoid decisions, involve maximum people, mask all emotion, never go around your boss — is the sabotage manual executed in good faith by people who believe they are being professional.
References:
- Office of Strategic Services, Simple Sabotage Field Manual (1944), declassified