When using the Top-Down approach to log results from user testing, place them under the following categories.
- Clarify the core concepts
Does the design match the user’s mental model (e. g., the desktop metaphor)? - Fit content to customers who use the product
Does the content fit the user’s expectations? Is the information organized or mapped properly and at the right level for the audience? Are there any missing parts? - Plan and maintain consistency
Is there consistency from program to program (external consistency and within a program (internal consistency)? - Provide reassuring feedback
How does the system provide feedback or information to the user (dialog boxes, time to complete tasks etc.)’? - Clarify interaction rules
Does the system follow a standard set of rules For interacting with the product from a design point of view (e.g, drag and drop or buttons)? - Structure navigation clearly
Does the user understand how to get from point A to point B (menu, icon, keyboard use)? - Use plain terminology
Does the language match the user’s own vocabulary of use? - Optimize user assistance
Can users get help when they need it (on1ine help or performance support)? - Optimize visual design
Is the ‘visual design effective and pleasing (e.g,, do radio buttons look like radio buttons; are icons intuitive in design? - Design for the context of use
Can the product he used as designed (are there “bugs” in the system that prevent it or is the context of use poorly conceived
taken from: Barnum, Carol. “Usability Testing and Research” p159. Also, see http://www.t2i.se/pub/papers/SpaceLab_Usability_Evaluation.pdf for real life usage of this.
Advertisement
Posted in: Uncategorized
August 1st, 2010 → 3:59 pm
[...] Test: Screen users to put them in the right subgroup before the test. Debrief them about the whole process. Observe them as they complete the test and do post-task and post-test questionnaires. (Further Reading: Pre-Test Briefing, Thinking-Out-Loud Procedure, Categories for logging test results) [...]