No, the user is not always correct. There is a big difference between what the user wants, and what the user needs. If a user were to ask for a new feature on a website, it is not always necessary for the designer of the website to add it. Too many features can cause frustration, cluster, and confusion. For every additional feature, there is more to learn, read about in the help section, and it opens up more room for error or for something to go wrong. There is a larger "user-centered" focus that Hoekman talks about. It is a variety of different things. This is allowing the users to have there voice heard, but not let it be heard to loud. You always must remember the applications main purpose even when users are wanting more features. These featues might not be necessary, especially because no application can be directed at every user. You always should keep it simple and understand when there might be too much going on.
Project 2 eliminations.
I would eliminate several of the preset buttons that seem to be very unnecessary and extraordinarily similar such as the "cardio," "hill training," and "heartrate," options. The bike machine my partner and I redesigned is a perfect example of how too many features can cause frustration and clutter. All of the features that I would take out could be simulated by increasing the resistance and pedal speed. This would make users be capable of getting started faster without being confused, along with being influenced to make a more customizable workout that would suit any given individuals needs.
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment