Textbook of Usability

Introduction

The quantitative models of the preceding chapters — the MHP, GOMS, Fitts's Law — predict specific aspects of human performance with precision. But interface design involves thousands of decisions that cannot each be subjected to formal modelling. Heuristics — broad principles derived from experience and research — provide guidance for the full range of design decisions. This chapter covers three influential heuristic frameworks: Nielsen's 10 usability heuristics Nielsen, 1994, Shneiderman's 8 golden rules Shneiderman, 1987, and Norman's design principles Norman, 2016. Each distils decades of research and practice into actionable guidelines. They overlap substantially — unsurprisingly, since they draw on the same body of cognitive psychology — but each offers a distinct perspective.

Nielsen's 10 Usability Heuristics

Jakob Nielsen's heuristics Nielsen, 1994, published in 1994, are the most widely used framework for usability evaluation. Originally developed through a factor analysis of 249 usability problems Nielsen, 1990, they were refined into 10 principles that collectively cover the most common categories of usability failure.

1. Visibility of System Status

The system should keep users informed about what is happening through appropriate feedback within reasonable time. Progress bars, loading indicators, confirmation messages, and status displays all serve this heuristic. The user should never have to wonder whether the system received their input or whether a process is still running.

2. Match Between System and the Real World

The system should speak the users' language, using familiar words, phrases, and concepts rather than system-oriented jargon. Information should appear in a natural and logical order. This heuristic encompasses terminology, mental models, and metaphors. A "shopping cart" on an e-commerce site matches the real-world concept; a "buffer queue" does not.

3. User Control and Freedom

Users often perform actions by mistake. They need clearly marked "emergency exits" — undo, cancel, back — to leave unwanted states without having to go through extended processes. This heuristic is frequently violated in setup wizards that provide no way to go back, in destructive actions without confirmation, and in systems where the only way to correct an error is to start over.

4. Consistency and Standards

Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions and internal consistency. Consistency reduces learning time and recall demands by allowing users to transfer knowledge from one part of the system to another. It operates at multiple levels: visual consistency (consistent use of colours, fonts, and spacing), functional consistency (the same gesture always produces the same type of result), and external consistency (following platform conventions).

5. Error Prevention

Good design prevents problems 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.

6. Recognition Rather Than Recall

Minimise 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 interface to another. This heuristic derives directly from the recognition-recall distinction in memory research (Chapter 3) Craik, 1972. Menus, toolbars, breadcrumbs, and recently-used lists all support recognition over recall.

7. Flexibility and Efficiency of Use

Accelerators — unseen by the novice user — may speed up interaction for the expert. Allow users to tailor frequent actions. Keyboard shortcuts, macros, customisable toolbars, and configurable defaults all serve this heuristic. The challenge is supporting expert efficiency without complicating the novice experience.

8. Aesthetic and Minimalist Design

Dialogues should not contain information that is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units and diminishes their relative visibility. This heuristic is grounded in the cognitive load research of Chapter 3 Sweller, 1988: extraneous information consumes working memory capacity and competes for attention. It does not mean "make it look sparse" — it means every visible element should serve a purpose.

9. Help Users Recognise, Diagnose, and Recover from Errors

Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.

10. 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, and not be too large.

Shneiderman's 8 Golden Rules

Ben Shneiderman's golden rules Shneiderman, 1987, first published in 1986, predate Nielsen's heuristics but overlap significantly. They emphasise consistency, control, and reduced memory load.

1. Strive for Consistency

Consistent sequences of actions should be required in similar situations. Identical terminology should be used in prompts, menus, and help screens. Consistent colour, layout, capitalisation, fonts, and so on should be employed throughout.

2. Seek Universal Usability

Recognise the needs of diverse users: novices and experts, varying ages and abilities, different cultural backgrounds. Features such as explanatory tooltips for novices and keyboard shortcuts for experts serve diverse users within the same interface.

3. Offer Informative Feedback

For every user action, there should be system feedback. For frequent and minor actions, the response can be modest (a subtle highlight). For infrequent and major actions, the response should be more substantial (a confirmation dialog, a success message).

4. Design Dialogs to Yield Closure

Sequences of actions should be organised into groups with a beginning, middle, and end. Informative feedback at the completion of a group of actions gives users the satisfaction of accomplishment, a sense of relief, and a signal to prepare for the next group.

5. Prevent Errors

Design the system so that users cannot make serious errors — for example, grey out inappropriate menu items, constrain input fields to valid ranges, and require confirmation for destructive actions.

6. Permit Easy Reversal of Actions

Actions should be reversible wherever possible. This feature relieves anxiety (the user knows they can recover from mistakes) and encourages exploration (the user is more willing to try unfamiliar features if they know they can undo).

7. Keep Users in Control

Experienced users want the sense that they are in charge of the interface and that the system responds to their actions. Surprising system-initiated actions, confusing data entry sequences, and inability to produce desired results all erode the user's sense of control.

8. Reduce Short-Term Memory Load

The limitation of human working memory requires that displays be kept simple, multiple-page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.

Norman's Design Principles

Don Norman, in The Design of Everyday Things [Norman, 1988; Norman, 2016], articulated principles that apply to all designed objects, from physical products to software interfaces.

Affordances

An affordance is a relationship between the properties of an object and the capabilities of the agent that determines how the object could be used Gibson, 1979. A flat plate on a door affords pushing; a handle affords pulling. In interface design, a button that appears raised affords clicking; a slider affords dragging.

Signifiers

Signifiers are perceivable indicators of affordances — they tell the user where to act and what to do. A button label is a signifier. An underlined text colour is a signifier for a hyperlink. Signifiers are often more important than affordances in design because they communicate the designer's intention to the user.

Mapping

Mapping is the relationship between controls and their effects. Natural mapping exploits spatial correspondence: a row of switches that maps left-to-right onto a row of lights, or a scroll bar where dragging down moves the content down (or up, depending on convention — the inconsistency itself illustrates the importance of mapping).

Feedback

Every action should produce an immediate, informative, and perceptible response. The delay between action and feedback should be minimised. Feedback should be non-intrusive for routine actions and more prominent for significant ones.

Constraints

Constraints limit the actions that are possible, preventing errors. Physical constraints (a USB plug that only fits one way) prevent incorrect insertion. Logical constraints (greyed-out menu items) prevent selection of invalid options. Cultural constraints (red means stop) provide conventional guidance.

Conceptual Models

A conceptual model is a simplified explanation of how something works. Good designs communicate a clear conceptual model that allows users to predict the system's behaviour. The desktop metaphor — files, folders, trash can — provides a conceptual model for file management that maps onto familiar physical-world concepts.

Comparing the Frameworks

The three frameworks overlap substantially but differ in emphasis:

• Nielsen focuses on evaluating existing designs — the heuristics were developed as criteria for heuristic evaluation (Chapter 16).
• Shneiderman focuses on designing new interfaces — the golden rules are formulated as design guidance.
• Norman focuses on understanding why designs succeed or fail — the principles explain the psychological mechanisms behind good and bad design. In practice, all three frameworks are used both for evaluation and design. Their overlapping coverage provides confidence: a design that violates a principle in one framework is very likely to violate a principle in another.

From Heuristics to Evidence

Heuristics are not a substitute for empirical evidence. They represent accumulated wisdom and common patterns of usability failure, but they cannot predict with certainty whether a specific design will work for specific users in a specific context. The strongest design practice combines heuristic guidance (to make informed initial design decisions and catch common problems early) with empirical methods (usability testing, A/B testing, analytics) to validate and refine designs with real users. The chapters in Part IV cover these empirical methods.