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; and consistent commands should be employed throughout.
← All guidelines
Shneiderman - 8 Golden Rules of Interface Design
Ben Shneiderman rules from text Designing the User Interface.
Ben Shneiderman's 8 Golden Rules of Interface Design, introduced in his seminal 1986 textbook Designing the User Interface, are the canonical rules for consistent, predictable interaction. Where Nielsen's heuristics describe usability in broad strokes, Shneiderman's rules zoom in on the micro-mechanics: consistency across screens, meaningful feedback after every action, shortcuts for power users, reversible operations, and informative error messages.
Teams reach for Shneiderman's 8 when the product is already functional but feels rough — buttons behaving differently across screens, actions with no confirmation, errors without a clear next step. The rules are especially useful for admin tools, enterprise applications, and any data-heavy interface where expert users are doing the same task hundreds of times a week.
Run an evaluation against Shneiderman's 8 in parallel with Nielsen's 10 for broad coverage, or on its own when you suspect the issue is less about discoverability and more about the interaction model itself.
2. Enable frequent users to use shortcuts
As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
3. Offer informative feedback
For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
4. Design dialog to yield closure
Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
5. Offer simple error handling
As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
6. Permit easy reversal of actions
This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
7. Support internal locus of control
Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
8. Reduce short-term memory load
The limitation of human information processing in short-term 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.
Other
Compare with another guideline
Side-by-side comparison
Nielsen's 10 vs Shneiderman's 8
Nielsen's 10 heuristics vs Shneiderman's 8 golden rules: where they overlap, where they diverge, and which to use for a UX heuristic evaluation. With Heurio.
Side-by-side comparison
Dieter Rams' 10 vs Shneiderman's 8
Dieter Rams' 10 principles audit a designed object's character; Shneiderman's 8 golden rules guide how to design interactive systems. Side-by-side, with Heurio.
See it in action
Shneiderman's 8, on a live URL, in one click.
Click anywhere on a real page, drop a heurio, pick the Shneiderman's 8 rule it violates. No screenshots, no Loom, no separate doc.