It's pretty simple... Most software users don't see the software as an abstract thing that can be better or worse, they see it as a tool they use to perform a task. Their goal isn't to use the software, it's to get their task done, and any change to the software (even a small one that benefits lots of other people) means that they will have to invest time in learning this new feature, which will take away from the time that they have to do the task that they want to get done.
It's a pretty straight forward calculation: I use Word to write school reports. I don't care that adding a step to the save dialog which other users (or even me) to do things in a more "logical" fashion. I've got my process, and I've probably even got some procedure in place to deal with the "inefficiency" that this new feature fixes. So if you make that change, then suddenly my old process will stop working, and i'll have to take an unplanned hour or two out of my day to learn how to use this new feature that you've implemented, when I was already on a time crunch for the thing I was doing. Sure, maybe your new feature will save me 8 hours over the course of the year, but the short term impact to my schedule is *really* frustrating.