Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
1944 OSS Manual on How to Sabotage Productivity (businessinsider.com)
11 points by kiyanwang on Sept 13, 2021 | hide | past | favorite | 5 comments


Full manual has been removed from the website.

Some favorites 1. Work slowly. 2. Rehash settled items from previous meetings

Here are a few which could modernize the manual:

Force hangup the person speaking when available during critical moments.

Attend meetings late.

Always jump to another call when critical choices are made.

Review all possible options, and reject the best two for "security" reasons.

Let the contractors have free reign.

Hire only the long winded and argumentative.

Fire your testers and embed a few contractors to understudy your best devs.

Always fire the bottom ten percent.

Put your best devs on formatting reports.


Some of these are not like the others:)



This always makes the rounds because it's funny how well it matches just... an average office environment. Are your coworkers spies?!?!

It seems to me that this war-era document might have been hastily created, and maybe they just asked 100 office workers: "What really grinds your gears". And then put the results in here without further analysis.

What's missing is some shred of evidence that the things it says to increase can be increased. Want more pointless meetings? You can't just do that. Maybe organizations are naturally resilient to more pointless meetings, having naturally reached a saturation point already.


Not reproduced in the Intercept article: undermine the capacity, availability, and reliability of public transportation, especially rail. Someone in the KGB must have gotten a copy ;-).




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: