🧪 Heuristic evaluation 1. How to conduct heuristic evaluation Heuristic evaluation is performed by having each individual evaluator inspect the interface alone. Only after all evaluations have been completed are the evaluators allowed to communicate and have their findings aggregated. This procedure is important in order to ensure independent and unbiased evaluations from each evaluator. Know what to test and how Whether it’s the entire product or one procedure, clearly define the parameters of what to test and the objective. Select 3–5 evaluators Ensuring their expertise in usability and the relevant industry. Heuristic evaluation 1 💡 ProblemsFound( i ) = N(1 - (1-l) i ) ProblemsFound( i ): number of different usability problems i: number of evaluators N: total number of usability problems l: proportion of all usability problems found by a single evaluator (34%) Know your users and have clear definitions of the target audience’s goals, contexts, etc Objectives User persona User stories Business goals 1st Walkthrough Have evaluators use the product freely so they can identify elements to analyze. 2nd Walkthrough Evaluators scrutinize individual elements according to the heuristics. They also examine how these fit into the overall design, clearly recording all issues encountered. Debriefing session Prioritize usability issues, and brainstorm solutions 2. Checklist of criteria Visibility of system status Heuristic evaluation 2 The system should keep users informed through appropriate feedback within reasonable time Match between system and the real world The system should speak the users' language rather than system-oriented terms. Follow real-world conventions User control and freedom Users often make mistakes and need 'emergency exits' to leave the unwanted state. Support undo and redo Consistency and standards Users shouldn't have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions Error prevention Prevent problems from occuring in the first place, or check for them and present users with a confirmation option before they commit to the action Recognition rather than recall Minimize memory load by making objects, actions, and options visible. Instructions should be visible or easily retrievable Flexibility and efficiency of use Accelerators - unseen by the novice user - may often speed up the interaction for the expert user. Allow users to tailor frequent actions Aesthetic and minimalist design Dialogues should not contain information which is irrelevant or rarely needed Help recognize & recover from errors Heuristic evaluation 3 Error messages should be expressed in plain language, indicate the problem, and suggest a solution Help and documentation Any necessary help documentation should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too Heuristic evaluation 4
