Writing a user-experience critique
Name:
Date:
Class:
A
Quick Questions
Shade in the A or B circle for each question.
1. Which opening step best starts a UX critique of a school canteen ordering app?
2. Which statement is a critique with evidence?
3. A UX critique judges an interface mainly against which standard?
4. Which is a well-formed recommended change?
5. Which should a balanced UX critique include?
B
Match the Pairs
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1Step 1: Open app > Step 2: Tap Search > Step 3: Filter results > Step 4: Book | AThis is an opinion with no evidence, no user path and no reasons. A critique must judge how well the interface supports the user's goals, using evidence. | |
| 2Recommendation: Add a visible Back button on the payment screen | BWeakness: The Save button is grey and small, so users miss it and lose their work | |
| 3A strength must be backed by evidence from the user's path, not just an opinion | CA recommended change: a specific improvement that would fix a weakness found in the critique | |
| 4A weakness is judged by how it gets in the way of the user's goal, with a reason | DA critique must include recommended changes. Stating a weakness without suggesting an improvement leaves the critique incomplete. | |
| 5Critique: I don't like the colours. The app is bad. | EStrength: Checkout needs only 2 taps, so users reach their goal quickly | |
| 6Critique: The menu is confusing. Weakness found, no changes needed. | FA user journey: the path a user takes through the interface to reach their goal, described step by step |
C
Definitions
UX critique
D
Fill in the Blanks
Complete each line of code by filling in the missing parts.
1.
_______: Home > Search > Cart > Pay
2.
Strength: One-tap Pay button
________: 9 of 10 users found it quickly
3.
________: Error text is hard to read
Evidence: 7 of 10 testers missed it
4.
Weakness: Cart icon is too small
______________: Enlarge icon to 48px
5.
____: Buy a ticket in two minutes
Journey: Home > Pick seat > Pay
E
Spot the Error
Shade in the letter of the line that contains an error.
Question 1
A
Goal: Pay for a canteen order
B
Step 1: Pay, then open app
C
Step 2: Add item, tap Pay
D
Step 3: See the receipt
Question 2
A
Goal: Find the bus timetable
B
Strength: Search bar is clear
C
Evidence: I just like the look
D
Fix: Add a recent routes list
Question 3
A
Goal: Change my password
B
Weakness: Reset link is hidden
C
Evidence: 4/5 users missed it
D
Fix: Change the app colours
Question 4
A
Goal: Enrol in a school club
B
Step 1: Open Clubs, tap Join
C
Step 2: Dev codes the database
D
Strength: Only 2 steps needed
Question 5
A
Goal: Check my timetable
B
Step 1: Log in with school ID
C
Weakness: 3 of 6 locked out
D
Fix: Make it better
Answer Key
Writing a user-experience critique
Section A: Quick Questions
Q1
A — Describe the path a student takes from opening the app to paying for lunch
Q2
B — The Pay button is grey and below the fold, so 3 of 5 testers could not find it
Q3
A — How well it supports the user's goals
Q4
A — Move the Pay button to the top of the cart screen and make it a high-contrast colour so users find it quickly
Q5
B — Both strengths and weaknesses of the interface
Section B: Match the Pairs
Q1
Step 1: Open app > Step 2: Tap Search > Step 3: Filter results > Step 4: Book → A user journey: the path a user takes through the interface to reach their goal, described step by step
Q2
Recommendation: Add a visible Back button on the payment screen → A recommended change: a specific improvement that would fix a weakness found in the critique
Q3
A strength must be backed by evidence from the user's path, not just an opinion → Strength: Checkout needs only 2 taps, so users reach their goal quickly
Q4
A weakness is judged by how it gets in the way of the user's goal, with a reason → Weakness: The Save button is grey and small, so users miss it and lose their work
Q5
Critique: I don't like the colours. The app is bad. → This is an opinion with no evidence, no user path and no reasons. A critique must judge how well the interface supports the user's goals, using evidence.
Q6
Critique: The menu is confusing. Weakness found, no changes needed. → A critique must include recommended changes. Stating a weakness without suggesting an improvement leaves the critique incomplete.
Section C: Definitions
Q1
UX critique — A review of an existing interface that follows a user's path, judges how well it supports their goals using evidence, and recommends improvements.Section D: Fill in the Blanks
Q1
Journey: Home > Search > Cart > PayQ2
Strength: One-tap Pay button
Evidence: 9 of 10 users found it quicklyQ3
Weakness: Error text is hard to read
Evidence: 7 of 10 testers missed itQ4
Weakness: Cart icon is too small
Recommendation: Enlarge icon to 48pxQ5
Goal: Buy a ticket in two minutes
Journey: Home > Pick seat > PaySection E: Spot the Error
Q1
B — A user journey must follow the real order of the user's actions. Paying cannot come before opening the app. It should read 'Step 1: Open app, tap Menu'.
Q2
C — A strength needs evidence from the user's path, such as taps, time or errors. A personal opinion is not evidence. It should be something like 'Evidence: Found it in 2 taps'.
Q3
D — A recommended change must address the weakness found. Changing colours does not fix a hidden reset link. It should suggest something like moving the link.
Q4
C — A UX critique follows the user's path through the interface. It must not describe developer work behind the scenes. It should be a user action like 'Step 2: Pick a day, tap Save'.
Q5
D — A recommended change must be specific and actionable. 'Make it better' is too vague to act on. It should name a change such as 'Fix: Add a Forgot ID link'.