4 ms·
Some (many) users actively refuse to learn. There appears to be some psychological barrier that prevents them from even trying (perhaps similar to how some peo
by blunte 7y ago
Some (many) users actively refuse to learn. There appears to be some psychological barrier that prevents them from even trying (perhaps similar to how some people panic at seeing any math beyond simple addition arithmetic). That's not to say the people are stupid - many of them are relative experts in some other domain, but yet when a computer interface is presented, they shut off their brains.
While I find "wizard" interfaces frustratingly slow to use, I think they are a better approach for many users. Here's a silly but not so terrible idea for an email interface, wizard-style:
1. "You have a new email from bob@example.com. Would you like to open it? [Open] [Save for Later]"
2. (opened) (display email). "Do you want to reply to Bob now? [Reply] [Do Something Else]"
etc. etc.
This kind of interface could be handled by anyone, and it would probably work well for people with different physical or visual challenges.
Anything more complicated than this is just beyond the willingness or capability of most people to handle. What's really scary is that some people operate their cars much like they operate a computer - doing unnecessary ritualistic things that have no benefit or produce the desired outcome as a side-effect, leaving some systems in a permanent state when they should be enabled/disabled at different times, and so on. The tendency is to think that people are just generally incredibly stupid (unwilling to learn, not incapable); but perhaps it's just that our UI approach needs to actually be two approaches - one for users, and one for refusers.
- Already__Taken 7y agoUsers don't read so I don't know how well this is going to pan out. You're making the mistake thinking users are carefully operating their machines with a purpose. It's more like being surprised by a spider, clicking on anything that moves and if it starts bonging click shut down and try again later before you delete your life. /12 years tech support and have a family.
- serpix 7y agoThis brings back times when doing parental tech support over the phone. "can you read what is on the screen right now" "There is nothing on the screen!" "there is a box on the center of your screen with words, please read them" "OH that box.."
- TeMPOraL 7y agoThat's arguably consequence of the discussion being over the phone, not of it being about computers. In my experience, any kind of task which involves giving people instructions is extremely frustrating when done over the phone; there's just too much context missing, so you have to start being extra precise to compensate - but then, most regular people aren't used to being talked to with precision, so they start getting annoyed and push back. The most common example I can think of is trying to explain someone over the phone how to get somewhere, when you know the lay of the land but they don't. A lot of frustration and useless info gets exchanged before they're even able to communicate you where they are.
- onefuncman 7y agoShoulda just FaceTime'd...
- Etheryte 7y agoI think this type of approach doesn't really help anyone, it's just condescending. As a user I don't want to learn, I actively refuse to. I want to do what ever I need to do and move on. Unless I use your application professionally, I don't want to learn it. I think the crux of the problem is secretly hidden here, though. Many creators overestimate how interested other people are in what they made. The complexity of using your solution is always at odds with how painful the problem I have is. If your solution isn't easy to figure out, it can be easier to just solve the problem in an other way.