Human Factors Primer
In a previous post, I wrote about the importance of usability in traffic intersection design and how this fits nicely into producing good quality documentation. In this post in the series, I provide a quick primer in Human Factors. I use the example from my last post. If you have not read that post, I recommend doing so now before continuing.
Human Factors Primer
Here are a few on human factors issues that go into designing and developing good products:
Visibility of system status - the system should always keep the users informed about what is going on through appropriate feedback. With our traffic light example, the placement of the traffic lights across the intersection allow the user to be kept informed of the status of the intersection at all times.
Match between system and the real world - The system should speak with words, phrases and concepts familiar to the user, not system-oriented terms and phrases. A traffic light that uses green to stop, blue to go would be a mismatch to what people expect these colours suggest, at least in the western world.
User control and freedom - Provide a clearly marked “emergency exit” to cancel or undo a task. With a stop line far enough back from the pedestrian crossing and the traffic light across the intersection, a user has sufficient time to be aware of traffic and pedestrian conditions and stop, or cancel, proceeding if a pedestrian is crossing in front of the car or if the intersection is not clear.
Consistency and standards - Words, situations, or actions should always mean the same thing. Follow conventions. Imagine if every intersection had different rules. It would be maddening for drivers. In fact, this is often the case that intersections are designed inconsistently and drivers must learn quickly a new set of rules upon approaching the stop line. If they don’t quickly catch on, other drivers who do know are happy to inform them of their “supposed stupidity” with a blaring horn or worse.
Error prevention - a careful design is better than good error messages. Prevent a problem from occurring in the first place. Consider again our example. Simply moving the traffic light across the intersection solves a number of problems in advance. I often hear error messages at intersections here in Berlin. Drivers of the cars stopped at the stop line are doing what they should do – keeping aware of the status of the intersection. But as they cannot also keep an eye on the traffic light, they do not proceed when the light turns green. Hence, the drivers in cars behind offer their own error messages in the form of a blaring horn and often an additional hand signal to reinforce the error message.
Recognition rather than recall - Make objects, actions and options visible. User should not have to remember information from one part of the dialogue to another. Users should not have to remember the status of the intersection when their attention is off it to learn the status of the traffic light. They should be able to see the status of the intersection at the same time as seeing the status of the traffic light.
Flexibility and efficiency of use - Accelerators, unseen by the novice, speed up interaction for expert users. (All levels of users.) If you know that the traffic lights on a street are synchronized to a certain driving speed, an expert driver will maintain that speed to enjoy a constant stream of green lights. A novice will charge from traffic light to traffic light and get red lights almost every time.
Aesthetic and minimalist design - Dialogues contain no irrelevant information. No extra “noise.” Imagine a traffic light with advertisements on it. What relevance does an advertisement for a soft drink have to do with a traffic light? It might be a cool thing to add a pixel board above every traffic light to let a driver enjoy a clever advertising campaign. After all, the driver is just sitting there staring at the light. Why not add a small tasteful bit of information, such as the location of the nearest gas station or fast food outlet. It is noise and would distract from the main task at hand, which is keeping aware of traffic conditions and knowing when it is safe to proceed.
Help for users in recognizing, diagnosing and recovering from errors - Error messages should be expressed in plain language (not codes), indicate the problem and suggest a solution. In multi-lingual Europe, having all signs in English wouldn’t make much sense. Symbols that are universally recognized are, therefore, often used. The three colours of a traffic light are recognized universally and so satisfy plain language requirements. But often traffic signs are not so recognizable and a small phrase or word should accompany the sign so users can learn the “code’ of the sign. An arrow leading off a highway is often accompanied by an “ausfarht”, or “exit’ sign to distinguish it from a sign indicating the upcoming direction of the highway.
Help and documentation - Any information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large. Well, in the case of driving, size really does matter. That is, the size of the sign should make it visible from a distance (such as over a lane so cars way back in the line can clearly see the traffic light). You should not have to search for the traffic light. It should carry concise information that is focused on the task at hand. For instance, a traffic light should not also include pedestrian signals.
Good resources on Human Factors are readily available through a Google search. My favourite is the Human-Computer Interaction Resource Network run by Thomas Wolfmaier, human factors specialist in Toronto, Canada.