What This Actually Is
The Simple Sabotage Field Manual was written in 1944 by the OSS, the predecessor to the CIA. It wasn't some dramatic spy thriller. It was a practical document for people living under enemy occupation who wanted to make the war harder for the other side without ever firing a weapon. The whole premise is that you don't need to blow up a bridge. You just need to do your job slightly wrong, consistently, across enough people, and the system breaks itself. The manual organizes its guidance around workplace behaviors. Most of the actual text is just a list of things like: make unnecessary complaints, insist on following every single procedure to the letter, talk in circles during meetings, deliberately misunderstand instructions, and create confusion wherever possible. That's it. No explosives. No covert operations training. The effectiveness comes from scale, not sophistication. I worked on a project years ago where we had to audit how compliant our team was with certain operational procedures, and I realized the same dynamic is at play when you're looking at organizational resilience. The manual assumes the saboteur is embedded. You're not an outsider trying to break in. You're already there. That's the part people miss when they read it.
The original document is in the public domain. You can find it on the National Archives website, and several reputable repositories have hosted scans for years. I won't link to anything directly since URLs rot, but searching for "OSS Simple Sabotage Field Manual National Archives" will get you there.
How the Mechanism Actually Works
The core insight isn't that individual acts of sabotage matter. A single person working slowly or making mistakes occasionally is an inconvenience. The manual targets something called coordination decay. When enough people in a system each introduce small frictions independently, the total output degradation becomes multiplicative, not additive. A factory doesn't lose 5% because five people are careless. It might produce nothing at all because the delays cascade through dependent processes. This is why the manual emphasizes actions that look normal on the surface. Deliberately misunderstanding orders so you do the wrong thing and then ask for clarification again. Insisting on perfection in trivial details while the critical path stalls. Holding meetings that could have been emails and then running those meetings without conclusion. Each one is deniable. Each one is plausible. And together they're devastating. Here's a counter-intuitive point that most summaries skip: the manual actually warns against overtly destructive actions. Destroying equipment, setting fires, stealing documents — those are considered bad sabotage because they draw attention, create martyrs, and trigger retaliatory crackdowns that make real resistance harder. The whole doctrine is built on the idea that the best sabotage is the kind nobody can prove is happening.
Get the Full Details
I ran into a real edge case with this when I was studying how these techniques transfer to modern corporate environments. There's a boundary where "following procedure too carefully" stops being sabotage and starts being performance review material. In one case I looked into, someone tried to implement a systematic slowdown by insisting on documenting every minor decision in triplicate. They lasted three weeks before their manager sat them down and asked if everything was okay. The workaround that actually works in practice is subtler: you don't refuse to follow procedure, you just apply it inconsistently and without explanation. You follow it rigorously when it's convenient and skip it when it's not, and you never acknowledge the pattern. That creates more confusion than outright refusal ever would, because you can't pin it on anyone person.
The Dark Side Nobody Talks About
This manual has serious limitations and downsides that most people glaze over. First, it requires a network. A single person doing these things is annoying, not damaging. The technique only scales when enough people are doing it simultaneously across different points in the system. That's the hardest part. Building that kind of distributed compliance without detection is extremely difficult. Second, it degrades trust. When people start noticing that work isn't getting done, they don't naturally conclude "organized passive resistance." They conclude the organization is broken or the leadership is incompetent. That can create genuine collateral damage to people who aren't involved in whatever larger cause you're supporting. Civilian workers, supply chains, essential services — they all feel the impact whether or not they agree with the sabotage goals. Third, the manual was written for a very specific context: industrial and military targets in occupied Europe during WWII. Transferring these techniques to other environments changes the risk calculus significantly. In a civilian workplace, the consequences for getting caught are termination, not execution. But the organizational damage from implementing this kind of systematic slowdown is still real, and it affects people who didn't consent to it.
If you're looking at this from a purely defensive angle — understanding what it looks like when it's happening to you rather than planning to use it — the best countermeasure is transparency. Most of the manual's techniques rely on plausible deniability and the inability to prove coordination. Breaking that requires making processes visible, creating clear accountability chains, and normalizing direct communication about workload and bottlenecks. A team that regularly discusses where work is actually getting stuck can't be undermined by the kind of slow, deniable friction this manual describes, because the friction shows up as a conversation instead of a mystery. The full manual runs about 80 pages with a handful of appendices. It's remarkably dry reading. Some sections are genuinely useful for understanding organizational vulnerability from a defensive standpoint. The rest is mostly common sense dressed up in wartime urgency. I've seen people treat it like a blueprint for revolution, and I've seen people ignore it entirely because it seems too obvious. Both reactions miss the point. The value isn't in any single technique. It's in recognizing that systems are fragile not because of what you break, but because of how many small things can go wrong at once when everyone's doing their part slightly differently than they should be.
