They should look for points in the prototype where they are confused or feel the user would be confused. These points should be described, evaluated for severity, extent, and the heuristic that was violated noted. It is also important to suggest a solution, if your evaluators are comfortable making a suggestion. The evaluator or an observer of the evaluator may record this information. Compile the results We compile the results in a post-evaluation meeting of the evaluators.
Every problem identified by an evaluator is tacked to a bulletin board, usually sorted by severity.
As each of the most severe problems is presented, the same problem found by a different evaluator is grouped with it, regardless of its severity rating. This is done for each of the remaining severity levels. Same-problem groups are then discussed and reduced to a single problem description, a single severity rating, and one or more suggested solutions. This choice is usually made based on how the development team wishes to approach correcting the problem. We always include a 'severity' group, followed most often by a 'problem type' group 6.