Usability Review

By Karsten Erxleben, SAP AG, Usability Engineering Center

This paper is outdated.

Abstract

The Usability Review is an expert-oriented method where at least two usability experts perform tasks with the application to be reviewed from a user’s perspective. It is a economical and efficient method to identify weak points in the software. In this article a description is provided of how to apply this method successfully.

One way in which usability can be improved is by means of Usability Reviews. The Usability Review is an expert-oriented method where at least two User Interface Designers perform tasks with the application to be reviewed from a user’s perspective [1]. Every obstacle and problem encountered while solving the tasks is recorded, and these provide the input for a review session. At this session the problems and possible solutions are discussed with the development team. Since four eyes are better than two, two User Interface Designers should take part in the Usability Review process to deliver an even more sound and comprehensive input for the development team.

Process

Preparatory Discussion

The preparatory discussion is held between one User Interface Designer and at least one developer of the application to be reviewed. It provides a forum for determining the scope of the application to be reviewed, the date for the review session and who should be involved in the review process. A date is also set in the preparatory discussion by which the formulated tasks will be given to the User Interface Designers.

In order to prepare the review, the User Interface Designers need a written, goal-oriented description of the essential tasks to be undertaken using the software. The task should describe the intended outcome, not how to achieve it.

This means that the user and his/her tasks have to be known. Additionally, the context the tasks are performed in (for example, the shop floor or an office) has to be familiar to the development team. The description has to be delivered by the development team to the User Interface Designers.

Preparation

In the preparatory phase, the two User Interface Designers test the application independently of each other. They use the tasks provided, based on the user context that was discussed. Every problem and possible solution from the expert's point of view is recorded in a document. After task-oriented processing, the application should be tested again for possible general usability problems and these should be written down as well.

Carrying out the Review Session

During the Review Session the application is discussed by the development team, the User Interface Designers, and other attendees like product or quality manager on the basis of the noted usability problems, and obvious solutions are immediately recorded. Should a need for further discussion exist, colleagues will record this, hold further talks to find a solution to the problem or agree to a date for a design session.

In addition the priority of the problem should be recorded. A follow-up review date could be set if necessary in the light of the number and difficulty of the problems.

At the end of the review a transcript is made available to those present.

Debriefing or Follow-up Review

If you decide not to hold a follow-up review, the implemented solutions should be tested by the date set and the development team should be given feedback on the revised version. If a follow-up review does take place it is performed using the previously established task descriptions and the transcribed problems as input.

 

[1] The described process was influenced by the "Formal Usability Inspections" described in Kahn, Michael J., Prail, Amanda; Formal Usability Methods, in: Nielsen, Jakob, Mack, Robert L. (eds.): Usability Inspection Methods. New York, Chichester, Brisbane, Toronto, Singapore 1994. John Wiley & Sons.

 

To top top