About heuristics

A Heuristic is a generally recognized rule of thumb that helps to achieve usability.

Heuristics are used to:

  1. Prevent well-known usability problems by teaching the heuristics to designers.
  2. Find usability problems in interactive systems, for example by using them in a heuristic evaluation or a usability inspection.

Examples of heuristics: Speak the users’ language; Be consistent; Provide good error messages.

Heuristics are always used in sets of 8 to 20 heuristics.

Heuristics are sometimes confused with user interface guidelines.


A bit of history

The first set of heuristics was published by Rolf Molich and Jakob Nielsen in 1990.

A revised version of these heuristics was published by Jakob Nielsen in 1994. The revised version expanded the scope of the heuristics and described each heuristic in a compact and elegant way. I did not participate in the revision.

Quality criteria for sets of heuristics

1.  Generally recognized
A reliable set of heuristics has stood the test of time

2.  Comprehensible
A heuristic must be easy to understand.
Example: People tell me that the following heuristic is hard to interpret: “Match between system and the real world

3. Examples
A good set of heuristics comes with plenty of examples that translate the heuristics into everyday language. I recommend at least two examples per heuristic, ideally a software and a hardware example.

4.  Manageable
Limit yourself to a few, important heuristics. I recommend sets of 10 to 15 heuristics.

5. Simplicity
Each heuristic should address exactly one usability issue.
“Speak the users’ language” is a simple heuristic.
Match between system and the real world” is a complex heuristic. It can be decomposed into several simple heuristics, for example “Speak the users’ language”, “Follow real world conventions” and “Match the real world.”
Complex heuristics can be difficult to comprehend.