Quote:
Originally Posted by Head416
Two very different scenarios. If I had a non-IT manager talking about stuff like this, I would say, we aren't doing that, then describe some hypothetical scenario that somehow justifies the objection and ends the discussion. At first I thought he was an idiot, but now I'm thinking he was just handling the situation in a politically correct manner. There are thousands of ideas that could technically work, but they're not happening on my network, the health of which I am responsible for.
|
Then why not just say "I am responsible for the health of this network so that is not happening. If you would like to submit a formal request that makes the business case for why we should do that I will review / consider it."
Giving him some BS answer is BS and apparently OP knew enough to know to get his answer verified. If it turns out he got a line of BS IT guy now looks like an idiot who does not know his poo. Situations like that have a way of making people go rogue and do secretly exactly what you don't want done.
If you make him submit the request and deny it for valid reasons you have documentation in case he does go rogue.