3 ms·

The average user has the same problems, but doesn't realize it is a UI problem or even think that he could be more productive. When he does he probably thinks t

The average user has the same problems, but doesn't realize it is a UI problem or even think that he could be more productive. When he does he probably thinks that he is too stupid to use a computer.

onli 5y ago
Which is by the way one main point in "The Design of Everyday Things" by Norman, the book being one core pillar of the usability field.
- mrighele 5y ago
  Yes, I read the book which is in part responsible for my previous comment. But it not only that. The older I get the less I am willing to spend energy to interpret the UI I have in front of me: even finding out which is the app I want to use in the wall of blue apps on my phone is wasted time.
quietbritishjim 5y ago
A saw a really obvious instance of this recently, with an old lady trying to use a self checkout. The machine asked which payment option you wanted: cash, credit card, voucher, etc. She selected cash. That brought you to a screen with a button in the middle allowing you to switch quickly to pay with card (to pay the remaining balance after you'd part paid with cash). The button text was "pay with card". The problem is, because it wasn't obvious that it was a button, she thought she had accidentally chosen the wrong option at the previous screen. She chose the "back" button at bottom and then selected "cash" again, but had the same problem. I saw her go through this cycle several times before asking for help. A really obvious button style could well have avoided the problem.
- husarcik 5y ago
  Sounds like they could have labeled it "pay with card instead".
  - quietbritishjim 5y ago
    What you've done there is add some extra text saying that this is not a current status - it's an action you could take. You could just as well have added "(this is a button)" instead. Why not just make it visually obvious that it's a button? Edit: You could say something similar about any non-verbal cues. Why not say "error" instead of using a red error icon? Why not say "left" instead of using a left-pointing arrow? Etc. The answer is always that (if used appropriately) it lowers the user's cognitive load. Admittedly sometimes it's reasonable to use both e.g. usually you do say "error" in words too, and maybe your suggestion would also be useful for this button.

The average user has the same problems, but doesn't realize it is a UI problem or even think that he could be more productive. When he does he probably thinks that he is too stupid to use a computer.

onli 5y ago

Which is by the way one main point in "The Design of Everyday Things" by Norman, the book being one core pillar of the usability field.

mrighele 5y ago
Yes, I read the book which is in part responsible for my previous comment. But it not only that. The older I get the less I am willing to spend energy to interpret the UI I have in front of me: even finding out which is the app I want to use in the wall of blue apps on my phone is wasted time.

quietbritishjim 5y ago

A saw a really obvious instance of this recently, with an old lady trying to use a self checkout. The machine asked which payment option you wanted: cash, credit card, voucher, etc. She selected cash. That brought you to a screen with a button in the middle allowing you to switch quickly to pay with card (to pay the remaining balance after you'd part paid with cash). The button text was "pay with card". The problem is, because it wasn't obvious that it was a button, she thought she had accidentally chosen the wrong option at the previous screen. She chose the "back" button at bottom and then selected "cash" again, but had the same problem. I saw her go through this cycle several times before asking for help. A really obvious button style could well have avoided the problem.

husarcik 5y ago
Sounds like they could have labeled it "pay with card instead".
- quietbritishjim 5y ago
  What you've done there is add some extra text saying that this is not a current status - it's an action you could take. You could just as well have added "(this is a button)" instead. Why not just make it visually obvious that it's a button? Edit: You could say something similar about any non-verbal cues. Why not say "error" instead of using a red error icon? Why not say "left" instead of using a left-pointing arrow? Etc. The answer is always that (if used appropriately) it lowers the user's cognitive load. Admittedly sometimes it's reasonable to use both e.g. usually you do say "error" in words too, and maybe your suggestion would also be useful for this button.