1 / 7

HCI – Evaluating and Measuring Success

HCI – Evaluating and Measuring Success. From the user’s eyes…. Are your assumptions about what task your design is supporting correct? i.e. The meaning of an icon/button or a label? Will users notice what actions are available? Will they see a menu option or a particular button?

mariska-takacs
Télécharger la présentation

HCI – Evaluating and Measuring Success

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HCI – Evaluating and Measuring Success

  2. From the user’s eyes… • Are your assumptions about what task your design is supporting correct? i.e. The meaning of an icon/button or a label? • Will users notice what actions are available? Will they see a menu option or a particular button? • When they see a particular button will they recognise that it is the one required for the task? • Will users understand the feedback that they get. i.e please wait while the system checks your details?

  3. Using Schneidermans 8 golden rules Check your system offers, when necessary the following: • 1. Consistency • 2 Enables frequent users to use shortcuts. • 3 Offers informative feedback. i.e. Your booking is complete/confirmation printing etc • 4 Design dialog to yield closure. i.e. exit, home buttons • 5 Offer simple error handling. i.e. error messages/help button /undo buttons • 6 Permit easy reversal of actions. i.e. undo button/back button • 7 Support internal locus of control - A feeling that the user is in charge NOT the system, ease of use • 8 Reduce short-term memory load - Don’t make the user have to guess what to do next, ensure navigation clear i.e. drop down boxes, menu choices etc

  4. Ask the user’s opinion • Use Questionnaires • “open” (‘write what they want’ reply) or “closed” (answers “yes/no” or from a wider range of possible answers) • Avoid using ‘open’ if asking a large amount of users i.e. 100 or more • important to use specific, clear, comprehensive and unambiguous questions, quantified where possible • e.g., daily?, weekly?, monthly? Rather than “seldom”, “often” and there should always be a “never” • Allow an area for feedback – i.e. Comments area • Use feedback and questionnaires to revisit/ improve system

  5. Speed • How long do you want to allow for your task – For Example: I want the user to obtain the ticket price of the ‘Lee Mack’ concert on the 29 May 2011 • Target 1 minute • Will accept 1.5 mintues • Will revisit system if it takes more than 1.5 minutes.

  6. Keystrokes • How many touches of the screen or clicks of the mouse do you want to allow for your task – For Example: I want the user to obtain the location of the ‘Next’ store nearest to the stadium • Target 5 touches/clicks • Will accept 7 touches/clicks • Will revisit system if it takes more than 7 touches/clicks.

  7. Errors made • How many errors (i.e. use of the back button due to wrong choices of button/icon) do you want to allow for your task – For Example: I want the user to obtain the telephone number of the ‘Frankie and Benny’s near the stadium • Target 0 errors – info found first time • Will accept 1 • Will revisit system if it takes 2 or more incorrect choices of button/icon.

More Related