Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Looks like government has already implemented a lot of these suggestions.


> Refrain from making decisions until all possible stakeholders can weigh in

> Create overly-ambitious timelines and set impossible-to-keep deadlines

> Send unnecessary meeting invites then cancel them last-minute

> Don't use collaborative software, just email things back and forth

> Introduce burdensome software license approval processes

> Leave off the phone or video call information from a calendar invite

Forget government, this is a summary of standard operating procedure at my last (large, private sector) employer. Maybe they weren't all idiots, they were just fighting the man.

Just like the original Simple Sabotage Manual, this is worth reading just to reflect a painfully clear image of your own organization's dysfunction (and possibly your own role in it).


This is the point. It is very desirable for sabotage to look like standard corporate inefficiency.

Smash equipment, waste thousands and get caught. Delay a big project, waste millions and nobody notices.




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

Search: