In IT you often find that when you give people exactly what they want, they are sorry they ever asked.
I helped one person who wanted a new version of Adobe rolled out to the entire company. They were working on a project and that project needed a new version of Adobe. Not an unreasonable request. I asked someone to test that new version and they tested it.
A week later that person had a different problem and I went to help them. It turns out that the fix was to upgrade their version of Adobe just like the other person who was testing it. However when I went to upgrade them they said “Maybe we shouldn’t upgrade this because it might break my other applications.” This was the same person who asked for the entire company to be upgraded the week before. I agreed that could happen, and upgraded him anyway. It worked fine. Problem solved.
Of course I went to my supervisor and told him what happened. The same person wanted the entire company to be upgraded, but not himself personally. You can’t have it both ways.
Often the quick and easy answer seems to be upgrading the software. Many times this is the correct one. I personally like using recent and supported software. However not every company believes in this. Many companies use very old software that is poorly supported or not at all. This is the main cause why they have problems as well.
To me, when you quickly want to make a major change and don’t consider the consequences you are just asking for problems. If I had upgraded everyone that day like it was my technical ability to do, I might have unleashed worse problems. Having someone test a change is so helpful, and so basic in giving the best IT experience for users.
If you want disaster make a quick change. If you want stability, think decisions through.