Because heuristics inspection and user testing are two complementary evaluation methods, people usually conduct both of them to get a system thoroughly evaluated. However, there is a problem: the nature of the usability problems found through analytic and empirical methods are not exactly the same, and the way by which evaluators document these two types of usability problems are also different; therefore, people find it difficult to consolidate the evaluation results from heuristics inspection and user testing. The aim of this paper is to propose a “usability problem report format,” which provides clearly defined components for describing a usability problem. After all the problems are documented using this format, the evaluators could match the usability problems from the above two types of evaluation methods by analyzing each component of the usability report. However, the rules for matching usability problems with different natures are yet to be developed in the future studies. Here are the basic components of the proposed format:
· Context: “user context,” “interaction context,” and the “work context;”
· Cause: the “design fault” or a “knowledge requirement on the user” that lead to the breakdown;
· Breakdown: the point at which “user does not take an appropriate step in the interaction;”
· Outcome: the results of a breakdown, including behaviors, performance, or preference;
· Solution: proposed design change for addressing the problem.
