A series of sabotage guides to help you dismantle any endeabour, organization, or team.
An initiative of the Office of Strategic Systemic Decay (OSSD).
Disclaimer: Satire!
This repository is a satirical take on corporate culture and the concept of sabotage in a humorous context. It is not intended to promote or encourage any damaging, illegal, or unethical activities. This guide is based on the United States Office of Strategic Services' (OSS) sabotage manual from World War II, adapted for a modern corporate environment.
The repository is structured to provide a comprehensive guide to various sabotage techniques, categorized by the role of the field agent. As corporate roles vary widely, the guide is designed to be adaptable to different contexts and situations. For maximum effectiveness, agents are encouraged to tailor the techniques to their specific environment.
- Ensure you have Git installed: If you don't have Git installed, download and install it from git-scm.com.
- Have a rich text editor: Use any text editor of your choice (e.g., Visual Studio Code, Sublime Text, Atom) to edit the files in this repository.
- Install a markdown preview extension: If your text editor supports it, install a markdown preview extension to view the files as you edit them. This will help you see how the markdown renders in real-time.
Visit the markdown syntax guide for more information on how to format your markdown files.
- Fork the repository: Click the "Fork" button at the top right of this page to create your own copy of the repository.
- Clone your fork: Use the command
git clone <repository URL>to clone your fork to your local machine. - Create a new branch: Use
git checkout -b <branch-name>to create a new branch for your changes. - Make your changes: Edit the files in your local repository to add or modify sabotage techniques. ( use the template below for consistency )
- Commit your changes: Use
git commit -m "Your commit message"to commit your changes to your branch. - Push your changes: Use
git push origin <branch-name>to push your changes to your fork on GitHub. - Create a pull request: Go to the original repository and click "New pull request" to submit your changes for review.
## [Pattern Name]
### Sabotage Technique
A pithy description of the core failure strategy.
> e.g. “Overload all communication into one Slack channel and mute it.”
### Field Deployment Instructions
Exactly how to implement the sabotage in a real environment.
Be specific and mischievous.
> e.g. “Create a Slack channel named #project-meta-updates-team-coordination. Add everyone. Pin 32 threads. Never summarize decisions.”
### Expected Symptoms
Observable behaviors and warning signs if the sabotage is working.
> e.g. “People stop reading messages, create side chats, and miss critical updates. Tensions rise over ‘who knew what, when.’”
### Amplifying Factors (Optional)
How to make the failure worse or more entrenched.
> e.g. “Celebrate ‘quick response times’ to noise. Add automated alerts to the same channel. Discourage questions.”
### Detection Clues
Smells or phrases to listen for in the wild.
> e.g.
- *“Wait, that was decided?”*
- *“I thought someone else was on that.”*
- *“I missed that — where was it posted?”*
### Countermeasures (Reality Mode)
What thoughtful teams can do to prevent, detect, or recover.
> e.g. “Establish communication contracts. Designate signal vs. noise channels. Use short, human summaries weekly.”
### Sabotage Credibility Rating
*(Optional: How likely is this to happen accidentally?)*
🟡 Low – Satirical only
`Medium` – Sometimes happens
`High` – We’ve lived through this and called it “normal”