← QCE Digital Solutions Unit 3

Writing a user-experience 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.

Part of: QCE Digital Solutions Unit 3 — Innovative Digital Solutions — Module 82

Understanding Writing a user-experience critique in QCE Digital Solutions Unit 3

What it does: The statement names a strength and supports it with evidence (2 taps), linking it to how well the goal is supported. The weakness is identified with a reason and its effect on the user's goal, which is what a critique requires. A strength or weakness needs evidence, like what happened or what users said. Opinions alone do not justify a judgement. The judgement is about whether users can achieve their goals, not the critic's personal taste. Recommendations should be specific, linked to a weakness and explain the benefit. Vague suggestions can't be acted on. A balanced critique identifies what already works well so it is kept, as well as what needs to change.

Common mistakes: 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'. 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'.

Class: _____________________  ·  Name: _____________________  ·  Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

🖨 Print worksheet + answer key Add Writing a user-experience critique to a class →

This module's key terms are also in a printable crossword (Modules 251–337) and word search (Modules 194–337).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning
Duo
Which opening step best starts a UX critique of a school canteen ordering app?
Describe the path a student takes from opening the app to paying for lunchList every colour used in the app's logo
Matches
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.
Applying
Meanings
Term
UX critique
Meaning
A review of an existing interface that follows a user's path, judges how well it supports their goals using evidence, and recommends improvements.
Practice
Journey: A student opens the canteen app to order lunch.
Testing
Gaps
: Home > Search > Cart > Pay
Check Answer
Spots
1Goal: Pay for a canteen order
2Step 1: Pay, then open app

Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.

The 'Ermine' badge — Tundra Streak, one of Cloodit's 106 collectible badges
Students earn collectable badges

Over 100 of them, across seven natural biomes.

Study Buddy
Students build a real study resource

Turns their work into revision material ready for Flash Cards and Exam study.

Diamond Dash — one of Cloodit's live, competitive Sprint games
Students lock in with Sprints

Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.

A Cloodit certificate of achievement, ready to personalise and print
Custom printable certificates

Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.

Add to class →

Quick Questions

1. Which opening step best starts a UX critique of a school canteen ordering app?
A. Describe the path a student takes from opening the app to paying for lunch ✓
B. List every colour used in the app's logo
A UX critique begins by following a user's journey through the interface towards their goal, such as ordering and paying.
2. Which statement is a critique with evidence?
A. The Pay button is bad and the app is annoying
B. The Pay button is grey and below the fold, so 3 of 5 testers could not find it ✓
A strength or weakness needs evidence, like what happened or what users said. Opinions alone do not justify a judgement.
3. A UX critique judges an interface mainly against which standard?
A. How well it supports the user's goals ✓
B. How much the critic personally likes it
The judgement is about whether users can achieve their goals, not the critic's personal taste.
4. Which is a well-formed recommended change?
A. Move the Pay button to the top of the cart screen and make it a high-contrast colour so users find it quickly ✓
B. Make the app better
Recommendations should be specific, linked to a weakness and explain the benefit. Vague suggestions can't be acted on.
5. Which should a balanced UX critique include?
A. Only weaknesses, because strengths do not need to be mentioned
B. Both strengths and weaknesses of the interface ✓
A balanced critique identifies what already works well so it is kept, as well as what needs to change.

Match the Pairs

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
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
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
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
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.
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.

Key Term

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.

Fill in the Blanks

1. Journey: Home > Search > Cart > Pay
Hint: Type the critique heading used for the steps a user follows through the interface.
2. Strength: One-tap Pay button Evidence: 9 of 10 users found it quickly
Hint: Type the word for the proof (such as test results) that backs up a judgement.
3. Weakness: Error text is hard to read Evidence: 7 of 10 testers missed it
Hint: Type the label for a part of the interface that does not support the user well.
4. Weakness: Cart icon is too small Recommendation: Enlarge icon to 48px
Hint: Type the label for a suggested change that would improve the interface.
5. Goal: Buy a ticket in two minutes Journey: Home > Pick seat > Pay
Hint: Type the word for what the user wants to achieve, which the interface is judged against.

Spot the 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
Line 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'.
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
Line 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'.
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
Line 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.
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
Line 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'.
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
Line 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'.

Student with a class code? Join your class →