Loading content
Heuristic evaluation is a structured usability inspection where experts systematically assess an interface against established heuristics. It uncovers usability issues early, rates problems by severity, and produces targeted recommendations to improve interaction and information architecture. Typical flow includes task analysis, heuristic application, issue…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
A heuristic evaluation is a structured inspection of a user interface by several usability specialists. They compare the interface with established design principles and document concrete interaction problems.
Jakob Nielsen and Rolf Molich developed the method around 1990 as a pragmatic part of discount usability engineering. It aimed to expose actionable usability problems early and with much less effort than extensive user testing.
Imagine several independent inspectors using the same checklist. Each person walks through the interface alone, links observations to a heuristic, and rates severity. Only then are findings combined, duplicates removed, and priorities agreed. Multiple perspectives improve coverage because individual evaluators notice different problems.
General design principles provide the criteria for inspecting dialogs and interactions.
Several specialists inspect separately at first so that their observations influence one another less.
Impact, frequency, and persistence of a problem support prioritization.
A shared findings list merges overlaps and makes the required action understandable.
The method works for early designs and existing interfaces when teams need a quick view of systematic usability risks. It produces expert findings about the interface; actual user behavior and domain-specific comprehension problems still require complementary user testing.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.