No, this is not true at all. In fact, the very first software project I was paid for was a perfect example: I had to replace an ancient DOS based database app w

No, this is not true at all. In fact, the very first software project I was paid for was a perfect example: I had to replace an ancient DOS based database app with something more modern. The end result had a GUI that was completely different, barely retained the same workflow, had tons of new input validation that users had to cope with all of a sudden. End result? They had a knee jerk hate for it when they saw it. They would have to re-learn routines they had settled into for about 10 years. So there was push-back. And it didn't last: a few weeks after the transition everybody told me that they liked the new app so much more. Why? Because they couldn't make that many dumb mistakes anymore that were tedius to correct. The app kept track of more information behind the scenes that helped then woth processing the data and - that was the main reason IMO - I had carefully designed a ton of tiny nearly invisible helpers into the UI that helped a lot with data entry. There was stuff like autocompletion that had context sensitive suggestions, form fields would pre-fill with the most likely values where appropriate etc. It was fairly subtle. It took a while for the users to learn all that. But once they understood the new way of doing things, noone wanted to go back anymore.