Nielsen Heuristics: the 10 usability rules

The Nielsen Heuristics are 10 general usability principles that guide the design of digital interfaces, used to evaluate websites and applications and find user experience problems. Created by Jakob Nielsen with Rolf Molich in 1990, they remain a central reference in interaction design.

• What are the Nielsen Heuristics?
• What are the 10 Nielsen Heuristics?
• The 10 heuristics explained with real examples
• How does a heuristic evaluation work?
• Heuristic evaluation or user testing: which to choose?
• Conclusion

What are the Nielsen Heuristics?

The Nielsen Heuristics are 10 general usability rules that work as a checklist for designing and evaluating user interfaces. Jakob Nielsen developed them in 1990 in collaboration with Rolf Molich and refined them in 1994 from a factor analysis of 249 usability problems, according to the Nielsen Norman Group.

The official material explains the name: "they are called "heuristics" because they are broad rules of thumb, not specific usability guidelines", defines the Nielsen Norman Group. In the review published in 2020, the group updated examples and explanations, but kept the same 10 principles — a strong indication of the set longevity.

These heuristics cover aspects such as clarity in communication, consistency, flexibility, and feedback. Any frontend or UX (User Experience) designer team can apply them without special tools: just know the principles and inspect the interface with discipline.

What are the 10 Nielsen Heuristics?

The 10 Nielsen Heuristics, in the Nielsen Norman Group official numbering, are:

1. Visibility of system status — the user should know what is going on, with immediate feedback.
2. Match between system and the real world — the interface speaks the user language, not the system.
3. User control and freedom — clear emergency exits, such as undo and cancel actions.
4. Consistency and standards — the same elements have the same behavior across the product.
5. Error prevention — prevent the problem before it happens.
6. Recognition rather than recall — visible options, without requiring the user to memorize screens.
7. Flexibility and efficiency of use — shortcuts for the experienced, simplicity for the novice.
8. Aesthetic and minimalist design — no irrelevant information competing for attention.
9. Help users recognize, diagnose, and recover from errors — clear error messages with a solution.
10. Help and documentation — accessible support when the interface alone is not enough.

The 10 heuristics explained with real examples

Each heuristic becomes more concrete when observed in products you use every day. The examples below show hits — and one classic miss — from well-known platforms.

1. Visibility of system status

Status visibility ensures the user knows exactly where they are and what comes next. YouTube does this well: it clearly shows which video is playing, the progress bar, and what is next in the queue.

2. Match with the real world

The interface should speak the user language, using icons, colors, and text that make sense off the screen. The use of the color red to indicate destructive actions or errors, for example, is almost universally understood.

3. User control and freedom

User control means freedom to navigate, undo, and go back without punishment. The lack of an edit button is the classic error of this heuristic: old versions of the Facebook app did not allow editing a comment after posting, and Twitter (now X) spent years allowing only deleting a tweet, with no edit option.

4. Consistency and standards

Consistency requires the same element to look and work the same way across the platform. If a button performs a specific action on one screen, the user expects the same behavior on any other.

5. Error prevention

Preventing an error is better than fixing it. Google is the classic example: it offers search suggestions and real-time spell corrections, preventing the user from even submitting a search with a typo.

6. Recognition rather than recall

Recognition reduces memory load: the user should not have to remember information from one screen to use it on another. "Breadcrumbs" (navigation trails) are a great example, as they show the path taken without mental effort.

7. Flexibility and efficiency of use

Flexibility serves both novices and experienced users in the same interface. Trello, for example, lets you operate boards with the mouse or with keyboard shortcuts, speeding up the work of those who already master the tool.

8. Aesthetic and minimalist design

Minimalist design works on the principle that less is more: irrelevant information confuses and competes with what matters. Keeping the layout clean and focused is a product decision — and today there are even AI (Artificial Intelligence) tools for design that help with this direction.

9. Help with error recovery

When the error happens, the platform should help the user understand and fix the problem with clear messages. Spotify does this well in its signup forms, pointing out exactly which field failed and how to resolve it.

10. Help and documentation

Help and documentation are the final safety net. The ideal is for the interface to be intuitive enough to dispense with them, but keeping accessible, easy-to-search documentation remains good practice in any product.

How does a heuristic evaluation work?

A heuristic evaluation is a usability inspection in which experts walk through the interface and record each violation of the 10 principles. The Nielsen Norman Group recommends that 3 to 5 evaluators analyze the product independently, because no single evaluator — however experienced — finds all the problems.

The basic process follows these steps:

1. Define the scope of the evaluation: flows, screens, and tasks that will be inspected.
2. Recruit 3 to 5 evaluators and align the understanding of the 10 heuristics.
3. Walk through the interface individually, recording each problem and the violated heuristic.
4. Consolidate the findings of the evaluations into a single list, with a severity rating.
5. Prioritize fixes and validate the most critical ones with real usability tests.

Heuristic evaluation or user testing: which to choose?

Use both methods at different moments: heuristic evaluation is fast and cheap for inspecting the design; user testing validates real behavior. In the article Why You Only Need to Test with 5 Users (2000), Jakob Nielsen showed that a single participant reveals on average 31% of usability problems — and that 5 participants reach about 85%.

The two methods add up to a broader quality culture, in line with what we discuss in the importance of software testing.

Conclusion

The 10 Nielsen Heuristics remain the most cost-effective usability checklist there is: they are free, applicable to any technology, and have survived three decades of web change. Before launching or updating any platform, go through the list — at CodeCrush we treat usability as a project requirement, not as final polish. Those who build software with a user focus from the start rarely need to redo the interface afterward.