this post was submitted on 10 Oct 2023
1702 points (94.0% liked)
Technology
60112 readers
2383 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Subterfuge at work, a fun subject to study.
Some of my favorites from a declassified WWII "simple productivity sabotage" manual:
Insist on doing everything through "channels." Never permit short-cuts to be taken in order to expedite decisions.
Make "speeches." Talk as frequently as possible and at great length. Illustrate your "points" by long anecdotes and accounts of personal experiences.
When possible, refer all matters to committees, for "further study and consideration." Attempt to make the committee as large as possible — never less than five.
Bring up irrelevant issues as frequently as possible.
Haggle over precise wordings of communications, minutes, resolutions.
Refer back to matters decided upon at the last meeting and attempt to re-open the question of the advisability of that decision.
Advocate "caution." Be "reasonable" and urge your fellow-conferees to be "reasonable"and avoid haste which might result in embarrassments or difficulties later on.
When I first saw these I was like goddamn, psyops got to my executive director!
Sounds like how work is done in large corps
Or public administration
Wow, most of these points just sound like a responsible way to handle all the bullshit requests from employees. I'm not saying make it unnessecarily painful for employees to request changes. However, I currently work at a company that did the "just do it" approach for years, got big with it and now our department needs to clean up the bullshit of many years to get the company up to code with whatever regulations we are under and people still think we can continue working just like that.
Generally, too little of something is bad for one reason and too much of something is bad for another reason.
“Don't order new working materials until your current stocks have been virtually exhausted, so that the slightest delay in filling your order will mean a shutdown.”
See also: lean manufacturing
Sounds like how I buy shoes and jackets.
What's funny about this is all of this pretty much comes naturally when you're doing something you don't want to do without a reason to do it.
Do you know if there is a book (extensive article) which covers that in detail?
OSS's Simple Sabotage Field Manual, 1944
There's a link at the top for the full pdf. And do note, OSS is Office of Special Services, the WWII precursor to the CIA - not Open Source Software lol.
Thanks (☞゚ヮ゚)☞
WWII changed their name to BMV I think.