UI/UX Design Testing, Metrics & Professional Practice Syllabus

Testing, Metrics & Professional Practice syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Testing, Metrics & Professional Practice in UI/UX Design, not a summary of it.

1. 1

   Usability Testing

   4 topics

   • Moderated vs Unmoderated Testing
   • Writing Test Scripts and Tasks
   • Think-Aloud Protocol
   • Remote and In-Person Testing
2. 2

   Evaluation & Iteration

   4 topics

   • Heuristic Evaluation
   • Cognitive Walkthroughs
   • Synthesizing Test Findings
   • Prioritizing and Iterating on Fixes
3. 3

   UX Metrics & Analytics

   5 topics

   • UX KPIs and Success Metrics
   • HEART Framework
   • System Usability Scale (SUS)
   • A/B Testing
   • Behavioral Analytics and Heatmaps
4. 4

   UX Writing & Content Design

   4 topics

   • Microcopy and UI Text
   • Voice and Tone
   • Content Strategy
   • Error Messages and Helper Text
5. 5

   Collaboration & Process

   4 topics

   • Agile and Lean UX
   • Working with Product and Engineering
   • Design Critiques and Feedback
   • Stakeholder Management
6. 6

   Portfolio & Career

   4 topics

   • Building a UX Portfolio
   • Case Study Storytelling
   • Presenting Design Work
   • Interviewing and Design Challenges

Testing, Metrics & Professional Practice flashcards for UI/UX Design

23 of 50 cards from the Testing, Metrics & Professional Practice deck — real questions with worked answers.

1. What is moderated usability testing?

   A usability test in which a trained facilitator interacts with the participant in real time — giving instructions, asking follow-up questions, and probing behavior — either in person or remotely.

2. What is unmoderated usability testing, and what is its main advantage?

   Testing in which participants complete tasks alone using an online tool, with no facilitator present. Its main advantages are speed, lower cost, and the ability to run many participants in parallel in their natural environment.

3. Give two situations where moderated testing is preferable to unmoderated testing.

   (1) Testing early prototypes or complex flows where participants may need guidance or clarification; (2) exploratory research where you need to ask follow-up questions and probe the reasons behind behavior.

4. What is a usability test script and what sections does it typically contain?

   A structured document the moderator follows to keep sessions consistent. It typically contains: a welcome/introduction, consent and recording permission, warm-up questions, task scenarios, follow-up/probing questions, and a wrap-up (e.g., SUS questionnaire, thanks, incentive).

5. What makes a well-written usability test task?

   It is a realistic, goal-oriented scenario ('You want to send $50 to a friend...') that is specific, actionable, and free of leading language or interface terms that give away the answer (avoid using the exact button labels).

6. Why should usability test tasks avoid using the exact words that appear in the interface?

   Because participants will simply pattern-match the words in the task to labels on screen instead of genuinely navigating, which biases the test and hides real findability problems.

7. What is the think-aloud protocol?

   A usability testing method in which participants continuously verbalize their thoughts, expectations, and reactions while performing tasks, revealing their mental model and the reasons behind their actions.

8. Distinguish concurrent think-aloud from retrospective think-aloud.

   Concurrent: the participant verbalizes thoughts while performing the task (real-time insight, but may alter behavior and task times). Retrospective: the participant performs tasks silently and then narrates their thinking afterward, often while watching a recording (natural performance, but relies on memory).

9. What is a key limitation of the concurrent think-aloud protocol?

   Verbalizing can change behavior and slow participants down (reactivity), so task-time and performance metrics collected during concurrent think-aloud are unreliable; some participants also find it unnatural and fall silent.

10. Compare remote and in-person usability testing.

    Remote: cheaper, faster recruiting, geographically diverse participants tested in their natural context, but less control and weaker observation of body language. In-person: full control of environment, rich observation (facial expressions, gestures), easier hardware/prototype testing, but costlier and slower.

11. What is heuristic evaluation?

    An inspection method (no users involved) in which a small group of usability experts independently examines an interface against a set of recognized usability principles (heuristics) and reports violations with severity ratings.

12. How many evaluators does Jakob Nielsen recommend for a heuristic evaluation, and why?

    About $3$–$5$ evaluators. A single evaluator finds only around $35\%$ of usability problems, while $5$ evaluators together find roughly $75\%$; beyond five, additional evaluators add little new insight for the cost.

13. Name five of Nielsen's 10 usability heuristics.

    Any five of: visibility of system status; match between system and real world; user control and freedom; consistency and standards; error prevention; recognition rather than recall; flexibility and efficiency of use; aesthetic and minimalist design; help users recognize, diagnose, and recover from errors; help and documentation.

14. Describe Nielsen's 0–4 severity rating scale for usability problems.

    $0$ = not a usability problem; $1$ = cosmetic, fix only if time allows; $2$ = minor problem, low priority; $3$ = major problem, high priority; $4$ = usability catastrophe, must fix before release.

15. What is a cognitive walkthrough?

    An expert inspection method that evaluates how easy it is for a new user to learn an interface by stepping through a specific task action-by-action and asking whether the user would know what to do at each step.

16. What four questions are asked at each step of a cognitive walkthrough?

    (1) Will the user try to achieve the right effect? (2) Will the user notice that the correct action is available? (3) Will the user associate the correct action with the effect they want? (4) After the action, will the user see that progress is being made toward the goal?

17. How does a cognitive walkthrough differ from a heuristic evaluation?

    A cognitive walkthrough is task-specific and focuses on learnability for first-time users, walking step-by-step through one flow; a heuristic evaluation is a broad review of the whole interface against general usability principles, not tied to a single task.

18. What is affinity mapping (affinity diagramming) in synthesizing test findings?

    A synthesis technique in which individual observations from research sessions are written on separate notes and then grouped bottom-up into clusters of related issues, revealing themes and patterns across participants.

19. When synthesizing usability findings, why should observations be separated from interpretations?

    Observations are objective facts ('4 of 6 users clicked the logo expecting search'); interpretations are conclusions drawn from them. Recording them separately prevents bias, keeps evidence traceable, and lets the team debate conclusions against raw data.

20. What key elements should a well-reported usability finding include?

    A clear description of the problem, evidence (how many participants, quotes, or clips), where it occurred, a severity rating, and ideally a recommendation for fixing it.

21. What two dimensions are most commonly used to prioritize usability fixes?

    Impact (severity of the problem and how many users it affects, especially on critical tasks) versus effort (development cost to fix). High-impact, low-effort fixes — 'quick wins' — are done first.

22. In an impact–effort prioritization matrix, how are the four quadrants typically treated?

    High impact / low effort = quick wins, do first; high impact / high effort = major projects, plan deliberately; low impact / low effort = fill-ins, do when convenient; low impact / high effort = avoid or drop.

23. Why is iterative testing (test–fix–retest) recommended over one large usability test?

    Fixes can introduce new problems, and each round of a small test (about 5 users) uncovers most remaining major issues cheaply; repeated small cycles progressively improve the design more reliably than a single large study.

See more Testing, Metrics & Professional Practice flashcards →

Planning Testing, Metrics & Professional Practice for UI/UX Design

Testing, Metrics & Professional Practice (UI/UX Design) FAQ