Monday, February 10, 2014
4- Rachel Rosenbaum
From what I learned from Hoekman the user is not always correct; however, he says they adapt to technology which makes sense. Humans don't always know how to use something right away. The fist time humans used a computer or an IPhone they probably hated everything about it because it was so new to them. Now most people can't go a single day without using one. He says it is not always useful to listen to your loudest user and the features they want. Due to time constraints, money, and the fact that it could make the design hard for other users to use. Hoekman at first says you should use an Activity Centered Design. You need to design for what a user is doing rather than what they claim they want in a design. This means that users don't always know what they even want in a design or how it would be set up. You need to create a good design that will be useful to them depending on the actions they are performing. Hoekman found that if you create a design based on specific group it makes it less useful for other groups of people. He later tells us that ACD is too narrow and that Situational-Centered Design is the way to go. A situation-centric approach means that you need to look at the different situations people are in and they could be using the same applications no matter their differences. For me, this means you need to help people with the everyday problems, or situations, that they're in to create a good design.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment