Study smarter with Fiveable
Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.
Jakob Nielsen's 10 usability heuristics aren't just a checklist—they're the foundation of every design critique, portfolio review, and user testing analysis you'll encounter. When you're asked to evaluate an interface or justify a design decision, these principles give you the vocabulary and framework to articulate why something works or fails. You're being tested on your ability to identify which heuristic applies to a given scenario and explain how it improves (or harms) the user experience.
Think of these heuristics as falling into three core categories: keeping users informed, giving users power, and reducing cognitive burden. Don't just memorize the names—know what problem each heuristic solves and be ready to apply them to real interfaces. When a design critique asks "what would you change?", these are your go-to diagnostic tools.
Users should never have to guess what's happening. These heuristics ensure the system communicates clearly and speaks the user's language.
Compare: Visibility of System Status vs. Match Between System and the Real World—both are about communication, but visibility focuses on what's happening now while real-world match focuses on how it's described. If a critique asks about confusing terminology, that's real-world match; if it's about missing feedback, that's visibility.
Great interfaces don't trap users—they empower them to explore confidently, knowing they can always recover from mistakes.
Compare: Error Prevention vs. Error Recovery—prevention stops mistakes before they happen (constraints, confirmations), while recovery helps after something goes wrong (clear error messages, suggested fixes). Strong designs need both layers. If an FRQ shows a frustrating error state, discuss which layer failed.
Users have limited mental bandwidth. These heuristics minimize the thinking required to use an interface effectively.
Compare: Recognition vs. Consistency—recognition is about making options visible so users don't have to remember; consistency is about making behaviors predictable so users don't have to relearn. Both reduce cognitive load but through different mechanisms.
Not all users are the same. These heuristics ensure interfaces work for beginners and experts alike while remaining clean and supportive.
Compare: Minimalist Design vs. Help and Documentation—these might seem opposed (less content vs. more support), but they work together. The interface itself should be minimal; help should be available but not intrusive. Good design reduces the need for documentation.
| Concept | Best Heuristics |
|---|---|
| Communication & Feedback | Visibility of System Status, Match Between System and Real World |
| User Empowerment | User Control and Freedom, Flexibility and Efficiency of Use |
| Error Handling | Error Prevention, Help Users Recognize/Diagnose/Recover from Errors |
| Reducing Mental Effort | Recognition Rather Than Recall, Consistency and Standards |
| Interface Clarity | Aesthetic and Minimalist Design, Help and Documentation |
| Beginner vs. Expert Needs | Flexibility and Efficiency of Use, Recognition Rather Than Recall |
A user accidentally deletes an important file and can't get it back. Which two heuristics failed, and how would you fix each?
You're reviewing an app that uses a unique icon system with no labels. Which heuristic does this violate, and what's the underlying principle?
Compare and contrast Error Prevention and Help Users Recover from Errors—when would you prioritize one over the other in your design?
A form shows "Error 4032" when users enter invalid data. Identify the violated heuristic and rewrite the message to comply with best practices.
An expert user complains that an interface is "too slow" even though it loads quickly. Which heuristic likely needs attention, and what features might you add?