top of page

Heuristic Evaluations

☻Qualitative Method:
Explore how players feel and behave through interviews, observations, and open-ended feedback. (with optional quantitative metrics)

​

Best Stage: Mid–late development (and before launch)

Primary Goal: Identify and remove barriers so the product is usable by people with diverse abilities

Effort: Moderate

Overview

​Heuristic evaluations help assess how playable, learnable, and enjoyable a game is without requiring live user testing. They are typically conducted using a set of UX principles, such as Nielsen’s 10 Usability Heuristics.

How a Heuristics Review Works

  1. Pick what to review - this could be a full game build, a specific feature (like onboarding), or just the UI.

  2. Choose heuristics to review

  3. Play and evaluate - Reviewers (usually UX researchers or designers) play through the game or prototype and look for places where the experience violates any of the heuristics.

  4. Log issues - include the heuristic, a short description, and severity.

  5. Share findings - organize results with suggestions for improvement.

Nielsen’s 10 Usability Heuristics

  1. Visibility of System Status

  2. The game should keep players informed about what is going on, through appropriate feedback within a reasonable time.

  3. Match Between System and the Real World

  4. Use familiar language, concepts, and metaphors that match player expectations and genre conventions.

  5. User Control and Freedom

  6. Players should be able to undo actions or exit out of unintended states easily (e.g., skip cutscenes, back out of menus).

  7. Consistency and Standards

  8. Follow platform and genre conventions so players don’t have to guess what things mean or how they work.

  9. Error Prevention

  10. Design systems to prevent errors before they occur (e.g., confirmation before deleting saved games).

  11. Recognition Rather Than Recall

  12. Reduce memory load by keeping options, instructions, and controls visible or easily accessible.

  13. Flexibility and Efficiency of Use

  14. Let experienced players speed up interactions (e.g., keyboard shortcuts, skipping tutorials) while still supporting beginners.

  15. Aesthetic and Minimalist Design

  16. UI should be clean and not overloaded with irrelevant information—especially important during onboarding and tutorials.

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

  18. Provide clear, human-readable error messages and recovery options (e.g., in inventory systems or multiplayer connectivity).

  19. Help and Documentation

  20. While it's better if players don’t need instructions, accessible and searchable help (like a pause menu with controls) is important.

More Resources:

Korhonen, Hannu, Marko Montola, and Juha Arrasvuori. "Understanding Playability Heuristics for Mobile Games." Proceedings of the MobileHCI 2006 Workshop on Mobile Gaming, 2006, pp. 9–12.
 

Schell, Jesse. The Art of Game Design: A Book of Lenses. 3rd ed., CRC Press, 2019.
 

Desurvire, Heather, and Charlotte Wiberg. “Game Usability Heuristics (PLAY) for Evaluating and Designing Better Games: The Next Iteration.” Online Communities and Social Computing, edited by A. A. Ozok and P. Zaphiris, Lecture Notes in Computer Science, vol. 5621, Springer, 2009, pp. 557–566.

bottom of page