This article raises good points, but I'd like to argue / disagree with it in several points: It doesn’t mean that your users are stupid, just that they haven’t

This article raises good points, but I'd like to argue / disagree with it in several points: It doesn’t mean that your users are stupid, just that they haven’t spent the thousands of hours in front of a computer that you have. Like office workers spending 8 hours a day in front of a computer? They easily make that time only on work time.. not that it helps. ..they don’t know how to (or even that they can) copy and paste text. Some users don't. But what should I do, send a copy of computer 101 with every eMail I send? Many users are used to web applications and don’t understand that they need to download and install new versions of desktop software to get access to the features in a new version. So, what's the maintenance staff there for? In my experience regular office users don't set up or update anything, ever! Data storage File system hierarchy and network mount points are so far off the average user horizon that you shouldn't bother anyway. You just point to it in the file explorer. Everything else is completely pointless. As for filetypes and converting: ok, that's a valid point. It's a good idea to send instructions with it, as it is a somewhat non-common task. The jargon you use I agree. Talk the users language, not computer slang. You should therefore never put something only in a right click menu or anywhere else that it can’t easily be discovered. Please, I beg you. Put stuff where you would normally expect it from your WM / OS. If it would be in the context menu, then put it there. Normally you also put stuff in the menu bar / ribbon / icon bar depending on conventions. Don't try to invent new interface guidelines, you'll probably fail.. horribly. Concurrency Try not to expose them or avoid it entirely (rework the workflow if necessary). Otherwise build the interface in a way that clearly notifies the user of this circumstance. Non-technical users aren’t so confident and won’t try things in the same way. In fact some of them seem to think that a wrong move could cause the computer to burst into flames. Most of them don't try anything at all. They will ask you how to do it. If you have some kind of system that has tweaks: train your users (that's what tech training is for). So try to stick to conventions they will understand Absolutely. The need for backups I preach this all the time. People also always agree to me in this respect. Doesn't help, they never actually do it, much less spend money on it. Could as well talk to the wall.. That they should read the documentation I totally agree. No one will read your precious documentation. If you roll out a new software, train them with the workflow. You do train your workforce to use the tools they use, right? Unskilled users often don’t realize how unskilled they are. Consequently they may blame your software for problems that are of their own making. May? They always do. I figure this must be human nature or something. One just has to be as polite as possible in such cases. In other words, stay professional. ------------- Otherwise I found it the article as entertaining as irksome. Raises some good points.