4- Grant Pendrey

Hoekman never steps away from the opinion that you are always designing for the users of the product/project/item. No matter what the decision, you must always make sure that in the end, your design is something that works for the user and improves their use in some way. However, he says in chapter three that the user is not always correct. For example, sometimes the is so close the product that their have "blinders" on and cant see what is truly wrong or a better solution. Other times a single design to better fit one user does is not always the best for all users as a whole. What is important when designing is to use different methods to understand the users needs and problems. Sometimes the users have possible solutions but that is not always the case. Once you can understand these issues, designing to better the interaction with a design can be focused on fixing these issues and evaluate your progress for better design.

As for project two, when looking at a "situation-centric approach"... Hoekman describes using specific tasks or situations to observe and understand how the users interacts with a design. One method that could have been better used by my team would be to actually interact with the design ourselves, identify some possible problems and add these tasks to our Use Case tasks. This would help to identify possible design flaws before starting our use case creating more focused design initiatives to research.