UI/UX Design Basics for MarketersUX foundations for marketers · Lesson 2 of 21

The 10 usability heuristics in practice

Article · 10 min · 9 min lecture

Video lecture

The 10 usability heuristics in practice

12 chapters · about 9 min · full transcript

Coming soon

Chapter 1 of 12

The 10 usability heuristics

  • Tap, nothing happens, tap again
  • Ten principles from Jakob Nielsen
  • Run a review and score severity

The narrated lecture is in production

Every chapter is scripted and ready. Browse the chapters and read the full transcript now — the video will appear here when it’s published.

Chapters

A shared checklist for good interfaces

In the 1990s, usability expert Jakob Nielsen published ten general principles for interaction design, known as usability heuristics. They remain one of the most widely used tools for evaluating interfaces quickly. A heuristic evaluation — reviewing a page against these principles — takes little time and reliably uncovers common problems.

The ten heuristics with marketing examples

#HeuristicWhat it meansMarketing example
1Visibility of system statusKeep users informed about what's happening"Sending…" then "Thanks! Check your inbox" after a form submit; progress steps in checkout
2Match between system and the real worldUse users' language and familiar concepts"Book a call" instead of "Initiate consultation workflow"
3User control and freedomProvide clear ways to undo, go back or exitEasy-to-find close button on pop-ups; editable cart
4Consistency and standardsFollow platform and internal conventionsLinks look like links; the logo returns home; buttons look the same site-wide
5Error preventionPrevent problems before they occurDate pickers instead of free text; confirming before deleting
6Recognition rather than recallMake options visible instead of relying on memoryShowing selected plan details at checkout; recently viewed items
7Flexibility and efficiency of useSupport both novices and expertsAutofill, saved details, shortcuts for returning customers
8Aesthetic and minimalist designRemove information that competes with what mattersOne primary call to action per section
9Help users recognize, diagnose and recover from errorsPlain-language error messages with solutions"That email looks incomplete — did you mean name@gmail.com?"
10Help and documentationProvide easy-to-find help when neededFAQs near pricing; chat link during checkout

Running a quick heuristic evaluation

  1. Define the task you're evaluating ("Register for the webinar on mobile").
  2. Walk through the task as a new user would, ideally on the device your audience uses.
  3. Note each problem, the heuristic it breaks, and where it happens.
  4. Rate severity — for example 0 (not a problem) to 4 (blocks the task).
  5. Recommend a fix for each.
  6. Ideally, have two or three people evaluate independently, then combine findings; different people spot different problems.
Heuristic evaluation log
Task: ________________________   Device: ________
No Location        Problem                       Heuristic  Severity  Fix
1  Form            No confirmation after submit   H1         3        Add success message + email
2  Pricing         "SKU tiers" jargon             H2         2        Rename to "Plans"
3  Pop-up          Close button tiny, low contrast H3        3        Larger, clear close button

Severity helps prioritize

Not every issue matters equally. Prioritize:

  • Frequency: how many users hit it?
  • Impact: how badly does it block them?
  • Persistence: is it a one-time annoyance or a repeated one?

Fix high-severity, high-frequency issues first. A missing confirmation message on a paid-traffic form may matter more than a slightly inconsistent icon.

Limitations

Heuristic evaluation is fast and cheap but it is expert judgment, not user evidence. It misses problems specific to your audience's knowledge, context or language, and it can produce false alarms. Combine it with usability testing and analytics (covered later in the course).

Worked example: a small e-commerce store

Task: "Buy a phone case on mobile."

Findings:

  • H1: After tapping "Add to cart", nothing visible changes — users tap again and add two cases.
  • H2: Shipping is called "fulfillment fee".
  • H4: Some buttons are rounded and green, others square and gray.
  • H5: The phone model is typed as free text, leading to mistakes.
  • H9: Card errors say "Transaction failed (code 51)".
  • H10: No delivery information until the last step.

Fixes: a toast message and cart badge update; "Shipping" wording; one button style; a model dropdown; human-readable payment errors with next steps; delivery times shown on product pages.

Common mistakes

  • Evaluating on desktop when most customers use mobile.
  • Listing problems without severity, so teams fix trivial issues first.
  • Treating heuristics as rigid rules rather than guides.
  • Skipping real user testing because "we already did a heuristic review".

Hands-on: run a heuristic review with a shared sheet

Set up a simple spreadsheet (Google Sheets, Excel or Airtable all work) with these columns, then have two or three people fill it in independently before you merge results.

ID | Task | Screen/URL | Problem (observed) | Heuristic (H1-H10) | Frequency (1-3) | Impact (1-3) | Persistence (1-3) | Severity | Fix | Owner | Status

Add a formula to turn the three ratings into a single severity score so the team sorts by evidence rather than volume:

Severity (in column I, row 2):   =ROUND((F2*2 + G2*3 + H2)/6*4, 0)

This weights impact most heavily and maps the result onto the familiar 0–4 scale. Adjust the weights if your team prefers, but agree on them before the review, not after.

Step by step:

  1. Choose one task and one device. For example, "Buy a gift card on an Android phone from a Facebook ad."
  2. Walk the task twice. First as a newcomer, reading everything. Then quickly, as a returning customer.
  3. Log only what you observe. "Tapped 'Add to cart'; nothing changed" is an observation. "The cart is bad" is not.
  4. Tag the heuristic. If a problem breaks two heuristics, choose the most specific one.
  5. Merge and de-duplicate. Combine the reviewers' sheets, keep the clearest wording, and note how many reviewers found each issue.
  6. Sort by severity and pick the top three fixes for the next sprint or campaign.

Using AI to speed up (not replace) the review

You can paste screenshots or page text into a multimodal AI assistant and ask it to suggest potential heuristic violations. It is useful for breadth — it may spot jargon or missing feedback messages you overlooked — but it hallucinates problems and misses context. Use it as an extra reviewer whose findings must be confirmed on a real device:

Act as a usability reviewer using Nielsen's 10 heuristics. For the attached screenshots of the
task "<task>" on mobile, list potential issues as: screen, observation, heuristic, why it matters.
Only list issues visible in the screenshots. Say "uncertain" when you are guessing.

How to measure success

Track the number of high-severity issues open over time, and connect the top fixes to a task metric: task completion rate in usability tests, form completion rate, or support contacts about the same problem. A heuristic review "worked" when the specific problems it found stop appearing in recordings, tickets and tests.

Summary

Nielsen's ten heuristics give you a fast, structured way to review any page or flow. Define a task, walk through it on the right device, log problems with the heuristic, severity and fix, and prioritize by frequency and impact — then validate with real users.

Key takeaways

  • Nielsen's ten heuristics are a fast, widely used checklist for evaluating interfaces.
  • Evaluate specific tasks on the device your audience actually uses.
  • Log each problem with the heuristic, severity and a recommended fix.
  • Heuristic reviews complement — but don't replace — testing with real users.

Check your understanding

Quick questions to lock in the lesson. They don’t count towards your certificate.

  1. After submitting a form, nothing on the page changes. Which heuristic is violated?
  2. A checkout error reads 'Error 0x80045'. Which heuristic does a better message address?
  3. What is a key limitation of heuristic evaluation?

Put it into practice

Run a heuristic evaluation of one key task on your website or a client's, on a mobile phone. Log at least six problems with heuristic, severity and fix, and pick the top three to address.

Enrol for free to save your progress

Reading is always free. Enrol to keep your place, take the final assessment and earn a verifiable certificate.