There are several credible business reasons for moving from XP to Vista. However, there are many not to. There is never a realistic review of the upgrade impact to the entire business. Most companies can not provide a good and credible reason for their upgrade plan. If there is a plan.
What really kills me about the upgrade merry-go-round is that companies upgrade for reasons that have nothing to do with their business. They upgrade to protect their investment in licenses when they have not looked at how much it costs to upgrade in term of internal labor to develop the upgrade process and to handle the turmoil that an upgrade brings to their user population. They upgrade on the promise that they can finally realize some great feature or function of technology that they saw at a show several years ago. They upgrade because managers are using their budgets rather than loosing their budgets without considering whether there is a benefit.
For me, the incremental enhancements to security are worth the upgrade just to be able to lockdown the user environment. Then again, being a security focused consultant, it would be now wouldn?t it? While this is great for me, I wonder how much thought is given to weighing the cost/benefit analysis or even considering whether there is benefit to the user community or to the business. Microsoft?s product lifecycle policy puts even more pressure on customers to upgrade and this has become a major reason to upgrade. But at least this is intended to move lagging customers forward to more supportable technology which at least makes sense from a business perspective. Predictable interruption based on a predictable upgrade schedule beats the interruption of system failures.
Too many IT Departments forget to do the homework needed to determine whether there is any value to the organization to upgrade. While some upgrades are a no-brainer, other upgrades such as a massive organization wide OS upgrade have significant impact on many different aspects of the business beyond just the interruption required to perform the upgrade on an individual machine. The mark of a good IT Manager is the one that interviews all other department heads and solicits their input before slamming home that new OS, productivity suite, or database application. Most that I have seen lately let the department heads learn of the upgrade when it happens on their machine. I will have to say that this is a lot easier for the IT Department than having to add the consideration of what impact this would have to the upgrade plan.
Rant == 0