Heuristic Evaluation

You might say

Don't just say this interface 'feels clunky'. Run through Nielsen's usability heuristics to pinpoint whether status is hidden, error prevention is missing, or terminology is confusing.

A usability inspection method where evaluators systematically check an interface against established design principles to identify interaction defects.An evaluator edits a nickname in Settings and clicks Save. With no saving state or result message, the issue is recorded under visibility of system status with its location, reproduction steps, impact, and recommendation. After the fix, the same task is repeated to verify visible progress and outcome. Heuristic evaluation can reveal likely issues early, but it does not replace testing with real target users.

Know first

User Journey Acceptance Criteria A/B Test

How heuristic evaluation spots UI defects against principles

Settings / ProfileTask: edit nickname and save

Nickname

Nothing changes after click

Passing the recheck proves this known issue improved; real-user comprehension still needs testing.

How one heuristic evaluation moves from issue to recheck

Start with a concrete task: The evaluator opens Settings, edits a nickname, and clicks Save. The button does not change and the page shows no success or failure result. The user cannot tell whether the click worked, processing continues, or another action is safe.

Record the observation, heuristic, and recommendation together: Record the nickname form, edit-and-save steps, visibility heuristic, and duplicate-submission risk. Recommend a Saving state, temporary button disablement, and a clear result; judge severity from frequency, impact, and recovery difficulty. The heuristic explains the fact rather than replacing it.

Repeat the same path after the fix: Edit and save again, confirming visible progress, duplicate-submit prevention, and a clear result. Passing this recheck only shows that the known issue improved; comprehension and real-context behavior still require target-user testing.

Quick checkChoose the best answer

An evaluator clicks Save Nickname in Settings and sees no change. Which issue record best supports a fix and later recheck?

Record the nickname form location, edit-and-save steps, visibility heuristic, user impact, and the path to repeat after the fixWrite only that the page feels unpolished and should be redesigned, without a location or task stepsAsk for a green button without describing the user problem or repeating the save task afterward

You can say this to an AI Agent

Evaluate the Settings page with Nielsen's 10 usability heuristics. Perform the real task 'edit nickname and save'; record each issue with location, reproduction steps, heuristic, user impact, severity, and recommendation. After fixes, repeat the path and verify an immediate saving state, duplicate-submit prevention, and a clear success or failure result. List what still requires real-user testing.

Learn next

1A/B Test→2Acceptance Criteria→3User Flow→

Recommended tool

Web fine-tuning tool · Selector Pro

Select page elements for precise AI edits

Click a button, text, or card, note the change, then copy its exact location to AI.

Open Selector Pro website