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

My favourite method of usability test is Thinking-Aloud. The thinking aloud methodology is inviting the user to a lab one at a time, and presenting the user with a series of critical task that most frequently used for the site, such as “order a cake on next Friday”. The task should take several pages to complete. The user needs to verbalize their thoughts through the whole process.

The key thing for think aloud is that we don’t focus on the intermost thinking or the opinion of the website or application. It is more concern about the task they are doing and their behavior. This method is to define the gap between the way people thinking and they way they interact with the site.

What aspects of the technique worked well or were frustrating?

The thinking aloud method works really well. It is very efficient and effective. Designer are involved in the testing, which is very helpful for understanding the feedback. Also we dont need to do a huge amount of testing, just 5 people is good enough to reveal hidden problems. It helps the design process iterate faster.

The good thing is if we focus on opinion, we need to analyze the huge amount of data to get useful insight. But thinking aloud is focusing on behavior. So it is meaningful and practical feedback.

 

Advertisements