Skip to end of metadata
Go to start of metadata

This document is currently a 'work in progress.'

General FAQ:
Q. Does it matter which order you do your evaluations?
A. See UX Walkthrough Preparation and Execution.
Q. Do I have to do each evaluation?
A.
Q. Which evaluation is best for me? Why would I choose one evaluation over the other?
A.
Q. I do not have UX design related experience or anything similar, does it matter?
A. We believe that anyone can do a heuristic evaluation if you follow the guidelines we've set forth here. Undoubtedly your ability to do heuristic evaluations will improve each time you do one.
Q. How much time does it take to do an evaluation?
A. This really varies depending on how complicated your website or application it is, how throughly you investigate it, and how many task scenarios you decide to work through. For an 'average' website, you should probably expect a fairly thorough evaluation to take 3-5 hours.
Q. What are the general steps in doing a UX walkthrough?
A. See UX Walkthrough Preparation and Execution.

Heuristic Evaluation FAQ:
Q. What is an heuristic evaluation? Why should I do one?
A. See Heuristic Evaluation.
Q. The application I am evaluating has design and layout issues. How do I categorize these items?
A. These issues will usually be categorized under a heuristic related to what problems the design and layout issues cause for the user. If no other heuristic fits, "Aesthetic and Minimalist Design" is often a good choice for these types of issues.
Q. How do I test "Error Prevention"?
A. See Heuristic Evaluation - A System Checklist, #6. Error Prevention.
Q. What is "Flexibility and efficiency of use" and how do I test it?
A. See Heuristic Evaluation - A System Checklist, #8. Flexibility and Efficiency of Use.
Q. The application I am evaluating "violates" many of the heuristics. What should I do? Am I doing something wrong?
A. It is very common to find numerous heuristic violations in any website or application. The heuristics are simply a way of identifying, categorizing and communicating the ways your application can be improved, and should be viewed simply as helpful feedback.

Cognitive Walkthrough FAQ:
Q. What is a cognitive walkthrough? Why should I do one?
A. See Cognitive Walkthrough.
Q. What is a persona and why should I use one?
A. See Personas.
Q. How do I create a persona?
A. See Persona Creation.
Q. What if I don't have time to create a persona?
A. See UX Walkthrough Preparation and Execution#no_persona or Provisional Personas.

Accessibility Walkthrough FAQ:
To be done.

Low-Level Code Walkthrough
To be done.

Other Questions / Issues

  • No labels