Usability Heuristic Assessment


Usability Heuristic Assessment

Picture of Luís Filipe

Luís Filipe

Managing Partner YouX

The importance of usability evaluation

When developing new interfaces or products, usability is a critical success factor and should not be left to the discretion of the development team. Their experience with the interface or product tends to be very different from that of its potential future users. What is seen as simple and intuitive for the former tends to be complex for users who normally do not have the same level of involvement and knowledge of the area in question. The result of ignoring the latter tends to be failure.

It is for this reason that more and more companies and organizations are aware of the need to evaluate the usability of the solutions they intend to develop in order to ensure that they will be used effectively and with pleasure by their potential users.

However, usability evaluation tends to be neither simple nor quick and, moreover, it tends to be expensive. It is in this context that heuristic usability evaluation has proven to be an excellent option. It does not replace the use of methods, techniques and tools from the UX domain . However, due to the speed of its implementation, the systematization it allows and the results it provides, it is a good way to evaluate the usability of a product or interface design. Additionally, it combines well with other tools such as Personas or User Journey.

What does the Usability Heuristic evaluation consist of?

Heuristic evaluation uses UX experts with knowledge in the field to which the interface or product whose usability is intended to be evaluated belongs. These experts select a set of heuristics from which they will create a checklist of criteria that will allow them to find flaws and inconsistencies that escape the design and development teams. Due to its characteristics, heuristic evaluation translates into a practical way of solving problems and helping with decision-making.

Each member of the expert team will perform tasks independently, record usability issues and which heuristic violations occur, and then rate each issue in terms of severity. 

To classify severity, a severity table is used.

The Norman-Molish heuristics

There are several heuristics, but we would not be far from the truth if we say that the 10 Norman-Molisch are the best known.

In short, we can say that the Nielson-Molisch heuristics postulate:

1) Keep users informed about their status in an appropriate and fast way.

2) Show information in a way that users understand using the example of how the real world works and the users' language.

3) Give users control and let them undo mistakes easily.

4) Be consistent so that users don't get confused about what different words or icons mean, for example.

5) Prevent errors – a system should avoid conditions where errors arise or warn users before they take risky actions (e.g. “Are you sure you want to do this?” messages).

6) Have information and instructions available that allow users to recognize options, actions, etc., rather than forcing them to rely on their memory.

7) Have the flexibility to allow experienced users to find faster ways to achieve their goals.

8) Avoid confusion by limiting the available information to only what is relevant to the specific tasks that the user is performing.

9) Provide help using simple language about errors and their solutions.

10) List the steps in simple, searchable documentation that helps overcome problems.

The pros and cons of heuristic usability evaluation

Heuristic evaluation is a method that has great potential for evaluating usability. However, like other methods, it also has its pros and cons.

How a heuristic evaluation is conducted

Heuristic evaluations provide indications about where the problems will be, suggesting some options that will allow corrections.

Key Points:

  1. Knowing what we are going to test and how – whether it is a complete product or just procedures, we must clearly define the parameters we want to test and the objective.
  2. Knowing the users and having a clear idea of ​​the target objectives, contexts, etc. – personas and user journeys can help in this process.
  3. Select 3 to 5 evaluators – ensuring their expertise in both the industry and usability.
  4. Define the heuristics (normally no more than 10) – this will depend on the nature of the system/product/design to be analyzed. Using adaptation of the Nielson-Molish ones, adding others that are relevant, is a good principle.
  5. Define the checklist for each heuristic.
  6. Brief evaluators on what should be covered in a selection of tasks and suggest a severity scale that helps flag and prioritize problems.
  7. First step – Allow evaluators to use the software freely so that they can identify the problems to be analyzed.
  8. Second step – evaluators examine the individual elements according to the heuristics, also checking how they interact in the overall design and recording the problems found.
  9. Interrogate the evaluators in a session so that they can group the results obtained for analysis and suggest corrections.

What you will find in the evaluation report

The purpose of the usability heuristic evaluation report is to identify the main problems found in the product or interface and serve as the basis for a discussion on how to overcome them.

By its nature, this report will tend to call into question aspects of the work of the design and development team that project stakeholders promoted and defended. For this reason, it is important that there is a face-to-face presentation of the report.

Aspects taken into account::

  • As with any project, do not go beyond the scope (of the report).
  • reinforce authority by presenting the CVs of the authors (experts).
  • include the heuristics and checklists used and demonstrate their support.
  • include a simple summary of the main problems identified as well as an indication of the time and resources needed to resolve them.
  • list and describe the identified problems ordered according to their severity (severity scale)
  • for each of the identified problems, present recommendations that allow their resolution.
  • Add program screens of problems to help identify and understand them.

Are you developing new interfaces or products or looking to improve existing solutions? Check out our services.

You cannot copy content of this page

Skip to content