I'd be happy to elaborate -- and I'd love feedback, as this is something I'm
always trying to streamline and improve.
I try to identify the items under investigation ahead of time, so that I can
mark up a prewritten test script during the test. My usability tests are often
short and target a small number of issues, so that the results are manageable
and my DHTML-based "moving mockups" can keep up with the expected variations
they'll need to handle. I'd rather perform three short tests than one unwieldy
one.
Here's what a sample moderator script looks like. Notice that the expected
problem areas are identified ahead of time, with space for notes. It's much
faster for me to work from my notes, and they're essential if I can't record
the session for any reason.
1. Please log into the system using username: ME and password: PW.
[Clock stops when they click Log In. Time: ____]
[Username typo? Y/N]
[Password typo? Y/N]
[Clicked the correct button on first try? Y/N]
2. Please create a new login for John Smith.
[Clock stops when they click Save at the end. Time:____]
[Correct navigation? Y/N -- If N, where to first?_____]
[Required fields entered? Y/N -- If N, which weren't?_____]
[Default password >6 char? Y/N]
I hope that helps.
-Sarah
-----Original Message-----
Could you explain further how you take those measures. e.g. how do you
take time for tasks (whole tasks, parts...?), what other metrics you
look into, how you measure success ("yes/no", "yes but...", etc.
Thanks!
Sarah Kampman escribió:
> Though I take notes, I rely more heavily on quantitative measures when
> assessing the results of a usability test. All of the tasks I have
> participants complete have degrees of success, and often a time
> component as well. These measures lend themselves to comparison and
> analysis in a way that quotes do not. This is important for me, as
> usability testing only part of what I do, and I don't have the time to
> write out transcripts. The easier & faster I can make analysis, the
> better.
>
> As for the comments that I record, they fall into two categories:
> marketing and feedback. The "marketing" quotes are used to make a point
> internally, often to help position a change/enhancement as meaningful to
> a particular persona. The "feedback" quotes I use to fix whatever was
> problematic in the usability test, and I'll typically have my mockups up
> in Dreamweaver as I go through the feedback notes so that I can make the
> needed changes immediately.
>
> -Sarah Kampman
>
>
> -----Original Message-----
> I'm trying to find a better way to do usability test analysis.
>
> My current approach is: after i finish a usability study, with 8 or 10
> users, and collected my own and all observers' notes, I usually read all
> notes and then immediately write down the issues I feel area appearing
> more often (assuming my brain will remember issues that are repeated in
> many notes more than issues than appear only once).
>
> Now, how do YOU approach analyzing those notes? Reading and re-writing
> by heart? Putting all notes on a wall and eye-balling? Tagging the text
> with some piece of software?
>
--
Guillermo Ermel
Responsable de usabilidad
MercadoLibre.com
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [EMAIL PROTECTED]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
