Description of the room, including camera equipment used to record the actions and words of the evaluator Description of the observers, either in the room or behind a one-way mirror in the control room. If the observers are in the room, they should be briefly introduced (first names will do) Explanation of the product being… [Read more…]
August 1, 2010
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… [Read more…]
August 1, 2010
Quantitative Data: Time to completion of each task Number of participants completing tasks within allocated time Number of participants completing tasks with extra time Number of problems encountered Number of errors (unsuccessful tries) Number of local problems Number of times each participant uses “help” menu Number of times each participant accesses advertising sites Length of… [Read more…]
July 31, 2010
First impressions (look and feel of the product) First tasks (so important in fixing in users’ minds whether they will consider the product easy or difficult to use) Tasks most frequently performed Critical tasks (even if performed less frequently) Specific problem areas (typically identified by sponsor or heuristic evaluation) New tasks added to a product… [Read more…]
July 31, 2010
Motivation – how motivated are users to use the product? Typing skills – critical for some jobs Task experience – familiarity with the task that the product supports Turnover rates – high turnover rates would indicate that ease of learning issues is critical General education Learning style Computer background Software applications used Expected training support… [Read more…]
July 31, 2010
Design It is the idea of the product transformed into a blueprint, yet it is still abstract. Build a Prototype It is the first tangible model of the product and extremely important as testing cannot begin without it. Ranging from paper prototypes to interactive web pages, choose the level of fidelity that takes the least… [Read more…]
July 31, 2010
Tech-Ed, a usability consulting firm, proposes the following 12-step design process: Design site Develop prototype (fidelity levels, M. Shrage’s heuristics) Perform heuristic evaluation (& cog walkthru p158 C Wilson) Incorporate feedback into alpha site Perform usability test of alpha site (focus groups, surveys, tech support, http://ablongman.com/barnum/pdf/bladefinalreport.PDF test plan, scenarios, walkthru, pilot, ) Incorporate feedback into… [Read more…]
July 10, 2010
Lab Testing With Lab: put subject in a separate room with one-sided glass and record his reactions to the product Without Lab: observe subject from a distance and mark down his reactions to the use of the product. Could also ask him to be verbose. Field Testing Structured Observation: observe subject in his home Longitudinal… [Read more…]
June 28, 2010
Elegance & Simplicity Principles: Unity, Refinement, Fitness Techniques: Reduction determine essential qualities (adjectives) critique each element (does it relate to the essence of the design?; would design suffer without it? remove if non-essential) remove essential elements & see effect (if still essential, think of replacements) Regularization use regular geometric forms, simplified contours & muted colors… [Read more…]
June 27, 2010
Do less features, but do them well. Even if its less marketable, satisfied users will spread the word and will be more loyal customers. Paul Grice’s (1967) Cooperative Principles for Conversation: Quantity Quality Relevance Manner Respect Physical Effort Treat Clicks as Sacred Remember Where they put things (& where they were) Remember What They Told… [Read more…]
August 1, 2010
1