If It Isn't Broken, Don't "Fix" It.

Have you ever have an experience in your life where you decided to "fix" something and regretted it? I've actually had numerous experiences like this. I think my problem is that I always wanted more where more could have meant something newer or better or even cooler. In terms of your actual workflow, as a professional, I'd say unless you really needed to change something up, I think you should stick with works. The thing you mostly don't want to sacrifice is stability.

With that said, I want to go through some scenarios where it actually does make sense to update things.

1) Security. It's not talked about much but this is a big thing. There's a lot of electronic mayhem out there and you don't want to be compromised.

2) Bug fixes. If they affect you then sure go ahead but if not, there's always a risk of other bugs. Software development is a constant work in progress.

3) New features that enhance your abilities than translate into saving time, making the client experience better, or enhance collaborative abilities.