Blog Reflection 8
- What kinds of information and insights did it give you about the usability of the prototype?
User. Something that I already knew and experienced before, the library website is not that user-friendly. My task was to find a paper from a Journal. I tried to follow the steps from the evaluator but the main difficulty was to find which category architecture belong to. I believe having the most-used subcategories will be helpful, instead of trying to guess to which subject architecture belongs.
Evaluator. One insight that I found was that Websites have different ways or paths that get you to the wanted place. For instance, in the buy tickets task, there are different ways to do it. One of the easiest is to use the search bar that most pages have on the top-right corner. Unfortunately, most of the time, content is not well indexed and those kind of searches won’t work. As an evaluator I could notice the frustration my user had by this kind of issues.
- What aspects of the technique worked well or were frustrating?
User. As a user, thinking aloud helped me to get less frustrated and organise my thoughts before saying something. That helped me somehow to get the task done faster. On the other side, I felt slightly intimidated by my friend’s camera but after a while I forgot about it.
Evaluator. It helped me realise people have very diverse approaches for a problem. Before, I had never ‘evaluated’ the way a friend surfs the web. After doing so, I realised I would had taken a different direction. This was quite surprising, especially, considering the similarities we have in age and background. Hence, it is completely important to have a very diverse and wide range of user evaluations before launching a product.