Professional Documents
Culture Documents
Risk reduction
Evaluation and early redesign reduces the risk that final UI design will not meet
users’ needs
Much less expensive to fix user interface problems during early project stages
Can avoid schedule slippage due to user interface changes late in the project
Frequency of occurrence
Impact if it occurs
One-time or persistent
Prevent errors
Match Between System and the Real World - The system should speak the user’s
language, with words, phrases and concepts familiar to the user, rather than system-
oriented terms. Follow real-world conventions, making information appear in a
natural and logical order.
Recognize Rather than Recall - Make objects, actions, and options visible. The user
should not have to remember information from one part of the dialogue to another.
Instructions for use of the system should be visible or easily retrievable whenever
appropriate
Aesthetic and Minimalist Design - Dialogues should not contain information which
is irrelevant or rarely needed. Every extra unit of information in a dialogue competes
with the relevant units of information and diminishes their relative visibility.
Help and Documentation - Even though it is better if the system can be used without
documentation, it may be necessary to provide help and documentation. Any such
information should be easy to search, focused on the user’s task, list concrete steps to
be carried out, and not be too large.