> I recommend a different strategy when you encounter annoying processes like this—insist upon following these processes, to the letter, and going through appro

> I recommend a different strategy when you encounter annoying processes like this—insist upon following these processes, to the letter, and going through appropriate channels until the system collapses under its own weight. This is usually not what happens. Case in point: Our company had an easy means to share files with anyone at the company. You could specify exactly who is allowed to see it. Suddenly IT took that means away, citing security reasons (people were not using it properly). However, all the alternatives they provided were unworkable - and I mean that literally. They only worked within people in the same department, but you couldn't send something to people of other departments. The files (text) I needed to share were classified as top secret, so sending them via mail attachments (unencrypted) was a no-no according to IT. Encrypting them made them not work on the receiving end (the decryption process was somewhat faulty - although you could view them in the tool, it wouldn't save it properly to disk, so the tools that acted on them failed. I made a fuss about this and for a few days complied with IT policy and work came to a halt. But only my work. Everyone else just said "Screw IT" and sent the files unencrypted over email in violation of company policy. My management isn't going to be sympathetic with me if none of my teammates are on board. And in general, this is how it plays out. Those who find non-kosher workarounds will utilize them, and you'll be in a small camp fighting IT. At your annual review, you'll be the least productive and will get the boot.