← QCE Digital Solutions Unit 1

Writing an interface improvement recommendation

A statement that names the problem, the useability principle it breaks, the specific change to make and the user benefit, linked with because and backed by evidence.

Part of: QCE Digital Solutions Unit 1 — User Experiences and Interfaces — Module 76

Understanding Writing an interface improvement recommendation in QCE Digital Solutions Unit 1

What it does: The word because joins the specific change to the expected improvement for users. The justification ties the problem to a named useability principle and explains why it matters to the user. Evidence comes from observations, test results or user feedback. A personal opinion is not enough to justify a change. A specific change says exactly what to alter and where. 'Improve in some way' cannot be acted on by a designer. A message that does not explain how to recover breaks the safety principle. The recommendation should then say what the message should say instead. A recommendation starts by naming the problem, and this line states one clearly and specifically.

Common mistakes: Line 1 should name the problem, not give a solution. 'Add a larger button' is a change. It should be 'Problem: Back button hidden'. The problem is that users can delete by accident, so the principle broken is safety. The line should be 'Principle: Safety'.

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 an interface improvement recommendation to a class →

This module's key terms are also in a printable crossword (Modules 82–148) and word search (Modules 82–380).

Take this worksheet further — free with Cloodit

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

Learning

Duo

Which recommendation is written correctly?

Increase the Pay button size because testers missed it, which breaks learnability, so new users can finish checkout faster.The app is bad, so make it look better.

Matches

Make the app better so users like it more.

↓

The change is vague. It does not name the problem, the principle broken or the specific change, and it gives no evidence.

Applying

Meanings

Term

Improvement recommendation

Meaning

A statement that names the problem, the useability principle it breaks, the specific change to make and the user benefit, linked with because and backed by evidence.

Practice

Evidence: 4 of 5 testers could not find Pay.

Testing

Gaps

Principle:

Check Answer

Spots

1Problem: Add a larger button

2Principle: Learnability

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

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 recommendation is written correctly?

A. Increase the Pay button size because testers missed it, which breaks learnability, so new users can finish checkout faster. ✓

B. The app is bad, so make it look better.

A good recommendation names the problem, the principle it breaks, the specific change and the user benefit. 'Make it look better' is vague and gives no evidence.

2. What word links the change to the reason in a recommendation?

A. because ✓

B. maybe

'Because' connects the specific change to the problem and the user benefit, so the reader can see why the change is justified.

3. Which is the stronger piece of evidence to support a recommendation?

A. I personally don't like where the Back button is.

B. 4 of 5 testers could not find the Back button in the beta test. ✓

Evidence comes from observations, test results or user feedback. A personal opinion is not enough to justify a change.

4. Which recommendation names a specific change?

A. Improve the error messages in some way.

B. Change the grey error text to red 16pt text beside the empty field. ✓

A specific change says exactly what to alter and where. 'Improve in some way' cannot be acted on by a designer.

5. Which statement gives the expected improvement for the user?

A. ...so users with low vision can read the message and fix the form on their first try. ✓

B. ...so the screen has more colours.

The expected improvement describes the benefit to the user, such as fewer errors or faster tasks, not just a change in how the screen looks.

Match the Pairs

Problem: Users miss the Submit button on the form. → Names the specific problem found in the interface, based on what was observed during testing.

Evidence: 4 of 5 testers could not find Submit within 30 seconds. → Backs up the recommendation with data from testing so the problem is not just an opinion.

A recommendation links the change to the user benefit using the word because. → Make the Submit button larger and green because users will find it faster and complete the form with fewer errors.

A justification names the useability principle that the problem breaks. → This breaks the learnability principle because new users cannot work out the next step without help.

Make the app better so users like it more. → The change is vague. It does not name the problem, the principle broken or the specific change, and it gives no evidence.

Change the menu to a dropdown. Users will be happier. → The change is not linked to a problem or principle with because, and the user benefit is vague and unsupported by evidence.

Key Term

Improvement recommendation

A statement that names the problem, the useability principle it breaks, the specific change to make and the user benefit, linked with because and backed by evidence.

Fill in the Blanks

1. Problem: Users tap Delete by mistake. Principle: Safety

Hint: Type the useability principle about protecting users from harmful mistakes.

2. Add a confirm box to Delete because users will not lose files by accident.

Hint: Type the linking word that connects the change to the user benefit.

3. Evidence: 6 of 8 testers missed Save. Change: Make the Save button larger.

Hint: Type the label for the beta test data that backs up the problem.

4. Change: Rename Menu to Main menu. Benefit: New users find options faster.

Hint: Type the label for the expected improvement for the user.

5. Problem: Text is too small to read. Change: Increase font size to 16 pt. Benefit: Users read it without squinting.

Hint: Type the label for the specific fix being recommended.

Spot the Error

Question 1

A Problem: Add a larger button

B Principle: Learnability

C Change: Show a Back icon

D Because: users can undo steps

Line A — Line 1 should name the problem, not give a solution. 'Add a larger button' is a change. It should be 'Problem: Back button hidden'.

Question 2

A Problem: Delete has no warning

B Principle: Learnability

C Change: Add a confirm dialog

D Because: users avoid mistakes

Line B — The problem is that users can delete by accident, so the principle broken is safety. The line should be 'Principle: Safety'.

Question 3

A Problem: Icons have no labels

B Principle: Learnability

C Change: Make it better

D Because: new users learn fast

Line C — A recommendation needs a specific change. 'Make it better' is vague. It should say exactly what to do, such as 'Change: Label each icon'.

Question 4

A Evidence: I think it's bad

B Problem: Menu is too deep

C Principle: Effectiveness

D Change: Add a Home shortcut

E Because: tasks finish sooner

Line A — Evidence must come from users or testing, such as '6/8 testers got lost'. A personal opinion does not support the recommendation.

Question 5

A Problem: Form errors unclear

B Principle: Effectiveness

C Change: Say how to fix it

D Because: it is cheaper to code

Line D — The because part must give a benefit to the user. Being cheaper to code helps the developer. It should be a user benefit, such as 'users finish the form'.

Student with a class code? Join your class →