UX NIELSEN HEURISTICS METHOD

The system should always keep users informed about what is going on through appropriate feedback within a reasonable time.

The system should speak the users’ language, with words, phrases, and concepts familiar to the user, rather than system-oriented terms.

Users often choose system functions by mistake and will need a clearly marked “emergency exit” to leave the unwanted state without having to go through an extended dialogue.

Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.

Even better than good error messages is a careful design that prevents problems from occurring.

Make objects, actions, and options visible to minimize the user’s memory load. The user should not have to remember information from one part of the dialogue to another.

Accelerators, unseen by the novice user, may often speed up the interaction for the expert user, so the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

Dialogues should not contain irrelevant or rarely-needed information. Every extra unit of information competes with the relevant units of information and diminishes their relative visibility.

Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.

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.