Blog Reflection 8

 

What kinds of information and insights did it give you about the usability of the prototype?

While observing the user you were able to identify what areas of the design they found confusing or got stuck on. By watching facial expressions you are able to gain an understanding of the users feeling towards various elements of the website that they may not be saying out loud as they are using the interface. With the thinking out loud portion the user is able to give direct feedback about what they find frustrating and is able to talk you through how they are navigating the interface. This can help you identify what the user was expecting to do at a certain point and if that expectation was met, thus allowing you to get a better idea of how the user would behave when interacting with a certain design.

 

What aspects of the technique worked well or were frustrating?

Given how many things are needing to be done at once (recording, watching facial expressions, listening to users thoughts, watching how user interacts with the interface, ect…) it is easy for important information to get ‘lost in the crowd’. This is alleviated with the recording but its difficult to have one person, for example, record both what the user is doing on the screen and their facial expressions. Users may often act abnormally when they know they are being recorded and have to talk through their actions which may lead to the information collected not being realistic. Overall I think most aspects of the technique work well, in particular the ‘thinking out loud’ aspect as users are able to directly air their frustrations and by talking through what they are doing you learn how they would typically approach this sort of interface.

Advertisements