When I first started reading chapter 3, I was a little confused because it did seem very contradictory to what he was saying before, but everything in chapter 3 was just as relevant and on point as any of the other chapters thus far.
So is the user always correct? No, although it seems strange at first, the chapter even stated sometimes the user wants more than they actually do. Hoekman then goes on to say that the user usually only learns a small amount of the app they are using, so it is hard to address whether they are "correct" or not. I also do not think that if one or a couple of people want a specific feature in the designers app, that the designer should put it in there. If the app is easy for everyone else, and everyone else is happy with the way it is, you would be risking upsetting everyone else based off of a couple people.
Larger than a "user-centered" focus, you could find yourself using a "situation-centric" focus. This is simply what is sounds, which is designing something for a person to figure out when they are in a specific situation. The strategy behind this method is that is does not limit you to one or a few persona's, but everyone. As Hoekman states in the book, it doesn't matter what the person is interested in or what they are like, because if they are in a certain situation, then everyone will be solving things in the same situation.
For project 2, we could have used this focus by putting our test subjects in a specific situation, seeing how they react to that situation, taken notes, and used those notes to design a new model that allows the user to solve that situation in an obvious way. This could be a very successful way to design something while pleasing many different kinds of people.
No comments:
Post a Comment