In my first job after university, I was responsible for automating a ton of stuff in a telecom and making new apps that could connect and streamline processes,

In my first job after university, I was responsible for automating a ton of stuff in a telecom and making new apps that could connect and streamline processes, the usual efficiency and capability stuff. There was a team where I replaced their mainframe UI with a web-based UI that enabled better reports, better visibility and categorization of the orders, etc. It dug into the mainframe to do data IO, scrapers acted as the interface between the mainframe and web UI. One lady who used my system complained of getting tendonitis in her right wrist. It was from using the mouse so much, which she had never really had to do with the mainframe UI. Years later, I realize that updating their UI was the wrong thing to do. I could have given them the various reports and stuff without updating their UI. Updating their UI severely decreased their efficiency, even if the mainframe UI sucked to look at and was difficult for newcomers to understand. That being said, if an enterprise organization has high employee turnover, I think it's better to have a system that's easy to understand and use within a single glance. Those places sometimes have difficulty training their new employees and getting them up to speed. That being said, if employee turnover is high, the company probably has bigger problems.