Golden Rules of Interface Design (2013)
Classic “golden rules” for interface design from the 1980s are being revisited in light of today’s software, hardware, and touch-first environments. Commenters largely agree that principles like consistency, error prevention, clear feedback, and low cognitive load still hold up, but emphasize they are heuristics, not absolutes, and must be balanced against real-world constraints, user expectations, and the need for expert workflows. The thread also contrasts different schools of HCI thought, criticizes trends like hidden or shifting controls and overemphasis on aesthetics, and highlights the enduring influence of early HCI research on modern UX.
Historical context & relation to other heuristics
- Several commenters note the rules predate more widely known frameworks (e.g., later usability heuristics) and use older terminology (“short-term memory load” vs. “cognitive load”).
- The endurance and overlap of these principles with later work is seen as evidence they captured something fundamental rather than being superseded.
- Some see irony in the original page’s old-style layout compared to more modern, digestible presentations of similar heuristics.
Consistency and expertise
- Strong support that consistency enables users to become “experts” in a product; patterns compound learning across features.
- Others warn that “consistency above all” is a trap: the real priority is matching user expectations and real-world mental models.
- Examples: inconsistent button behavior across screens, car touchscreens vs physical controls, RC controllers, Office vs its Ribbon redesign, and modal editors like Vim.
Error prevention, disabled controls, and feedback
- Disagreement over aggressively preventing input vs allowing errors with clear, immediate feedback.
- Many argue disabled actions are fine only if users can easily see why and how to enable them (tooltips, messages, status indicators).
- Hiding unavailable actions is widely criticized; gray-out is preferred to teach existence, location, and conditions.
- Persistent forms and localized error correction (not losing entered data) are emphasized as critical.
Aesthetics vs usability
- Long debate over whether interfaces should prioritize beauty or functionality.
- One side argues beauty reduces cognitive friction and should be integral.
- The opposing view insists safety, clarity, and ergonomics must trump aesthetics, citing skeuomorphic failures and complex domains like cockpits and financial tools.
Conceptual models, tools vs utilities
- Commenters stress that users must infer the product’s conceptual model from the UI; unclear domain concepts cause confusion regardless of labeling.
- Distinction made between “utilities” (should be ultra-simple and intuitive) and “tools” (can justify steeper learning curves for efficiency).
- Discussion of aligning implementation with a clean conceptual model rather than exposing internal quirks.
Performance, stability, and evolving UIs
- Poor performance and constantly shifting layouts are seen as violating almost all the rules in practice (smart TVs, Spotify, moving buttons).
- There’s resentment toward frequent, non-essential redesigns perceived as change for its own sake.
Additional suggested principles
- Don’t move interface elements unexpectedly.
- Support undo/history and reversible actions.
- Avoid mystery-meat navigation, unlabeled icons, and peek-a-boo controls.
- Provide customization and composability.
- “Don’t make me think” and “don’t design UX you yourself would find hostile” are proposed as overarching meta-rules.