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?

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?

Using Schneidermans 8 golden rulesCheck 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

Ask the user’s opinionUse 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 moreimportant to use specific, clear, comprehensive

and unambiguous questions, quantified where possiblee.g., daily?, weekly?, monthly? Rather than “seldom”,

“often” and there should always be a “never”Allow an area for feedback – i.e. Comments areaUse feedback and questionnaires to revisit/

improve system

SpeedHow 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 2011Target 1 minuteWill accept 1.5 mintuesWill revisit system if it takes more than 1.5

minutes.

KeystrokesHow 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 stadiumTarget 5 touches/clicksWill accept 7 touches/clicksWill revisit system if it takes more than 7

touches/clicks.

Errors madeHow 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 stadiumTarget 0 errors – info found first timeWill accept 1 Will revisit system if it takes 2 or more

incorrect choices of button/icon.