Skip to content
Tutorials Center
My learning

Topics

Lesson 30 of 36 ยท Usability Testing

Heuristic Evaluation and Cognitive Walkthrough

Find usability problems without users: apply Nielsen's 10 heuristics in an expert review, run a cognitive walkthrough, and combine them with testing.

Testing with users is the gold standard, but it takes time to organize. Usability inspection methods let a few evaluators find many problems quickly, with no participants, based on established principles. They are ideal before a test (to remove obvious problems so the session reveals deeper ones) and when time is short.

This lesson covers the two best-known methods: heuristic evaluation and the cognitive walkthrough.

Heuristic evaluation

A heuristic evaluation has several evaluators inspect an interface alone, compare it against a list of usability principles, and record every violation. Jakob Nielsen's ten heuristics are the most used list.

Nielsen's heuristics (1 to 5)

Visibility of system status Always tell users what is going on.
Match with the real world Use the user's words and concepts.
User control and freedom Easy undo, cancel and exit.
Consistency and standards Same thing, same word and look.
1 / 2

Examples of violations:

  • Visibility of status: pressing Pay shows nothing for six seconds, so users press it again.
  • Match with the real world: an error says "Exception 0x80004005" instead of "We could not save your changes".
  • User control: a destructive delete with no undo or confirmation.
  • Consistency: "Remove" in one list, "Delete" in another, "Trash" elsewhere for the same action.
  • Error prevention: allowing a date range where the end is before the start.
  • Recognition over recall: asking users to retype a code shown on a previous screen.

How to run one

  1. Pick 3 to 5 evaluators (one gets about 35 percent of problems, five find most). Domain and usability experts are best.
  2. Define the scope and tasks or scenarios to review.
  3. Each evaluator goes through the interface at least twice (overview, then detail), alone, logging each issue with the heuristic violated, location, description and a severity (0 to 4, see severity ratings).
  4. Merge and deduplicate the findings in a group session, then agree on ratings.
  5. Report with screenshots and fixes.

A limitation: evaluators find problems that violate rules, but may report issues real users never have, and miss problems of domain knowledge. It complements user testing and does not replace it.

Python Merge evaluators' findings

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Issues found by several evaluators, with high average severity, go to the top of the list.

Cognitive walkthrough

A cognitive walkthrough checks how easy a task is to learn for a first-time user. You walk through the correct action sequence step by step and, for each step, ask four questions:

  1. Will the user try to achieve the right effect (do they know this step is needed)?
  2. Will the user notice that the correct action is available?
  3. Will the user connect the correct action to the effect they want (does the label or icon make sense)?
  4. After the action, will the user see that progress was made (is there feedback)?

If the answer to any question is "no", record a failure story explaining why a real person would go wrong there.

Python Walkthrough record

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Two steps expose the same design issue: the return option is hidden behind an unclear label and a small "..." menu.

Choosing between methods

Method Needs users? Best for Main weakness
Heuristic evaluation No Quick broad coverage of known problems May report false alarms, misses domain issues
Cognitive walkthrough No Learnability of a task for new users Narrow: tasks only
Usability test Yes Real behavior, surprises Takes more time and recruiting

A practical sequence: inspect first to clear the obvious, then test with users, then iterate.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. Which heuristic does a 'Delete' with no undo violate?

    Users need an emergency exit or undo for mistaken actions.
  2. 2. Why should heuristic evaluators first work alone?

    Independent reviews avoid bias; merging comes afterward.
  3. 3. A cognitive walkthrough focuses on which kind of user?

    It evaluates how easily a new user can learn the correct steps by exploration.

Summary

  • Heuristic evaluation uses a few independent evaluators and a list of principles such as Nielsen's ten.
  • Merge findings, remove duplicates and rate severity together.
  • A cognitive walkthrough asks four questions per step to check learnability for new users.
  • Inspection methods are fast and cheap but complement, not replace, testing with real users.

Next: UX Metrics: SUS and Task Success