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

My user was doing the “Buy tickets” task. From the “thinking ” of the user, it seems that it went very fluently. She did look for information, which were not giving to her straight away. However, they all didn’t take a long time for her to figure out where to look for what she wants. She didn’t have much changing in facial expressions from the video that we recorded, as the whole process is quite user friendly and are the normal habit that people have. So my conclusion is the prototype is structured very well and definitely did lots of user testing in order to make it fit to most people’s habit.

  1. What aspects of the technique worked well or were frustrating?

Using the “Think-aloud” technique, it is much easier to learn about where the user hesitated or were not clear enough. If only user test on user and ask for feed back by user, there will be some points that the user didn’t notice which is important for the developer. As a designer, getting to know which part annoys the user the most and by the words they were using, we can figure out how disappoint they are to the procedure. The frustration is most users are not used to this kind of technique and are easily forget to speak out what he/she is thinking about.

Advertisements