Pioneered by the Nielsen Norman Group, the 10 Usability Heuristics are basic observation criteria used to evaluate computer software for potential usability issues. The primary advantage of Heuristic Evaluation (HE) is that it can add value at any point in the design's life cycle.
UX Usability Heuristics
Scott C. Krause | Friday, Mar 19, 2021
#1: 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.
#2: 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.
#3: 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.
#4: Consistency and standards
Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions.
#5: 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.
#6: 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.
#7: Flexibility and efficiency of use
Shortcuts — hidden from novice users — may speed up the interaction for the expert user such that the design can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
#8: Aesthetic and minimalist design
Interfaces should not contain information which 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.
#9: 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.
#10: 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.
Transition to TypeScript
Indispensable Curated TypeScript Links
The Clandestine Dead Drop
The Ironclad Clandestine Dead Drop
New Macbook Setup for Developers
New Macbook Config for Devs 2021
UX Usability Heuristics
HE Heuristic Evaluation
Curated Blogfolios Links
Curated Emerging Tech Links
Indispensable Curated Tech Links
Cytoscape Skills Data Visualization
Persuasive Infographics & Data Visualizations
eCommerce Accessibility A11y
Accessibility Challenges Unique to eCommerce
Roll Dice in High-Fidelity 3D
Create 3D Dice with Strong Random Entropy