Chapter 13 is all about how and why we evaluate our design. If we start with the ”Why, what, where and when”. We evaluate to make sure that the design meets the exact needs of the customer, that’s the number one priority. If this isn’t fulfilled our requirements might not been good enough or we just have to rethink the design. What we evaluate can be many different things, like how easy this product is to use compared to the other options available on the market. The first step of evaluation can take place in a laboratory to make sure that the requirements are met, then we can move on to a natural environment etc. When do we evaluate? If the design is a brand-new concept it has to be evaluated more often to make sure that it fulfills the user's requirements. Since our design isn’t a brand new concept I think we can get away with evaluating once, since we have a good idea of what the user requires by looking att similar designs on the market.
Case study evaluations take place in different settings with different amount of control. We could apply this by letting a person from our usergroup use our design to get from A to B and then ask how easy it was, if it was fun etc.
So this chapter basically goes through why it’s important to evaluate, and i completely agree with that statement, if you don’t evaluate you have no idea if the product reach the requirements.
Chapter 14 mentions different evaluation studies that take place in different settings, like controlled and natural. Usability testing is a type of evaluation which usually takes place in a controlled environment where you can measure the time it takes for a user to complete a task and how many errors was made etc. This is interesting to do so you can see how easy and effective your design is. Different kind of experiments can also be done to validate hypotheses etc.
Chapter 15 is about evaluation methods based on trying to understand the users by heuristics or via remotely collected data.
Heuristic evaluation is when a expert uses the interface and i guided by different usability principled know as heuristics. The expert can for example go through the process of adding a friend on a social network many different times to identify the usability problems.
I think that an expert roleplaying as a user is a great final step in evaluating to make sure that nothing is missing or misleading in the design.
Question: How do you decide if the design is good enough?