Skip to content
Tutorials Center
My learning

Topics

Lesson 36 of 36 ยท Projects and Practice

Practice: UX Review and Critique Exercises

Sharpen your UX skills with hands-on exercises: critique a login form, fix a confusing error, check accessibility, design a flow and plan a test, with answers.

UX skill grows by doing: looking at real interfaces, saying specifically what is wrong, and proposing better ones. These exercises cover the second half of this course, from visual and interaction design through prototypes and testing. Try each one before opening the discussion; there is rarely one right answer, but there are better and worse reasons.

Exercise 1: Critique a login form

What is wrong with this form?

List at least six problems, then compare with these:

  • Low contrast: gray text and a pale button fail contrast ratios.
  • Tiny font and tiny targets (11 px text, a 10 px button).
  • Placeholders instead of visible labels; "Pass" is cryptic.
  • A weak primary button: the label "Submit" says nothing about the result; "Log in" is clearer.
  • The "Forgot it?" link is almost invisible and vague ("Forgot password?").
  • No visible focus style, no show-password control, no error messages defined.

Exercise 2: Rewrite the error messages

Rewrite each message so it is specific, blame-free and tells the user what to do.

Python Check your rewrite against a rule set

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Compare your versions with the "after" lines. Messages should appear next to the problem field and combine color with text and an icon.

Exercise 3: Pick a fidelity and a method

For each situation, choose a prototype fidelity (see fidelity levels) and an evaluation method.

Situation Suggested answer
Two ideas for navigation, one day Paper or gray-box prototype and a quick test with 3 to 5 people
Whether people understand a new pricing page label Mid fidelity test with real labels, task scenario
Does a loading animation feel calm High fidelity with motion; observe reactions
Pre-launch scan of a 40-screen product, no time for users Heuristic evaluation by 3 to 5 evaluators
Which of two headlines converts better A/B test (see A/B testing)

Exercise 4: Map a flow and find the dead end

Draw a flow for "cancel a subscription" including error, retention offer and confirmation. Then check it with a program.

Python Dead-end finder

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Fix it: cancel_error needs "Try again" and "Contact support" paths. Also note that the flow offers no way back from cancel_start to settings; add one. Ethical design point: cancelling should be about as easy as signing up. See UX in teams for how to push back on dark patterns.

Exercise 5: Write a usability test scenario

Write one task scenario for "check whether a package is covered by the warranty" without using the words on the interface. Good example: "You bought a blender 14 months ago and the motor stopped. Find out whether the company will repair it for free." Then define success (reaches the warranty terms and states the coverage period) and one follow-up question ("What did you expect to find first?"). Compare to the guidance in test planning.

Exercise 6: Rate severity and score a SUS

Given the observations below, assign a severity (0 to 4) to each and justify it using frequency, impact and persistence: (a) 5 of 5 users cannot find the Export button; (b) 1 of 5 mistook an icon but corrected in two seconds; (c) 3 of 5 lost typed data after a session timeout. A sensible reading: (a) 3 or 4, (b) 1, (c) 4 (data loss is severe).

Python SUS practice

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

(Here enumerate starts at 0, so index 0 is item 1, an odd item.) Try changing the answers to see the score move.

Exercise 7: Design a mini design system

Pick three tokens (primary color, spacing step, radius) and one button with four states. Write the token names, then write the handoff notes a developer would need (see design systems). Check that your primary color has 4.5:1 contrast with its label.

Self-assessment

Rate yourself from 1 to 5 on each: hierarchy and layout, type and color, interaction states, accessibility, wireframes, prototypes, flows, test planning, moderating, analysis, metrics, collaboration. Pick the lowest two and repeat the matching lessons with a new example. Then build a project of your own and add it to your portfolio (portfolio case study).

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. Which is the best label for a login button?

    A specific verb phrase tells users what will happen.
  2. 2. Which method fits a quick pre-launch check without participants?

    Heuristic evaluation needs only evaluators and a set of principles.
  3. 3. A bug makes users lose typed data. What severity is sensible?

    Data loss is high-impact and erodes trust, so it is severe.

Summary

  • Critique with specifics: contrast, size, labels, button text, error handling and states.
  • Match fidelity and method to the question you need to answer.
  • Check flows for dead ends and write task scenarios without interface words.
  • Rate severity by frequency, impact and persistence; compute SUS carefully.
  • Keep practicing on real products and keep the best work in your portfolio.

Next: back to the UX Design course page