Nielsen’s 10 usability heuristics
The foundational principles for evaluating and improving any digital interface, explained with modern examples
In 1994, Jakob Nielsen published ten general principles for interaction design. Three decades later, they remain the most widely used heuristic evaluation framework in the industry. They are not rigid rules but broad guidelines that help identify usability problems without running user tests.
This guide walks through all ten heuristics with examples from current products, explains how to spot violations in your own interfaces, and offers criteria for prioritising fixes.
What is a heuristic evaluation?
A heuristic evaluation is a usability inspection method in which one or more evaluators examine an interface by comparing it against a set of recognised principles. It does not require real users, making it a fast and cost-effective technique for catching design issues early.
Nielsen and Molich demonstrated that three to five evaluators can identify roughly 75 % of a product’s usability problems. Each evaluator goes through the main flows, noting where the interface violates a heuristic and assigning a severity rating.
- It is an expert inspection method, not an end-user test
- It can be run on prototypes, mockups or live products
- Three to five evaluators are enough to cover most issues
- Each finding is classified by severity: cosmetic, minor, major or catastrophic
System status visibility and real-world match
The first heuristic states that the system should keep users informed about what is happening through appropriate feedback within a reasonable time. When you upload a file to Google Drive, the progress bar and "Uploading… 45 %" message confirm the action is moving forward. Remove that indicator and the user has no idea whether the file uploaded, failed or is still processing.
The second heuristic asks the system to speak the user’s language, not the developer’s. Airbnb doesn't say "Enter the check_in_date parameter" — it says "Check-in". Stripe doesn't show HTTP error codes; it shows readable messages like "Your card was declined: insufficient funds". Matching the real world also means using metaphors and visual conventions the user already knows.
- Loaders, progress bars and confirmation states eliminate uncertainty
- Use vocabulary from the user’s domain, not development terminology
- Icons should represent recognisable concepts: a bin for delete, a padlock for security
User control, consistency and error prevention
The third heuristic argues that users need a clearly marked "emergency exit". Gmail lets you undo a sent email for a few seconds, avoiding irreversible consequences. Figma offers unlimited version history so any change is reversible.
The fourth heuristic — consistency and standards — requires that identical elements behave identically throughout the interface. If a blue button means "primary action" on one screen, it must not mean "cancel" on another. Apple and Google publish design guidelines (Human Interface Guidelines, Material Design) precisely to guarantee this coherence across apps.
The fifth heuristic goes beyond error messages: it is about designing so the error never occurs in the first place. Forms that disable the submit button until all required fields are filled, or date pickers that grey out past dates when irrelevant, are examples of effective prevention.
- Always offer the option to undo, go back or cancel
- Keep colours, typography, labels and interaction patterns consistent
- Use real-time validation and input constraints to prevent errors before they happen
Recognition, flexibility and minimalist design
The sixth heuristic — recognition over recall — states that users should not have to remember information from one screen to the next. Search autocomplete, breadcrumb navigation and recent-action histories all apply this principle. Amazon shows "Recently viewed" and "Inspired by your history" so users don't need to recall what they searched for yesterday.
The seventh heuristic calls for flexibility and efficiency. Interfaces should work well for novices and power users alike. Keyboard shortcuts in Figma (Ctrl+D to duplicate, Ctrl+Shift+K to insert an image) speed up the advanced user without complicating the beginner’s experience — they can still use the menus.
The eighth heuristic advocates for aesthetic, minimalist design. Every additional visual element competes for the user’s attention. The most effective interfaces strip away noise and prioritise information relevant to the task at hand. Notion employs a clean aesthetic where content dominates and controls only appear on hover.
Error recovery and documentation
The ninth heuristic states that error messages should be expressed in plain language, pinpoint the problem and suggest a constructive solution. GitHub shows "We couldn't find that page" alongside a search bar and links to the homepage, instead of a bare "404 Not Found". An empathetic tone and alternative paths turn a dead end into a chance to redirect the user.
The tenth heuristic acknowledges that while the ideal system needs no documentation, help should be available when needed. Notion’s tooltips, Stripe’s contextual help centres and Figma’s interactive walkthroughs are examples of documentation embedded in the product — accessible at the right moment without breaking the workflow.
- Errors should explain what went wrong in human language and offer a fix
- Documentation should be contextual, searchable and get to the point fast
- FAQs, tooltips and interactive guides flatten the learning curve without cluttering the interface
How to run a heuristic evaluation on your project
To run an effective heuristic evaluation, select three to five evaluators with usability knowledge. Each one independently walks through the main flows, noting every heuristic violation they find, the screen where it occurs and a severity level from 0 (cosmetic) to 4 (catastrophic).
The team then consolidates findings, removes duplicates and prioritises fixes. Severity 3-4 issues are blockers that must be resolved before launch. Severity 1-2 issues can be scheduled for later sprints. The process can be repeated after each design iteration to verify that fixes resolve the detected problems without introducing new ones.
- Define the critical flows to evaluate (onboarding, checkout, search…)
- Each evaluator works independently to avoid group bias
- Consolidate findings into a severity × violated heuristic matrix
- Repeat the evaluation after applying fixes to measure progress
Key Takeaways
- Nielsen’s heuristics are a fast, cost-effective framework for spotting usability problems
- Three to five evaluators can identify roughly 75 % of issues
- Error prevention is more effective than error messages
- Visual and functional consistency reduces the user’s cognitive load
- Each finding should be rated by severity to prioritise fixes
Want to evaluate your product’s usability?
We run heuristic evaluations and usability tests to identify the issues holding your users back. Clear diagnosis, prioritised improvements.