For each of 2 techniques (user observation, thinking-aloud)
- What kind of information and insights did it give you about the usability of the prototype?
User observation and thinking-aloud recording form provide me with a wholesome angle to recording users’ experience and understand users’ needs, i could detect it from verbal behavious with each individual positive and negative comments, which could be considered as a strongly intension, while non-verbal behaviours recording was more helpful in detecting tiny confusion from users’ expression, the confusion might not influence the mission execution however need more time to carry out the process, which could be considered as a deficient in terms of usability that need to be improved.
What aspects of the technique worked well or were frustrating?
Both the techniques worked well, because they could reflect users’ experience from different perspective. In terms of feasibility, however, user observation could reflect more useful information than thinking-aloud when the process being carried out.
Thinking-aloud method could help understand user’s latent needs whereas another method could detect more about explicit needs. The former technique requires high quality of users’ cooperation, that is to say, it is totally depend on users’ own values and previous experience, it is hard to maintain the observing course to the fullest, so it could receive less information than another one, however it reflect subjective perspectives, so it could somehow figure out latent needs based on users’ genuine and original intention.
Moreover, user observation could help collecting detailed insights which strait -forward point to the designer’s demand. Designers could find certain answers to the problems they want to collect, because user observation data comes from users, and then filtered from designers, different designers might have different observation key-findings towards one tester. Therefore from my point of view, this approach could gather information directly.