Heuristic Evaluations

Conducting a heuristic evaluation can be a cost effective and relatively quick way to asses the usability of your site. They can be conducted by a usability expert or, failing that, you can apply sets of tried and tested heuristics yourself. The most well known set of heuristics are Jakob Nielsen’s:

  • Visibility of system status: The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
  • Match between system and the real world: The system should speak the users’ language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
  • User control and freedom: 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. Support undo and redo.
  • Consistency and standards: Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
  • Error prevention: Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
  • Recognition rather than recall: Minimize the user’s memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
  • Flexibility and efficiency of use: Accelerators—unseen by the novice user—may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
  • Aesthetic and minimalist design: Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
  • Help users recognize, diagnose, and recover from errors: Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
  • Help and documentation: 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.

Another good resource is Userfocus, who have a useful Excel spreadsheet containing a list of recognised usability guidelines. It presents a series of statements about your website against which you are asked to score points on a sliding scale. The points are collated and displayed in a neat visual which illustrates the usability of your site against their specific guidelines.

A heuristic evaluation should not replace user testing, and should not be confused with it either. The evaluation is more of a sanity check. And as with everything there’s always going to be an edge case, whereby applying one of the heuristics may have a negative effect on the user experience.

The simple fact of the matter is that UX without actual user testing is not UX. So while you will rarely do any harm by applying simple tried and tested heuristics, you will never understand your users without user testing. There’s a fantastic article by Hoa Loranger on this very subject, and it should be given to every company executive who really wants to build UX into their process but is reluctant to cough up for user testing.

 

Continue Reading

Steve Krug’s Usability Test Script

It’s the ‘go to’ test script. I’m pasting it here for quick reference.

There’s also a PDF version.

 
Introduction

Hi _________ . My name is _______, and I’m going to be walking you through this session.

You probably already know, but let me explain why we’ve asked you to come here today: We’re testing a web site that we’re working on to see what it’s like for actual people to use it.

I want to make it clear right away that we’re testing the site, not you. You can’t do anything wrong here. In fact, this is probably the one place today where you don’t have to worry about making mistakes.

We want to hear exactly what you think, so please don’t worry that you’re going to hurt our feelings. We want to improve it, so we need to know honestly what you think.

As we go along, I’m going to ask you to think out loud, to tell me what’s going through your mind. This will help us.

If you have questions, just ask. I may not be able to answer them right away, since we’re interested in how people do when they don’t have someone sitting next to them, but I will try to answer any questions you still have when we’re done.

We have a lot to do, and I’m going to try to keep us moving, but we’ll try to make sure that it’s fun, too.

You may have noticed the camera. With your permission, we’re going to videotape the computer screen and what you have to say. The video will be used only to help us figure out how to improve the site, and it won’t be seen by anyone except the people working on the project. It also helps me, because I don’t have to take as many notes. There are also some people watching the video in another room.

If you would, I’m going to ask you to sign something for us. It simply says that we have your permission to tape you, but that it will only be seen by the people working on the project. It also says that you won’t talk to anybody about what we’re showing you today, since it hasn’t been made public yet.

Do you have any questions before we begin?

Background information questions

Before we look at the site, I’d like to ask you just a few quick questions. First, what’s your occupation?

Good. Now, roughly how many hours a week would you say you spend using the Internet, including email?

How do you spend that time? In a typical day, for instance, tell me what you do, at work and at home.

Do you have any favorite Web sites?

Now, finally, have you bought anything on the Internet? How do you feel about buying things on the Internet?

And what have you bought?

OK, great. We’re done with the questions, and we can start looking at things.

Usability test

First, I’m just going to ask you to look at this page and tell me what you think it is, what strikes you about it, and what you think you would click on first.

For now, don’t actually click on anything, just tell me what you would click on.

And again, as much as possible, it will help us if you can try to think out loud so we know what you’re thinking about.

From this point it’s up to you. Ask them to consider the elements of the site and ask for their verbal feedback every step of the way.

 

Text excerpted from “Don’t Make Me Think” by Steve Krug.

Continue Reading