Obviously, "back in the day" TUIs were the only option, but computers were not as a prevalent back then, so there was no familiarity factor to leverage.
Obviously, "back in the day" TUIs were the only option, but computers were not as a prevalent back then, so there was no familiarity factor to leverage.
They do in the job roles I exampled because a large part of their job is quick entry. I have experience building and supporting systems for those types of users and a frequent comment is "I want to be able to enter information as quickly as I can so I can keep up with the customer speaking their instructions". Some of the older agents even preferred green screens because they could write with one hand and type with the other (while wearing a headset) -- I never quite got how they managed to multitask like that but kudos to them for pulling it off.
The company wanted everything to run under Windows so it had to be a native app with a GUI. When we deployed it there was a flood of compaints. Most of them were about the speed of data entry and the fact that the old keyboard shortcuts they were all used to had stopped working.
We tried to fix as many of the issues that we could but there was only so much that we could do. As it was a contract job we had to work with the UI the company wanted and as it was a contract job, once the bugs were fixed we couldn't make any other changes.
This raises another important consideration. A lot of software isn't and shouldn't be aimed at "most people". A few weeks spent learning something less intuitive can easily pay off over the course of a professional career using the software if it affords those that know the interface well a faster or otherwise better workflow.
Just a reminder so that you people don't design CAD software for heavy use by professionals in the same way you'd design a tax form for almost everyone to use once a year.