http://www.peterpixel.nl/writings/usability-testing-guidelines/ Sun, 05 Sep 2010 08:26:47 +0000 hourly 1 http://wordpress.org/?v=3.0.1 http://www.peterpixel.nl/writings/usability-testing-guidelines/comment-page-1/#comment-90 James Boekbinder Fri, 20 Apr 2007 10:45:03 +0000 http://www.peterpixel.nl/writings/?p=12#comment-90 In the above, I meant: just stop that test assignment, not 'stop the test' (the whole thing). In the above, I meant: just stop that test assignment, not ‘stop the test’ (the whole thing).

]]> http://www.peterpixel.nl/writings/usability-testing-guidelines/comment-page-1/#comment-89 James Boekbinder Fri, 20 Apr 2007 10:44:06 +0000 http://www.peterpixel.nl/writings/?p=12#comment-89 Very good start! A couple comments: - Don't interfere - No, I would not give them any hints. Only put a limit on the time they're allowed to struggle with it. If you have to give hints, the application has failed. Just stop the test and note the result. - Thinking out loud - this might be a good one to add. Remember that this is QUALITATIVE user testing, so asking the person to say what's going through their mind can reveal much more than their behavior otherwise would. For example, they might be succeeding in a task, but for entirely different reasons than the design thinks. Very good start! A couple comments:
- Don’t interfere – No, I would not give them any hints. Only put a limit on the time they’re allowed to struggle with it. If you have to give hints, the application has failed. Just stop the test and note the result.
- Thinking out loud – this might be a good one to add. Remember that this is QUALITATIVE user testing, so asking the person to say what’s going through their mind can reveal much more than their behavior otherwise would. For example, they might be succeeding in a task, but for entirely different reasons than the design thinks.

]]>