In Chapter 3 of designing the obvious, Hoekman talks about users needs and to answer the blog assignment question, the user is not always correct. The users' need's is what we should focus on by creating the personas in order to know what would be better for the product. We need to know what the user is trying to get out of the product in order to fully benefit from their input. Although the user may have their own ideas and perceptions of what they want the product to look like or do for them, they don't know exactly how to do that and the effect the changes might have on the product. Therefore every little piece of feedback from a user might now be worth changing on the product but you will be able to analyze how their feedback could help later.
In my team, I believe we used both a user centered and a situation-centric approach in redesigning our product. We changed some of the main things that our user said was troubling to them especially the ideas that we thought we were better for the design but we also didn't change a few things that our user said we might want to. He said the programs were pretty confusing but instead of clarifying the old situation we created a new way to sort through the programs. We didn't use his exact advice but we found a way to re-work the design to accommodate for theses problems.
Hi Lee,
ReplyDeleteEverything you say in your post is correct, and you definitely understand the basics of why sometimes it's important to "ignore the user". However, you don't answer all of the questions asked--you don't define what a situation-centric approach is or describe the approach that Hoekman advocates for. Your post also would've been strengthened by more examples from both the chapter and real life. Feel free to take a closer look at Chapter 3 and then extend your thoughts below.