News for hackers. Stuff that matters.
Re:If too many users are wrong, it's probably your fault (2011) by danieltillett on Tuesday January 12, 2016 @04:41PM (#10890613)
Just assume your users are illiterate, innumerate, and have a broken mouse that randomly clicks and you will be fine.
Re:If too many users are wrong, it's probably your fault (2011) by rntz on Tuesday January 12, 2016 @05:12PM (#10890808)
This is the opposite of what the article is saying. The users weren't clicking randomly. They were clicking with a purpose, they just didn't understand the difference between their menu bars and the ones inside the image. They had a faulty mental model, not a faulty mouse.
Re:If too many users are wrong, it's probably your fault (2011) by danieltillett on Tuesday January 12, 2016 @06:40PM (#10891264)
I think you are missing my point − if you design a UX with this user type in mind you would have avoided the problem described in the article from the beginning.

The solution to robust user interfaces is not to just whack labels on images saying don’t click on this, but to step back and assume your user can’t (or won’t) read, can’t (or won’t) do anything mathematical, and also who loves to randomly click on things. Build for the worst possible user in mind and you will avoid a lot of problems.

For example, if the author had assumed that people like to randomly click on things then they could have created a pop-up that said don’t click on this, use the menu above.

Re:If too many users are wrong, it's probably your fault (2011) by kaybe on Tuesday January 12, 2016 @07:01PM (#10891361)
Which the user then won't read?
Re:If too many users are wrong, it's probably your fault (2011) by danieltillett on Tuesday January 12, 2016 @07:08PM (#10891392)
Then on their second random click you drag their mouse to the menu for them. Keep thinking of solutions.
Re:If too many users are wrong, it's probably your fault (2011) by 5ilv3r on Tuesday January 12, 2016 @07:00PM (#10891357)
Having random thrashing return useful instructions (like making the button they SHOULD be clicking on glow or blink a few times) is not a bad design pattern. Reminds me of the annoying (to me) new mac wiggle-for-massive-cursor feature.
Re:If too many users are wrong, it's probably your fault (2011) by danieltillett on Tuesday January 12, 2016 @07:03PM (#10891371)
Exactly, but you really need to get into the mindset of the random clicker user type to even think of doing this.
Re:If too many users are wrong, it's probably your fault (2011) by nkrisc on Tuesday January 12, 2016 @05:08PM (#10890790)
While I prefer to frame it with a bit more empathy, essentially, yes. This is correct.
Re:If too many users are wrong, it's probably your fault (2011) by danieltillett on Tuesday January 12, 2016 @06:47PM (#10891292)
I am not suggesting that you should think that your users are like this, but that you should design with this type of user in mind. Step back, put on your dunce cap, and fix the problems with your design.

This raises a really interesting point which is the cognitive elite are responsible for designing systems with zero empathy for the rest of the population. It is much harder to design a system that anyone can use and most system designers really don’t make the effort.

Re:If too many users are wrong, it's probably your fault (2011) by nkrisc on Tuesday January 12, 2016 @10:50PM (#10892214)
The problem you bring up is very real. Who designs software and websites? People who are very good with computers. Who uses the software and websites? Mostly people who aren't good with computers.

I work in a UX role and my yardstick is whether my mom would understand it.

Re:If too many users are wrong, it's probably your fault (2011) by danieltillett on Wednesday January 13, 2016 @01:43AM (#10892674)
Great approach - assuming of course that your mother is not a developer :)
Re:If too many users are wrong, it's probably your fault (2011) by rakoo on Tuesday January 12, 2016 @05:12PM (#10890815)
Said differently, The User Is Drunk (https://www.youtube.com/watch?v=r2CbbBLVaPk)