Heuristic evaluation Functionality: Visual Design: Efficiency: Learnability: Navigation Feedback Accessibility Consistency Simplicity Flexibility Robustness Intuitiveness Responsiveness:
Heuristic evaluation Functionality: Does the site have compelling and unique content and will users understand the value proposition Visual Design: Will the design engage customers, with readable fonts and colors that work well together Efficiency: Can customers complete common tasks quickly with minimal scrolling and clicking
Heuristic evaluation Learnability: Are the terms used for navigation items and hypertext links unambiguous and jargon-free Navigation: Is the information that customers are most likely to need easy to find from the home page Feedback: Are error messages in plain language with clear instructions on what to do next
Heuristic evaluation Accessibility: Is the site designed for all customers, including the over 50’s and those with disabilities Consistency: Is terminology and conventions consistent with general (web) usage Refers to the language, format and behavior of the application. Consistency enhances the predictability of a system and makes it easier to learn
Heuristic evaluation Flexibility: Allows each user to tailor the system for his or her needs, style and task. This can mean allowing a user to perform a task in more than one way or the ability to store a user profile with defaults reflecting user preferences. Such customization gives the user a sense of control and can improve productivity
Heuristic evaluation Robustness: Seeks to minimize the opportunity for errors and allows the user to recover gracefully from a mistake. Provides an easy way out of an unwanted choice
Heuristic evaluation Intuitiveness: Intuitive interfaces build on conventions and user experiences to provide natural mappings and present information in a natural and logical order. The best interfaces use familiar concepts and language
Heuristic evaluation Responsiveness: Refers to the need to keep users informed. This includes an awareness of where the user is within the framework of an application and acknowledging user requests through appropriate feedback within a reasonable timeframe
Heuristic evaluation Simplicity: Allows the user to perform tasks in as few steps as possible. A simple interface does not confuse a user by presenting too many choices. Simplicity also limits cognitive demands
Heuristics Mental Workload Matches Intended User Population Consistency Page Architecture Navigation/Structure System Performance User Interaction
SUS -system usability scale 1. I think that I would like to use this system frequently 2. I found the system unnecessarily complex 3. I thought the system was easy to use 4. I think that I would need the support of a technical person to be able to use this system 5. I found the various functions in this system were well integrates
SUS -system usability scale 6. I thought there was too much inconsistency in this system 7. I would imagine that most people would learn to use this system very quickly 8. I found the system very cumbersome to use 9. I felt very confident using the system 10. I needed to learn a lot of things before I could get going with this system
Usability evaluation Due 10/18/09
Conduct a usability evaluation Web site of your choice If ambitious do a product comparison Evaluation of competing web sites Social networking, dating, shopping Power point presentation Must be submitted via hard copy
Usability evaluation report Product's) tested Tasks, features and scenarios that were evaluated Why were these chosen Difficulty, importance. Frequency, competitive advantage Who did you test and why User group description Number of people used in evaluation
Usability evaluation report Evaluation methodology used Heuristics Performance testing Criterion measures Satisfaction Subjective ratings of usability Task completion Number of error Usability test administration and data analysis procedure
Usability evaluation report Usability finding Overall summary of usability results What worked What didn’t What changes should be implemented to improve usability Would it have been helpful to perform this usability test prior to product release Why or why not