Minimize the user's memory load by making 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.

The more users' expectations prove right, the more they will feel in control of the system and the more they will like it.

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.

Even the best designers produce successful products only if their designs solve the right problems. A wonderful interface to the wrong features will fail.

Information Overload = "information pollution"

Compared to 1999...we cannot quite declare victory, but we can declare progress.

Inadequate use of usability engineering methods in software development projects have been estimated to cost the US economy about $30 billion per year in lost productivity.