Re: Wouldn't you think?
No, but only because of experience.
About a decade ago the IT department I was working in was so fucked, the CEO of the company ordered the CTO to hold a retreat where the entire IT department was free to speak their mind. And things were so bad they actually did. After airing a fair lot of dirty laundry the CTO made an unprecedented gesture. He actually opened the floor to the entire IT staff to plan the next set of upgrades. Mostly it was the networking team, as was appropriate. So they all sat down in a big meeting, discussed all of the things they'd like to do, and proposed what the next step for the organization would be. There were several projects, an upgrade to the current version of Exchange server to replace the aging 95 version we were running, a proposal for a secure wireless system, some server replacements, a new core switch to replace the used one that was purchased four years before when we moved into the building, and building out a new high end SAN.
After discussion and looking at the budget everyone (including the Exchange guy and you know how much THEY hate to pass on upgrades) agreed that although it would require the entire budget for only one project, the SAN should be the next project. So they wrote it all up including the options to do everything but the SAN. The one project they absolutely didn't want to do was the secure wireless. So they handed it to one of the junior techs and said "price this out gold plated so it gets rejected" which he happily did. The first project that was approved? Yep, the gold plated wireless proposal. The project that was scrapped without much discussion? The SAN. Yes, it did get built about two years later.
Biting the hand that feeds IT
