zlacker

I met someone who did that all the time. Turns out it was a learned behavior from having gotten pushed aside for coming across as too nit-picky one too many times. They turned in to the kind of person that would let other people make mistakes and just watch - and believe it or not, it worked for them! In their environment, that was a bad lesson well-learned.

>>whatsh+(OP)
There is some merit to that approach though. For example, I moved IT support requests from a messaging system to an actual ticketing system. The number of requests actually dropped because if they aren't getting help instantly they'll actually try something rather than just giving up immediately and calling IT. Many many issues just went away because if you have to wait a bit all the braindead "click the button" or "turn on your monitor" issues go away.

>>whatsh+(OP)
There is a distinction between "I said it once, and I'm not obligated to say it again", and "I said it once, and therefore I can assume that everyone knows it". The difference is in whether you need everyone to know it (accountable for the result), or only need to CYA (accountable for your job).

>>alar44+C6
That and a mix of people tolerating and working around broken systems because the bureaucracy wasn't worth it.