I think you misunderstand. Changes for changes sake are negative for users. The last thing you want to do is change something that was working for users withou

I think you misunderstand. Changes for changes sake are negative for users. The last thing you want to do is change something that was working for users without giving them anything for it. However a lot of actively developed software today changes because they want it to be "fresh and exciting". Basically because of desire to use changes to market it. But changing anything for that reason hurts usability. Any change means the user will have to adapt to that change. You want to minimize the user having to adapt to anything. When you do make them adapt you need to give them clear value for that adapting.