I believe what he says in the book can be seen as contradicting but in reality, it is not. We, as designers, cannot focus on only what a user wants or needs, we also need to focus on what activity is going to be performed on this application as well. So, the user is not always correct. We should only add on to a design if it seems appropriate after multiple sketches, user tests, etc. "What is the purpose of the design?" is the question we should ask ourselves when determining if a feature should be added to a design. Overall, the two methods, user centered and designer-center, are both equal. One may work better in one case and the other in another (vice versa). First we must determine the purpose of the design before judging which method is better (for only you, make company tasks quicker, for public use, etc).
Hoekman's "situation-centric" design means redesigning or designing a feature by how a user navigated in a certain situation. The method we used was a user-centered method due to the fact of how we had to conduct a usability test, which is also similar to a "situation-centric" design.
No comments:
Post a Comment