Practical Heuristics for Usability Evaluation

Practical Heuristics for Usability Evaluation
Based on: Perlman, G. (1997) Practical Usability Evaluation. Based in part on Nielsen's 1993 Heuristics and Norman's 1990 Principles. \| About quest.cgi

Please rate the system using the heuristics.

Try to respond to all the items.
For items that are not applicable, use: NA
Make sure these fields are filled in: System: Email to:
Add a comment about an item by clicking on its icon, or add comment fields for all items by clicking on Comment All.
To mail in your results, click on: Mail Data

System: Email to:

Optionally provide comments and your email address in the box.

RETURN TO REFERRING PAGE

LEARNING 1 2 3 4 5 6 7 NA
1. Help and Documentation
Design for use without documentation. Provide easy-to-use task-oriented help bad good
2. Adopt the User's Viewpoint
Speak the user's language (avoid jargon). Make use of existing knowledge (familiar mental models). bad good
3. Simple and Natural Dialogue
Avoid extraneous information, steps, actions. Information should be in a logical, natural order. bad good
4. Design for Advancement
Provide shortcuts (quick keys, customization). bad good
ADAPTING TO THE USER 1 2 3 4 5 6 7 NA
5. Provide Maps and a Trail
Give the user a way to preview where to go, what will happen. Give the user a way to review / return-to previous contexts. bad good
6. Show the User What is (Not) Possible
Provide affordances to indicate what can be done. bad good
7. Intuitive Mappings
Design good response compatibility between controls/actions. bad good
8. Minimize Memory Load
Remove the need to remember across dialogues. Provide multiple views for easy comparisons. bad good
9. Consistency in the System and to Standards
Make sure the same term/action has one meaning. When there is no better way, conform to a standard. bad good
FEEDBACK AND ERRORS 1 2 3 4 5 6 7 NA
10. Feedback
Provide timely feedback about all processes, system status. bad good
11. Prevent Errors
Make it difficult to make errors. bad good
12. Error Messages
Diagnose the source and cause of a problem and suggest a solution. bad good
13. Clearly Marked Exits and Error Recovery
Make sure the user can get out of an undesirable state easily. Design assuming that people will make errors and need to recover previous states. bad good
1 2 3 4 5 6 7 NA

List the most negative aspect(s):

List the most positive aspect(s):

Top of Form | RETURN TO REFERRING PAGE

LEARNING			1	2	3	4	5	6	7		NA
1.	Help and Documentation Design for use without documentation. Provide easy-to-use task-oriented help	bad								good
2.	Adopt the User's Viewpoint Speak the user's language (avoid jargon). Make use of existing knowledge (familiar mental models).	bad								good
3.	Simple and Natural Dialogue Avoid extraneous information, steps, actions. Information should be in a logical, natural order.	bad								good
4.	Design for Advancement Provide shortcuts (quick keys, customization).	bad								good
ADAPTING TO THE USER			1	2	3	4	5	6	7		NA
5.	Provide Maps and a Trail Give the user a way to preview where to go, what will happen. Give the user a way to review / return-to previous contexts.	bad								good
6.	Show the User What is (Not) Possible Provide affordances to indicate what can be done.	bad								good
7.	Intuitive Mappings Design good response compatibility between controls/actions.	bad								good
8.	Minimize Memory Load Remove the need to remember across dialogues. Provide multiple views for easy comparisons.	bad								good
9.	Consistency in the System and to Standards Make sure the same term/action has one meaning. When there is no better way, conform to a standard.	bad								good
FEEDBACK AND ERRORS			1	2	3	4	5	6	7		NA
10.	Feedback Provide timely feedback about all processes, system status.	bad								good
11.	Prevent Errors Make it difficult to make errors.	bad								good
12.	Error Messages Diagnose the source and cause of a problem and suggest a solution.	bad								good
13.	Clearly Marked Exits and Error Recovery Make sure the user can get out of an undesirable state easily. Design assuming that people will make errors and need to recover previous states.	bad								good
			1	2	3	4	5	6	7		NA