Skip to content

Comment on Simple Sabotage Field Manual – How to Destroy Your Organizationsparent

Comments

Also, I feel like they are saying maybe you can/should look into some of these things, even done in good faith, to see if they are actually helping or hurting. “Haggle over precise wordings of communications, minutes, resolutions” This may be done in good faith, but is the situation/task something that needs a ridged , precisely detailed, process and it is helping to insist on precision? Or is it something that could be done just as effectively without ridged precision? Or does it end up conflicting with other requirements?

If a report has to have days of the week spelled out (“Monday” rather than “MON”, “percent” rather than “%”) but you also have a strict limit on character count due to space constraints, you end up with less precise wording in the report. Taking a step back and looking at it from the “if I wanted to actively sabotage this process, what would I do” might allow you to see good faith efforts that end up in bad outcomes.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.