It is not the user’s fault

Please don’t make me think: I just want to wash my darn clothes. You have no idea how hard it is to select a washer and dryer. I mean seriously folks: all I want is to wash and dry my clothes. I don’t need 500 buttons, schedules, a 300 page user manual and blah blah blah. Can I please have a washer with a single button that reads ON! How did it get so button and option crazy. You know what it reminds me off: bad software development! Let’s not think about how users will interface with the product…which reminds me of Jon’s post from Mozilla labs. Bang on…

The microwave with the most buttons may be most popular, but it is not the best microwave.

The best microwave has no buttons at all.

It doesn’t need any buttons because it already knows how long you
want your food cooked and how hot. You never need to set the clock,
either: it’s just always right.

The no-button microwave may not be reachable, but like a guiding star it shows us the direction we should travel.

Users do not know what interface they want.  Users do not know what features they want.

Users know the tasks they want to do, and the problems they have.

We learn more by watching the user work than by asking the user.

Comments are closed.