UX Principles Study Guide

The 10 Usability Heuristics and Core UX Concepts from the Nielsen Norman Group
Tradition

Written as an original study companion. All explanations and examples are paraphrased and expanded in plain language; this
is not a reproduction of NN/g articles. For the official source material, courses, and research reports, visit [Link].

What this guide covers

• The 10 usability heuristics (Jakob Nielsen, 1994) explained with practical examples.
• How to run a heuristic evaluation — the method these heuristics are built for.
• Other core NN/g ideas: usability components, UX vs UI, user research basics, and interaction cost.
• How to use all of this in design reviews, portfolio case studies, and interviews.

UX Principles Study Guide Page 1

 1. Foundations: What Usability Actually Means
Usability is not a vague feeling of “easy to use.” Nielsen defines it through five measurable quality
components. If you can name these in an interview, you can also explain how you would measure a
redesign.

Learnability How quickly can a first-time user complete basic tasks? Measured with first-use
task success.

Efficiency Once users have learned the design, how fast can they perform tasks?
Measured with time-on-task.

Memorability When users return after a gap, how easily do they regain proficiency? Important
for occasional-use tools.

Errors How many errors do users make, how severe are they, and how easily can users
recover?

Satisfaction How pleasant is the design to use? Measured with attitude scales like SUS or
SEQ.

A related concept is utility: whether the product does what users need at all. Usefulness = utility +
usability. A beautiful interface for a feature nobody needs fails on utility, not usability.

Interaction Cost
Every action a user takes — reading, scrolling, clicking, typing, waiting, remembering — has a mental and
physical cost. Good design minimises the total interaction cost of reaching a goal. Many of the ten
heuristics below are really strategies for lowering this cost.

UX Principles Study Guide Page 2

 2. The 10 Usability Heuristics
These are broad rules of thumb for interaction design, first published by Jakob Nielsen in the 1990s and
still the most widely used checklist in UX. They are called “heuristics” because they are general principles,
not strict rules — applying them well requires judgement about context.

1. Visibility of System Status

Principle. The system should always keep users informed about what is happening, through timely and
clear feedback.

Examples.

• Progress bars during uploads; skeleton screens while content loads.

• A “saved” confirmation after editing a document.
• In a cart flow: showing item count and step position (“Step 2 of 3”).
How to apply it. Users lose trust fast when the interface goes silent. If an action takes more than about a
second, show feedback. If it takes long, show progress, not just a spinner.

2. Match Between the System and the Real World

Principle. Speak the users’ language. Use words, concepts, and conventions familiar to them, and
present information in a natural, logical order.

Examples.

• An e-commerce site says “Cart”, not “Item acquisition module”.

• A calendar app orders days the way people read a week, not alphabetically.
• Skeuomorphic cues where helpful: a trash icon for delete.
How to apply it. Internal jargon leaking into the UI is the most common violation. Card-sorting and user
interviews reveal the vocabulary users actually use.

3. User Control and Freedom

Principle. Users often act by mistake. Provide clearly marked emergency exits — undo, redo, cancel,
back — so mistakes are cheap.

Examples.

• Undo for a deleted email instead of a scary confirmation dialog.

• A visible ‘×’ to dismiss any modal; Esc works too.
• Multi-step forms let users go back without losing entered data.
How to apply it. Undo is stronger than confirmation. Confirmations get clicked through automatically;
undo lets people act fast and recover when needed.

UX Principles Study Guide Page 3

 4. Consistency and Standards
Principle. Users should not have to wonder whether different words, situations, or actions mean the same
thing. Follow platform and industry conventions.

Examples.

• Internal consistency: the same button style and label for the same action everywhere in your product.
• External consistency: search box at top, logo links to home, links look clickable.
• Following iOS/Android platform patterns in native apps.
How to apply it. Jakob’s Law sits behind this: users spend most of their time on other sites, so they
expect your site to work like the ones they already know.

5. Error Prevention
Principle. Better than good error messages is a design that prevents problems in the first place. Eliminate
error-prone conditions or check for them and ask for confirmation.

Examples.

• Date pickers instead of free-text date fields.

• Disabling “Submit” until required fields are valid — with clear inline guidance.
• Gmail warning you when you write “attached” but attach nothing.
How to apply it. Distinguish slips (unintended actions, e.g. fat-finger taps) from mistakes (wrong mental
model). Slips need constraints and good defaults; mistakes need clearer communication.

6. Recognition Rather Than Recall

Principle. Minimise memory load. Make objects, actions, and options visible; users should not have to
remember information from one part of the interface to another.

Examples.

• Autocomplete and recent-search suggestions.

• Showing the shipping address on the payment step instead of expecting users to remember it.
• Menus over command lines for infrequent tasks.
How to apply it. Human short-term memory is small. Every piece of information a user must carry across
screens is a tax; show it again instead.

UX Principles Study Guide Page 4

 7. Flexibility and Efficiency of Use
Principle. Accelerators — unseen by novices — let experts speed up. Allow users to tailor frequent
actions. Serve both inexperienced and experienced users.

Examples.

• Keyboard shortcuts alongside menus.

• Saved addresses and payment methods for repeat buyers.
• Bulk actions, templates, and customisable dashboards for power users.
How to apply it. This heuristic is why “simple” and “powerful” are not opposites: layer the power so
beginners never see it until they need it.

8. Aesthetic and Minimalist Design

Principle. Interfaces should not contain information that is irrelevant or rarely needed. Every extra element
competes with the relevant ones and reduces their visibility.

Examples.

• A landing page with one clear primary action, not five equal buttons.
• Progressive disclosure: advanced settings hidden behind “More options”.
• Content prioritised by user goals, not by internal org structure.
How to apply it. “Minimalist” means high signal-to-noise, not white space for its own sake. A dense
trading dashboard can satisfy this heuristic if everything shown earns its place.

9. Help Users Recognize, Diagnose, and Recover from Errors

Principle. Error messages should be in plain language, precisely indicate the problem, and constructively
suggest a solution.

Examples.

• “That email address is missing an ‘@’” instead of “Error 422: validation failed”.
• Highlighting the exact field that failed, preserving everything the user typed.
• A useful 404 page with search and links, not a dead end.
How to apply it. Never blame the user, never use codes alone, and never wipe their input. Recovery cost
is part of the error’s severity.

UX Principles Study Guide Page 5

 10. Help and Documentation
Principle. Best case: the system needs no explanation. When help is needed, it should be easy to search,
focused on the user’s task, list concrete steps, and stay short.

Examples.

• Contextual tooltips at the point of confusion, not a separate manual.

• Searchable help centre with task-based articles (“How do I refund an order?”).
• Onboarding that teaches by doing, then gets out of the way.
How to apply it. Documentation is a fallback, not an excuse. If a core flow needs a tutorial to be usable,
the flow is the problem.

UX Principles Study Guide Page 6

 3. How to Run a Heuristic Evaluation
A heuristic evaluation is an inspection method: evaluators examine an interface and judge it against the
heuristics. It is cheap, fast, and does not require users — which is also its limitation. It finds likely
problems, not proven ones.

Process
• Define scope. Pick the key user tasks and screens to evaluate. Do not audit “the whole product”
vaguely.
• Use multiple evaluators. A single evaluator finds roughly a third of problems; 3–5 evaluators working
independently find most of them. Evaluators inspect alone first, then merge findings.
• Walk through tasks twice. First pass for flow and feel, second pass to inspect each screen element
against the heuristics.
• Log each issue separately. One finding per issue, tagged with the heuristic it violates, the location,
and evidence (screenshot).
• Rate severity. Combine frequency, impact, and persistence into a 0–4 severity score (0 = not a
problem, 4 = usability catastrophe; must fix before release).
• Prioritise and recommend. Sort by severity, propose fixes, and separate quick wins from structural
changes.

Limits to state honestly

• It reflects evaluator judgement, not user behaviour. Pair it with usability testing when stakes are high.
• It over-detects minor cosmetic issues and can miss deep mental-model mismatches.
• It cannot tell you whether the product is useful — only whether it is usable.

UX Principles Study Guide Page 7

 4. Related Core Concepts Worth Knowing
UX vs UI vs Usability
User experience covers every touchpoint a person has with a product or company — before, during, and
after use. The UI is only the surface layer. Usability is one quality attribute of that surface. Conflating the
three in an interview signals shallow understanding.

Jakob’s Law
Users spend most of their time on products other than yours, so they prefer your product to work the same
way. Innovation in navigation and core patterns must clear a high bar of proven benefit.

F-Pattern and Scanning Behaviour

Eye-tracking research shows users scan rather than read on the web, often in rough F-shaped patterns on
text-heavy pages. Front-load headings and first words of paragraphs; do not bury key information
mid-sentence.

Progressive Disclosure
Show only what is needed for the current step; reveal advanced options on demand. This resolves the
tension between heuristic 7 (power) and heuristic 8 (minimalism).

Fidelity of Feedback — Response Time Limits

Rough rules: about 0.1 seconds feels instant; about 1 second keeps the flow of thought but the delay is
noticed; around 10 seconds is the limit of attention — beyond that, show progress and let users do other
things.

Discount Usability
You do not need big budgets to test. Small, frequent studies — around five users per round, paper or
low-fidelity prototypes — catch most serious issues early, when fixes are cheap. Iteration beats scale.

Severity Over Volume

A report with 60 unranked findings is noise. Ranked severity, tied to user tasks and business impact, is
what makes an audit actionable.

UX Principles Study Guide Page 8

 5. Putting It to Work
In design reviews and audits
• Structure findings by heuristic — it gives stakeholders a shared vocabulary and makes the critique feel
objective rather than personal taste.
• Always attach severity and a recommended fix. A violation without a fix is a complaint.
• Quote the heuristic’s intent, not its number. “Users get no feedback that the file uploaded” lands better
than “H1 violation”.

In portfolio case studies and interviews

• Use heuristics to justify decisions: “I replaced the confirmation dialog with undo because undo
preserves user control at lower interaction cost.”
• When asked to critique a screen live, walk the ten heuristics in order — it guarantees structured
coverage under pressure.
• Do not name-drop all ten. Pick the two or three that genuinely drove the decision and go deep.

Memorisation aid
Group the ten into three clusters: Keep users informed (1, 9, 10 — status, errors, help), Match how
people think (2, 4, 6, 8 — real-world language, consistency, recognition, minimalism), and Give users
power (3, 5, 7 — control, prevention, flexibility). Three clusters are easier to recall than ten items.

Go further: [Link] publishes the original heuristic articles, videos, and free research summaries. Their UX Certification
courses on “Usability Testing” and “Accessibility” are the highest-signal paid options if you want a credential.

UX Principles Study Guide Page 9