- Interviews/Observations: One-on-one sessions with users.
- Focus Groups: Often used in marketing well before there is any kind of prototype or product to test, a facilitated meeting with multiple attendees from the target user group.
- Group Review or Walk-Through: A facilitator presents planned workflow to multiple attendees, who present comments on it.
- Heuristic Review: Using a predefined set of standards, a professional usability expert reviews someone else's product or product design and presents a marked checklist back to the designer.
- Walk-Around Review: Copies of the design/prototype/wireframe are tacked to the walls, and colleagues are invited to comment.
- Do-it-Yourself Walk-Through: Make mock-ups of artifacts, but make the scenarios realistic. Walk through the work yourself.
- Paper Prototype Test: Use realistic scenarios but a fake product.
- Prototype Test: A step up from a paper prototype, using some type of animated prototype with realistic scenarios.
- Formal Usability Test: Using a stable product, an animated prototype, or even a paper prototype, test a reasonably large number of subjects against a controlled variety of scenarios.
- Controlled Experiment: A comparison of two products, with careful statistical balancing, etc
- Questionnaires: Ask testers to complete a formal questionnaire, or matching questionnaire.
In my prospectus, I suggested that only 4 of these usability methods would apply to the study of open source usability:
- Heuristic Review
- Prototype Test
- Formal Usability Test
In that post, I had an unspoken assumption that I would likely study an open source program of a suitable size, but one that had usability issues that needed to be uncovered and analyzed.
However, after a discussion with Eric Raymond, I wonder if it would be better to modify that assumption. Instead, I could study an open source program of a suitable size, one that was successful in addressing usability. The results of the case study wouldn't be a diagnostic review of the usability issues, but a summary of what works in open source usability.
The benefits to this kind of usability study are immediate to the open source community. In my experience, and that of Raymond, most open source programmers are more likely to imitate successful designs rather than apply the rigor of usability studies to their own programs. If my study is to benefit the open source community as a whole, I need to change how I approach the case study.
I'm not sure how to refer to this new kind of usability test. I don't recall seeing a name for it in the literature. It seems very similar to a Heuristic Review - except that the results identify positive design ideas rather than identifying usability issues for a designer to correct. In a different framework, this is the first half of a "plus/delta" exercise (where participants identify what works and what needs improvement). In that respect, it's also similar to the method of Questionnaires. But I still think it's a different thing.
Perhaps a good name for this is an "Usability Analysis," which adequately and simply describes the method. I'll use that name for now, until someone points out a more correct description.