Usability Study Guide

📖 Core Concepts Usability – how safely, effectively, efficiently, and enjoyably users can achieve their goals with a system. ISO definition – “the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use.” Primary notions – designs that match human psychology/physiology → faster task completion, easier learning, higher satisfaction. Usability components (Nielsen & Shneiderman) Learnability – ease of accomplishing basic tasks on first use. Efficiency – speed after learning. Memorability – how quickly proficiency returns after a break. Errors – number, severity, and recoverability of mistakes. Satisfaction – pleasantness of the experience. Related concepts – Ergonomics = physiological fit; Usability = psychological fit (recognition, decision‑making). Usability as a non‑functional requirement – quantified by indirect measures (e.g., error counts, task‑time). 📌 Must Remember Usability = Effectiveness + Efficiency + Satisfaction (ISO). Nielsen’s 10 Heuristics – Visibility, Real‑world match, User control, Consistency, Error prevention, Recognition vs recall, Flexibility, Aesthetic/minimalist, Help users recover, Help & documentation. Key metrics – task completion rate, completion time, error rate/severity, success‑to‑failure ratio, time spent on errors, satisfaction rating, frustration indicators. Iterative design loop – Prototype → Test (real users) → Analyse → Refine → Repeat until targets met. RITE (Rapid Iterative Testing & Evaluation) – modify the interface immediately after a problem is found and a solution is clear. Remote testing – asynchronous, large samples; can be quantitative (task‑based surveys) or qualitative (screen recordings + think‑aloud). Cognitive models – GOMS and Human Processor Model predict user time/cognitive load. 🔄 Key Processes Iterative Design Cycle Define usability goals → Build low‑fidelity prototype → Conduct usability test → Collect quantitative/qualitative data → Identify violations of heuristics or metrics → Implement changes → Re‑test. Heuristic Evaluation Recruit 3–5 usability experts → Walk through the interface → For each Nielsen heuristic, note violations → Prioritize by severity → Report with concrete redesign suggestions. Cognitive Walkthrough Select representative tasks → At each step ask: “Will the user know what to do?” → Record decision points, potential confusions → Recommend UI cues or workflow changes. RITE Method Run a scripted task set with a participant → If a problem is spotted and a fix is obvious, update the prototype before the next participant arrives → Continue until no critical problems remain. Remote Video‑in‑Video Testing Participant’s webcam overlay on live device screen → Record think‑aloud commentary → Synchronize video + screen capture for post‑analysis. 🔍 Key Comparisons Usability vs. Ergonomics – Usability: mental models, recognition, decision‑making. Ergonomics: physical comfort, posture, reach. Heuristic Evaluation vs. Cognitive Walkthrough – Heuristic: expert‑driven, checks against generic principles. Walkthrough: task‑focused, simulates a new user’s thought process. Think‑Aloud vs. Co‑Discovery (Subjects‑in‑Tandem) – Think‑Aloud: single user verbalizes thoughts. Co‑Discovery: two users discuss together, often revealing hidden assumptions. Lab Testing vs. Remote Testing – Lab: controlled environment, high‑fidelity observation. Remote: larger sample, natural context, limited direct observation. ⚠️ Common Misunderstandings “Usability = Aesthetic design.” A pretty UI can still be hard to use; satisfaction is only one component. “If users finish a task, usability is good.” Ignoring efficiency (time, effort) and error recovery gives a false picture. “Consistency always helps.” Over‑consistency can hide shortcuts for expert users; flexibility may be needed. “Usability testing is only for final products.” Early low‑fidelity prototypes provide the most cost‑effective feedback. 🧠 Mental Models / Intuition The “Goal‑Operator” model – users think what they want (goal) and how to achieve it (operators). Good designs make the operators obvious. Error cost principle – each error adds a “cognitive penalty”; preventing errors reduces overall task time more than speeding up correct steps. Memory load reduction – Recognition > Recall. Show options; don’t force users to remember commands. 🚩 Exceptions & Edge Cases Expert users may prefer shortcuts that violate “minimalist design.” Provide hidden accelerators without cluttering the main UI. Highly regulated domains (e.g., medical devices) require error prevention over flexibility; extra confirmations are acceptable. Mobile screens limit visibility; “visibility of system status” may need subtle animations rather than full‑screen messages. 📍 When to Use Which Heuristic Evaluation – early design phases, low cost, when you need a quick sanity check. Cognitive Walkthrough – when assessing learnability for new or infrequent users. GOMS / Human Processor Model – estimating task time before building a prototype. RITE – fast‑moving projects needing immediate fixes after each user test. Remote Video‑in‑Video – testing mobile apps where screen capture is hard; need simultaneous view of face & screen. Component‑Based Testing – modular interfaces (e.g., widget libraries) where each component’s usability must be isolated. 👀 Patterns to Recognize High error rate + low satisfaction → likely poor error‑prevention or confusing feedback messages. Long completion times but high completion rate → efficiency problem; look for unnecessary steps or poor navigation. Sharp drop in memorability after a break → missing “recognition” cues or inconsistent labeling. Repeated comments about “I don’t know what to do next” → break in the cognitive walkthrough; missing affordances. 🗂️ Exam Traps Choosing “Aesthetic design” as the primary usability goal – distractor; aesthetics is only one facet of satisfaction. Assuming “Consistency” solves all errors – wrong; error prevention and clear recovery are separate heuristics. Selecting “Remote testing” for detailed eye‑tracking data – remote methods lack high‑resolution gaze data; lab studies are needed. Confusing “Learnability” with “Memorability.” – learnability is first‑time use; memorability concerns re‑entry after a lapse. Picking “GOMS” for qualitative insights – GOMS provides quantitative time predictions, not user attitudes; think‑aloud or interviews are better. --- Use this guide to flash‑review each heading before the exam – focus on the bolded key terms, compare the side‑by‑side bullets, and practice recalling the step‑by‑step processes.