Jakob’s Ten Usability Heuristics

Visibility of System Status

The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time.

Why: Helps users learn the outcome of their prior interactions. Predictable interactions create trust in the product.

e.g., You Are Here maps, Checkout flow, Phone tap

Match between System and the Real World

The design should speak the users' language. Use words, phrases, and concepts familiar to the user, rather than internal jargon. Follow real-world conventions, making information appear in a natural and logical order.

Why: Ensures users can understand meaning without looking it up. Matches mental models around important concepts.

e.g., Stovetop controls, “Car” more conventional than “Automobile”, Shopping cart icon

User Control and Freedom

Users often perform actions by mistake. They need a clearly marked "emergency exit" to leave the unwanted action without having to go through an extended process.

Why: Allows users to remain in control of the system and avoid getting stuck or feeling frustrated.

e.g., Exit sign, Undo and redo, Cancel button

Consistency and Standards

Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions.

Why: Decreases cognitive load, people use platforms other than yours: includes internal consistency (within a single product) and external consistency (matching industry conventions)

e.g., Check in counter at hotel, “Delete” vs “Remove”

Error Prevention

Good error messages are important, but the best designs carefully prevent 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.

Why: Slips are unconscious errors caused by inattention (mismatch between user mental model and design). 2 types of errors: 1) slips 2) mistakes

e.g., Guard rails, Airline confirmation, Date selection on calendar (grey out unavailable options)

Recognition Rather than Recall

Minimize the user's memory load by making elements, actions, and options visible. The user should not have to remember information from one part of the interface to another. Information required to use the design (e.g. field labels or menu items) should be visible or easily retrievable when needed.

Why: Reduces the amount of cognitive effort required from users. Humans have limited short-term memories.

e.g., Lisbon question (Is Lisbon the capital of Portugal?), Comparison table (listing differences), Search (queries presented together with results as a reference)

Flexibility and Efficiency of Use

Shortcuts — hidden from novice users — may speed up the interaction for the expert user so that the design can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

Why: Allows flexibility; people can pick whichever method works for them since processes can be carried out in different ways

e.g., Shortcuts (on a map), Keyboard shortcuts, Tap to like

Aesthetic and Minimalist Design

Interfaces should not contain information that is irrelevant or rarely needed. Every extra unit of information in an interface competes with the relevant units of information and diminishes their relative visibility.

Why: Ensures the visual elements of the UI support the user’s primary goals; focuses on the essentials

e.g., Simple teapot over ornate (too many details), Communicate over decorate, Organized over messy UI

Help Users Recognize, Diagnose, and Recover from Errors

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

Why: Helps users notice and recognize errors using visuals

e.g., Wrong way sign, Internet connection error, No search results

Help and Documentation

It’s best if the system doesn’t need any additional explanation. However, it may be necessary to provide documentation to help users understand how to complete their tasks.

Why: Helps user execute task; should be concise, concrete in steps laid out, and easy to search

e.g., Airport information center, FAQ, Information Icon