Thanks Ron.

Another question for the list...

Do you think it is possible to conduct a usability test without
asking users the reason why they acted in a certain way, such as by
not asking any follow up questions?

What do you feel is the benefit of follow-up, if any?


--- In houstonhfes@yahoogroups.com, Ron Vutpakdi <vutpakdi@...> wrote:
>
> I think that it is hard to distill success or failure into a simple
one dimensional scale/score that always works.  Yet, presenting to
management, a single score would help make things more
understandable. 
>
> There ought to be several dimensions (say on a 3 or 5 point
scale): 
> success or failure
> how long things tookhow much the user struggled
>
> Maybe also add how important the task is?
>
> That maps (in some ways) to how I prefer to rate usability issues
and how we rate software bugs:
> how important is the issue
>
> how often does the issue come up
> how long might the issue take to fix
>
>
>
> You could sum up the the scores on the individual parts into a
total score.
>
> Maybe the key is to come up with a single score, but also to
represent to back up the score with an explanation. 
>
> Ron
>
======================================================================
======
> Ron Vutpakdi
> vutpakdi@...
>