Writing an interface improvement recommendation
Name:
Date:
Class:
A
Quick Questions
Shade in the A or B circle for each question.
1. Which recommendation is written correctly?
2. What word links the change to the reason in a recommendation?
3. Which is the stronger piece of evidence to support a recommendation?
4. Which recommendation names a specific change?
5. Which statement gives the expected improvement for the user?
B
Match the Pairs
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1Problem: Users miss the Submit button on the form. | AThe change is vague. It does not name the problem, the principle broken or the specific change, and it gives no evidence. | |
| 2Evidence: 4 of 5 testers could not find Submit within 30 seconds. | BNames the specific problem found in the interface, based on what was observed during testing. | |
| 3A recommendation links the change to the user benefit using the word because. | CThis breaks the learnability principle because new users cannot work out the next step without help. | |
| 4A justification names the useability principle that the problem breaks. | DBacks up the recommendation with data from testing so the problem is not just an opinion. | |
| 5Make the app better so users like it more. | EMake the Submit button larger and green because users will find it faster and complete the form with fewer errors. | |
| 6Change the menu to a dropdown. Users will be happier. | FThe change is not linked to a problem or principle with because, and the user benefit is vague and unsupported by evidence. |
C
Definitions
Improvement recommendation
D
Fill in the Blanks
Complete each line of code by filling in the missing parts.
1.
Problem: Users tap Delete by mistake.
Principle: ______
2.
Add a confirm box to Delete _______ users
will not lose files by accident.
3.
________: 6 of 8 testers missed Save.
Change: Make the Save button larger.
4.
Change: Rename Menu to Main menu.
_______: New users find options faster.
5.
Problem: Text is too small to read.
______: Increase font size to 16 pt.
Benefit: Users read it without squinting.
E
Spot the Error
Shade in the letter of the line that contains an error.
Question 1
A
Problem: Add a larger button
B
Principle: Learnability
C
Change: Show a Back icon
D
Because: users can undo steps
Question 2
A
Problem: Delete has no warning
B
Principle: Learnability
C
Change: Add a confirm dialog
D
Because: users avoid mistakes
Question 3
A
Problem: Icons have no labels
B
Principle: Learnability
C
Change: Make it better
D
Because: new users learn fast
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
Question 5
A
Problem: Form errors unclear
B
Principle: Effectiveness
C
Change: Say how to fix it
D
Because: it is cheaper to code
Answer Key
Writing an interface improvement recommendation
Section A: Quick Questions
Q1
A — Increase the Pay button size because testers missed it, which breaks learnability, so new users can finish checkout faster.
Q2
A — because
Q3
B — 4 of 5 testers could not find the Back button in the beta test.
Q4
B — Change the grey error text to red 16pt text beside the empty field.
Q5
A — ...so users with low vision can read the message and fix the form on their first try.
Section B: Match the Pairs
Q1
Problem: Users miss the Submit button on the form. → Names the specific problem found in the interface, based on what was observed during testing.
Q2
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.
Q3
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.
Q4
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.
Q5
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.
Q6
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.
Section C: Definitions
Q1
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.Section D: Fill in the Blanks
Q1
Problem: Users tap Delete by mistake.
Principle: SafetyQ2
Add a confirm box to Delete because users
will not lose files by accident.Q3
Evidence: 6 of 8 testers missed Save.
Change: Make the Save button larger.Q4
Change: Rename Menu to Main menu.
Benefit: New users find options faster.Q5
Problem: Text is too small to read.
Change: Increase font size to 16 pt.
Benefit: Users read it without squinting.Section E: Spot the Error
Q1
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'.
Q2
B — The problem is that users can delete by accident, so the principle broken is safety. The line should be 'Principle: Safety'.
Q3
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'.
Q4
A — Evidence must come from users or testing, such as '6/8 testers got lost'. A personal opinion does not support the recommendation.
Q5
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'.