The Thinking Aloud Method
The basic idea of the thinking aloud method is simple:
users perform a test task, and talk about what they are
trying to do, what questions they have, what they read, etc.
- Users need instructions, like "Tell me what you are thinking about
as you work".
- You may need to remind the user to keep talking, but you should not
ask specific questions.
Comments like "Tell me what you are thinking" and "Keep talking" are
good, but "Why did you do that?" is not, because it sounds like you are
reprimanding the user.
- You can take notes of what the user is saying, or you can videotape it.
Taking notes takes some practice, to keep up with the user.
- From the notes or videotape you make a list of all difficulties
users encountered. (Include links to the original notes.)
- By comparing hou you thought the interface would work
with the test results you should be able to rethink the design.
It is important to have several test users to get an idea whether an error
one user makes will be a common error or not.
- Thinking aloud may make users more conscious about their actions
than they would normally be. They may make more errors in a more casual
setting.
- Take into account that users will sometimes say things that make
no sense or are just plain wrong.
An interesting test is to show someone two identical objects and make them
explain what they think is different.
Virtually noone will say the objects are identical.