Intelligence & power
An intelligence manual treated pointless meetings as weapons
The 1944 OSS manual recognized organizations as systems that could be disrupted through their own procedures. Its familiar office examples belong to a wartime document.
A weapon made of ordinary behaviour
Among the more surprising pages of the Office of Strategic Services'1944 Simple Sabotage Field Manual are examples involving committees, procedural delay and unnecessary discussion. Their setting is wartime disruption, but the behaviours sound familiar to anyone who has watched a routine decision consume a day.
The manual's insight was that damage need not begin with damaged machinery. Work also depends on decisions moving between people. If that movement slows, material and labour can sit idle even when the equipment remains intact. Administrative behaviour becomes part of the physical system's performance.
Procedure can protect or obstruct
A committee can bring relevant knowledge into a decision. A rule can prevent a dangerous shortcut. A request for clarification can expose a mistake before it becomes costly. The same outward forms can also consume effort without improving the result. The manual treated that ambiguity as useful to its wartime purpose.
This does not mean every slow process is sabotage. Intent cannot be diagnosed from resemblance to a paragraph in an old manual. An overloaded organization, unclear authority or a legitimate disagreement can produce similar symptoms. The historical source explains what its authors thought could be exploited; it does not identify secret motives in a contemporary workplace.
The title tells you what kind of source it is
This is a field manual: a prescriptive document intended to influence conduct. It is evidence of what its authors recommended. It is not a measured study showing how often those recommendations were attempted or how much disruption each produced. Answering those questions would require operational reports and evidence about outcomes.
Its organizational section also sits within a larger wartime text that includes physical sabotage. Isolating the office passages as a humorous productivity guide can obscure that purpose. The amusing recognition is real, but it should not replace the source's context or turn the entire document into a timeless management authority.
Read it as an anatomy of dependence
The historical value lies in its picture of how institutions function. A decision needs an owner. Information must reach someone able to act. A procedure must eventually terminate in a result. These are ordinary dependencies, but a system that forgets them can become vulnerable without losing a single machine.
A constructive contemporary reading is diagnostic rather than accusatory. Ask what a process is meant to achieve, whether its participants can explain that purpose and whether it has a clear endpoint. Those questions concern design and accountability, not suspicion about colleagues. The manual's lasting surprise is that an intelligence service considered such ordinary organizational habits strategically consequential. Its pages make the connection between wasted attention and impaired capacity unusually visible, while leaving the reader responsible for separating historical intent from present-day analogy.
Sources and further reading
- Simple Sabotage Field Manual ↗
OSS Strategic Services Field Manual No. 3, 17 January 1944; section 11, General Interference with Organizations and Production