While it is necessary to hear the feedback from the users, they can sometimes be wrong. It is possible that the experience the user tells to the designer is different from what actually happened, and this problem is not usually because the user has intention to harm the application by providing false feedback.
Therefore, the designer sometimes should decline requests to add certain features sent from some users; they sometimes will ask for features that will make the software or the Web site worse than before. Another possible problem is that there are more than one type of users who will use an application or a Web site. If the designer answers yes to every request, some groups of users might think that they are being edged out, and some of them might switch to the competitors' products.
Hoekman advocates "situation-centered" design as an alternative to "user-centered" design which stands between user-centered design and activity-centered design. In this design method, the designer knows the user of the product he or she designs, but focuses on the situations which it is built to solve.
In order to follow the situation-centered design method in project 2, I could have tested the machine by myself before developing user case and usability test, to recognize the problems that other users might or might not encounter.
No comments:
Post a Comment