UX Design Critiques: 3 Tips for Effective Feedback
How to run a critique that produces decisions instead of opinions. Watch it before your first critique: it changes what you write down.
Watch on YouTube (opens in a new tab)Third-party video. It is loaded from YouTube and is not hosted by the academy.
By the end of this lesson you can
- Use a repeatable method to critique an interface against goals and principles.
- Separate observation, impact and suggestion in written feedback.
- Prioritise improvements by their effect on users.
The idea
Critique is a core design skill. You will critique your own work every day, review teammates' work, and assess competitors. Good critique is specific, grounded in goals and principles, and useful to the person receiving it. "I don't like the colours" is an opinion. "The two buttons have equal weight, so people may not know which one continues the booking" is a critique.
A five-step method
- Understand the goal. Who is this for, what are they trying to do, and what does the business need? Without the goal, you cannot judge anything.
- Do the task. Try to complete the main task as a user would. Note every hesitation.
- Review with principles. Go through hierarchy, grouping and alignment, typography, colour and contrast, consistency, content and copy, states and feedback, and accessibility.
- Write findings as observation, impact, suggestion. What you see, why it matters for the user or the goal, and one possible improvement.
- Prioritise. Rank findings by how much they affect people's ability to succeed. Lead with the most important, and include what works well so it is kept.
Critique is not testing
An expert critique, like a heuristic evaluation, predicts problems. It is fast and cheap, but it can miss real problems and flag ones users do not mind. Use critique to improve designs before testing, and confirm important findings with real users.
Why it matters in real projects
Designers who can critique clearly improve their own work faster, give feedback colleagues value, and present their own decisions convincingly. Critique also appears in many design interviews ("critique this app") and in client work, where you need to explain what is wrong with an existing site without offending its owners.
A realistic example
A designer is asked to critique a charity's donation page. Instead of listing dislikes, they write:
Observation: The monthly and one-off options are shown as two small tabs above the amount buttons, and "monthly" is selected by default without a clear label. Impact: People intending a one-off gift may set up a recurring payment by mistake, which damages trust and may lead to refunds and complaints. Suggestion: Ask "How often would you like to give?" with two clearly labelled options and no default, or default to one-off and offer monthly as a clear second choice.
The finding is specific, connected to user and organisational impact, and offers a direction without dictating the final design. The charity's team immediately understands why it matters.
- Frequency is easy to miss and preselected. Risk of accidental monthly gifts.
- "Donate" looks the same as the amounts, so the main action does not stand out.
- The fee note fails contrast and may surprise people later.
Step by step
Write the goal
One sentence each for the user goal and the business goal.
Complete the task twice
Once naturally, noting hesitation; once slowly, looking for problems.
Go through the principles
Use the checklist: hierarchy, grouping, alignment, type, colour, consistency, content, states, accessibility.
Annotate a screenshot
Number each issue on the image.
Write each finding
Observation, impact, suggestion. Keep each to two or three sentences.
Prioritise and add positives
Order by user impact. Add two or three things that work well.
Common mistakes
Mistake Critiquing without knowing the goal.
Instead Ask, or state your assumption about the goal before you begin.
Mistake Stating preferences as problems.
Instead Tie each point to a principle, evidence or a likely user impact.
Mistake Prescribing a full redesign for every issue.
Instead Offer a direction; leave room for the designer to solve it.
Mistake Only listing negatives.
Instead Say what works so it is not lost in changes.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 45 min
Write a structured critique
Critique the sign-up or onboarding flow of a real app using the method.
Steps
- Write the user and business goals.
- Complete the flow and annotate screenshots.
- Write at least six findings as observation, impact, suggestion.
- Prioritise them and add three positives.
- Share with someone and ask whether each finding is clear.
Deliverable
An annotated critique document, around one to two pages.
Assignment
Assignment
Critique and redesign
Choose your top three findings from the exercise and redesign those parts of the flow. Show before and after, and explain how each change addresses the finding.
Deliverables
3 items
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
5 items
Summary
- Critique is specific, goal-based and useful.
- Method: understand the goal, do the task, review with principles, write observation, impact and suggestion, then prioritise.
- Include positives so good decisions survive.
- Critique predicts problems; testing confirms them.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
- Design Critiques: Encourage a Positive Culture to Improve Products (opens in a new tab)Nielsen Norman Group
- 10 Usability Heuristics for User Interface Design (opens in a new tab)Nielsen Norman Group
Your notes
Marking complete updates your course and roadmap progress.