← QCE Digital Solutions Unit 1

Recording pitfalls and useful solutions in an existing interface

Doing a task step by step in an existing interface, recording each pitfall and each useful feature against a useability principle, using screenshots with notes and ideas worth reusing.

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

Understanding Recording pitfalls and useful solutions in an existing interface in QCE Digital Solutions Unit 1

What it does: This entry records the pitfall, the step where it happens and the useability principle it breaks (safety, because users can lose data by accident). A useful feature is recorded with its step and principle, so the idea can be reused in your own design. Good notes name the principle and say exactly what happens. Opinions with no evidence cannot be used in an evaluation. Notes on a screenshot (arrows, circles, labels) show exactly where each finding is, so others can check it. You must actually do the task in the interface. This lets you see the pitfalls and useful features as a real user would.

Common mistakes: With no confirm message, a user can delete a photo by accident. That is a Safety problem, so the line should be 'Principle: Safety'. A progress bar helps users, so it is a useful feature. It should be recorded as 'Useful:', not as a pitfall.

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 Recording pitfalls and useful solutions in an existing interface 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
During a task walk-through of an existing app, what should you do at each step?
Record any pitfall or useful feature and link it to a useability principleSkip to the end and give the app an overall score out of 10
Matches
Step 4: The app is bad and confusing
↓
The note is vague. It names no specific pitfall and no useability principle, so it cannot be used as evidence.
Applying
Meanings
Term
task walk-through
Meaning
Doing a task step by step in an existing interface, recording each pitfall and each useful feature against a useability principle, using screenshots with notes and ideas worth reusing.
Practice
Task: Book a school library room
Testing
Gaps
Type:
Check Answer
Spots
3Pitfall: No confirm message
4Principle: Utility

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

The 'Lion' badge — Inheritance King, 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. During a task walk-through of an existing app, what should you do at each step?
A. Record any pitfall or useful feature and link it to a useability principle ✓
B. Skip to the end and give the app an overall score out of 10
A task walk-through is step by step. Each note is tied to a useability principle so the evidence is specific.
2. Which note about a school canteen app is linked to a useability principle?
A. Learnability: the first screen has no instructions, so new users do not know where to tap ✓
B. This app is bad and I do not like it
Good notes name the principle and say exactly what happens. Opinions with no evidence cannot be used in an evaluation.
3. Why do you add notes to a screenshot during a walk-through?
A. To point to the exact part of the screen where the pitfall or feature appears ✓
B. To make the screenshot look more colourful in your report
Notes on a screenshot (arrows, circles, labels) show exactly where each finding is, so others can check it.
4. Which is an example of an idea worth reusing?
A. A hidden menu that takes five taps to find, which makes tasks slower
B. A confirmation step before deleting a file, which supports the safety principle ✓
Ideas worth reusing are useful features that solve a problem well. You can adapt them in your own design. The hidden menu is a pitfall.
5. You are walking through the task 'book a library room' and the Submit button is grey and unlabelled. How do you record it?
A. Do not record it, because only useful features belong in a walk-through
B. As a pitfall, with the step number, a screenshot note and the principle it breaks ✓
Record both pitfalls and useful features. A pitfall needs the step, a note on the screenshot and the principle, such as effectiveness or learnability.

Match the Pairs

Step 3: Checkout button hidden below the fold → A walk-through note recording a pitfall, because the button is hard to find (breaks learnability and effectiveness)
Screenshot 4 + note: 'Progress bar shows steps left' → A screenshot with a note recording a useful feature that helps users and is an idea worth reusing
Record a pitfall against the safety principle during a walk-through → Pitfall | Step 5: Delete has no confirm | Safety
Record an idea worth reusing and link it to a useability principle → Reuse | Step 2: Search suggests words | Utility
Step 4: The app is bad and confusing → The note is vague. It names no specific pitfall and no useability principle, so it cannot be used as evidence.
Walk-through notes: list only the pitfalls found → It leaves out the useful features. A walk-through should record both pitfalls and useful solutions worth reusing.

Key Term

task walk-through
Doing a task step by step in an existing interface, recording each pitfall and each useful feature against a useability principle, using screenshots with notes and ideas worth reusing.

Fill in the Blanks

1. Step 2: Tap the tiny Pay link Note: Hard to tap, so users miss it Type: pitfall
Hint: Type the word used to label a problem you found in the interface.
2. Step 4: Undo fixes a wrong order Type: useful feature Principle: safety
Hint: Type the useability principle about protecting users from making costly mistakes.
3. Screenshot 3: arrow points to Help icon Note: Icon is clear, easy to learn Principle: learnability
Hint: Type the useability principle about how quickly a new user can pick up the interface.
4. Step 3: Progress bar shows steps left Type: useful feature Reuse: add a progress bar to my design
Hint: Type the label that marks an idea worth using again in your own design.
5. Step 5: Search fails, task cannot finish Type: pitfall Principle: effectiveness
Hint: Type the useability principle about whether users can complete the task accurately.

Spot the Error

Question 1
A Task: Delete a saved photo
B Step 3: Tap the bin icon
C Pitfall: No confirm message
D Principle: Utility
Line D — With no confirm message, a user can delete a photo by accident. That is a Safety problem, so the line should be 'Principle: Safety'.
Question 2
A Task: Order a pizza in an app
B Step 2: Pick a size
C Pitfall: Progress bar shown
D Principle: Learnability
Line C — A progress bar helps users, so it is a useful feature. It should be recorded as 'Useful:', not as a pitfall.
Question 3
A Task: Find a library book
B Step 2: Type a title
C Screenshot: step2_search.png
D Note: Search box has a hint
E Pitfall: Unclear what to type
Line D — The note says the box has a hint, but the pitfall below says users do not know what to type. The note must say 'Search box has no hint' so the record is consistent.
Question 4
A Task: Change my password
B Step 1: Tap Settings
C Step 4: Tap Password
D Step 3: Type new password
Line C — A walk-through records steps in order. After Step 1 comes Step 2, so this line should read 'Step 2: Tap Password'.
Question 5
A Useful: Free times in green
B Principle: Prettiness
C Idea to reuse: Colour coding
Line B — Each note is linked to a real useability principle. Prettiness is not one. Colour coding that helps users find a time quickly fits 'Principle: Efficiency'.

Student with a class code? Join your class →