.

KeywordDescriptionNemesisSource

.

ux-feedbackUser experience principle: interfaces should provide feedback about their current status. Users should never wonder what state the system is in.Nielsen

.

ux-implementation-levelUser experience principle: interfaces should not be organized around the underlying implementation and technology in ways that are illogical, or require the user to have access to additional information that is not found in the interface itself.Nielsen / Cooper

.

ux-jargonUser experience principle: users should not be required to understand any form of implementation level terminology. (This principle is a special case of ux-implementation-level).Nielsen (renamed from "match between system and the real world")

.

ux-controlUser experience principle: users should always feel like they are in control of their software. (This principle is often the nemesis of ux-interruption, especially in cases where developers assume users want more control than they actually want).ux-interruptionNielsen

.

ux-undoUser experience principle: actions should support undo so that users remain in control. (This principle is a special case of ux-control).New (split from control)

.

ux-consistencyUser experience principle: in general software should be internally consistent with itself, and externally consistent with similar interfaces to leverage the user's existing knowledge.Nielsen

.

ux-error-preventionUser experience principle: interfaces should proactively try to prevent errors from happening.Nielsen

.

ux-mode-errorUser experience principle: users should not encounter errors because the interface is in a different state than they expected it to be. (This principle is a special case of ux-error-prevention).New

.

ux-error-recoveryUser experience principle: interfaces should proactively help users recover from both user errors and technology errors. (A preferable case is to address through ux-error-prevention so that the error does not occur).Nielsen

.

ux-discoveryUser experience principle: users should be able to discover functionality and information by visually exploring the interface, they should not be forced to recall information from memory. (This is often the nemesis of ux-minimalism since additional visible items diminish the relative visibility of other items being displayed).ux-minimalismNielsen (renamed from "recognition rather than recall")

.

ux-efficiencyUser experience principle: interfaces should be as efficient as possible, minimizing the complexity of actions and the overall time to complete a task. Nielsen

.

ux-minimalismUser experience principle: interfaces should be as simple as possible, both visually and interactively. Interfaces should avoid redundancy. (This principle is often the nemesis of ux-discovery since removing or hiding items deep into the interface forces the user to rely more on memory than recognition).ux-discoveryNielsen

.

ux-interruptionUser experience principle: interfaces should not interrupt the user. Interfaces should never ask the user a question that they are not prepared to answer simply for a false sense of ux-control. In general software should only speak when spoken to.ux-controlNew

.

ux-toneUser experience principle: interfaces should not blame the user, or communicate in a way that is overly negative or dramatic.New

.

ux-natural-mappingUser experience principle: controls should be placed in the correct location relative to the effect that they will have.Norman

.

ux-affordanceUser experience principle: controls should visually express how the user should interact with them.Norman

.

ux-visual-hierarchyUser experience principle: controls that are more important or more commonly used should leverage visual variables such as size and contrast so that they have more dominance and weight relative to other controls. (This principle is an adaption of ux-discovery).New