Based on the readings from Hoekman I get the sense that the user is not always correct. They point out that the user may know what they want but they won't always go to that design. When users introduce new features they don't always work. There was an example where Hoekman talks about designing web pages. The user may want different features in some kind of new webpage but the reality is that the user will always go back t their usual websites. This is because this is what the user is used to using day in and day out and there isn't a real need to change what they do. This also brings up the point that maybe a designer shouldn't just focus on what the user wants and needs. Lets face it the designer is a user on some level also. The designer knows just as much as the user in some instances on what features or changes to a design can make it better. The designer can look at a design and think of features outside of the box where a user is just focused on what they want.
With the situation-centric approach I think it is saying that the designer needs to look at all possibilities in every situation. The designer should be looking at every aspect in order to help their design be the best. With this in mind I feel like I could have used more of the situational immersion on my Project #2. I was so concerned with what my use case person wanted and what they struggled with then what I though of the design myself. I feel like if I could have focused some more of the design on what I also though were problems and how I could fix them I could have combined that with what the user thought. Being able to put your own input into your design I feel like can definitely help especially if you have experience wit that design or you know how it works.
No comments:
Post a Comment