Writing Usability Specifications with ISO 9241-11

Download an aid to writing Usability Specifications

It seems that more and more people are discovering the merits of writing "Usability Specifications" based on ISO 9241-11. It has certainly worked for me. I'm happy to share my experience with you in the form of a Word 97 template that serves as a checklist and helps to speed up the development of a specification document. You can download the following documents (right-click and choose save method):

A Word 97/2000 template: 9241tmpl.dot

A completed example saved in Word 97/2000 format: UsabilitySpec.doc

Instructions for using the template

  1. Copy the template (9241tmpl.dot) into your Microsoft Office Template directory.
  2. Open Word, create a New document and choose the 9241tmpl template from the list.
  3. A new document appears with all the default content and a lot of variable information indicated by '<...>' (check out the Properties Bookmarks at the end of the template).
  4. Replace the <...> text, change the grey example text and save as a normal Word document.
  5. If you feel ambitious, you can now modify the Word document properties in either the template or individual documents. In this way you can set up defaults in the template, and can also make the completion of a document even faster by using a combination of properties and bookmarks. I have included a number of properties and bookmarks for you to modify (look at the last page of the template).

I recommend that you get hold of the actual ISO9241-11 standard (and also all other parts of ISO9241) and study it - it contains all of the background information that you won't find in my template. Also remember that my template is simply a checklist to help in developing a document on usability criteria and measures for a specific project. There is obviously a lot of heuristics behind it that is not explained in either the ISO standard or in my template

The Introduction in my template gives a brief explanation of the purpose and intent of a "Usability Specification" based on ISO9241-11. I have found that when such a document is drafted early in the project, it forms a vital link between HCI people and the rest of the project team. If done in collaboration with the team, it achieves the following:

  1. It helps to clarify assumptions about a lot of things (e.g. the user, the task, the environment, the conceptual nature of the application, the platform, etc.).
  2. It helps the usability engineer and system designer to argue about, and hopefully to eventually agree, about the right things!
  3. 3. It forms a frame of reference for early prototyping.
  4. Being a non-technical document, it is a lot easier for users and sponsors to digest. It tells them in clear terms what they must be able to do with the planned system for it to be regarded as a successful system.
  5. It helps to explain some of the complexities in, for example, the Functional Spec. and Technical Spec. to users.

Change the template in any way that makes it more useful to you. Word97 is really very powerful for this kind of thing. By using VBA I have streamlined my own version with macros and custom dialogs to automate and speed up several functions. I have done similar things with my Usability Test Report templates.

I welcome any suggestions for improving the template. (For example, several people have asked for an HTML version, which I'm working on at the moment.)

Jacques Hugo