Is the user always correct? Not at all. Designers should provide features to fulfill a specific need of the user. Just because one or more users asks for a feature doesn't necessarily mean that it will fulfill a necessary need. Designers also shouldn't ignore what users ask for. If the majority of a population is asking for a specific function, it may be necessary for them to complete the function your software was designed to do.
In Project 2 I redesigned on of the bikes in the SRSC. Based on the new sketch I would get rid of the audio buttons. I have never seen anyone use them and I'm not even sure what they are for. I would also get rid of some of the preprogrammed options that have their own buttons. A lot of them seem unnecessary and until you have use the bike it is very unclear as to what most of them even do.
In Project 2 I redesigned on of the bikes in the SRSC. Based on the new sketch I would get rid of the audio buttons. I have never seen anyone use them and I'm not even sure what they are for. I would also get rid of some of the preprogrammed options that have their own buttons. A lot of them seem unnecessary and until you have use the bike it is very unclear as to what most of them even do.
Posts
Yes, designers do not necessarily satisfy all personal/specific user needs. Designers need to listen to users as well as to have their own design principles in terms of simplicity considering general user groups. In that sense, your suggestion for redesign makes sense. At the same time, you might also want to consider providing some advanced features--if they are pretty critical--as optional menus (which are usually hidden/ignorable but adjustable for those who need them).
ReplyDelete