3 ms·
What the hell is wrong with users that you won't read the screen before clicking around on buttons!? I've been dealing with a set of users at work who could ea
by moron4hire 13y ago
What the hell is wrong with users that you won't read the screen before clicking around on buttons!?
I've been dealing with a set of users at work who could easily help themselves and continue on with their work if they would actually, you know, read the dialog boxes I spent tons of time writing to explain to them why the operation they tried was not correct and how to do it correctly. They don't want "wizard" interfaces that take them step-by-step through things, but they clearly can't use form-based interfaces that provide every option at once.
I watch them, it is their job to use this computer to do their work. In every training session I've ran, if I can get them to slow down long enough to even notice that a dialog box displayed, then they easily figure out their next step and continue on. But if I let them go at their own pace, they get confused and don't even recall that a dialog box appeared in the first place.
And it's not just non-techies. Most of the programmers I've worked with don't read the compiler's error messages. All they do is double-click the line to jump to the section of code and then try to figure it out from there, often by random-walking changes to the code until they get something that compiles. "If it compiles, it's correct", apparently. Never mind that they could save themselves a ton of time and confusion to read the error message and realize that you can't call Substring on a float!
If there weren't pertinent information on those screens, in those messages, then the installation could be done automatically. "open, next, next, next" is inferior to "open" as a user experience, but those "next" steps are there because there is important information there.
- Groxx 13y ago>... but those "next" steps are there because there is important information there. The OSX ecosystem would generally care to differ with you there, where the standard installation process is to drag a .app slightly to the right in the dmg that auto-mounts and auto-opens and shows you exactly what to do. Then you run it if you feel like it. Or even run it right from that window, it usually works, and quite a few applications will even detect it and offer to move themselves to your applications folder. Contrast this with a very common Windows install, which is run -> tell where to extract -> skip welcome screen -> uncheck shortcuts and start menu -> install -> uncheck 'run now' and 'show readme' -> click 'finish'. Sometimes there is important information in those steps. Very frequently there is not, and it's just a waste of time, and an annoyance. Just like the 'welcome' screen in those installers. Nearly all of that could have been done in one page, instead it's split into several, literally training people to just keep hitting next.