By the end of this lesson you can
- Run a structured critique of wireframes.
- Give feedback tied to goals and evidence rather than personal taste.
- Receive feedback and turn it into clear next steps.
The idea
A design critique is a structured conversation about whether a design meets its goals. Wireframe critiques focus on structure, flow and content, not on visual style.
Set the context
The presenter explains the problem, the user, the goals, constraints and what kind of feedback they need ("I'm unsure whether the steps are in the right order"). Without context, feedback drifts towards personal preference.
Give useful feedback
- Tie comments to goals: "If the goal is fast reordering, the reorder button is hard to find."
- Ask questions: "What happens if someone has no saved address?"
- Be specific about location and reason.
- Mention what works, so it is kept.
Receive feedback well
Listen, take notes and ask clarifying questions. Avoid defending every decision; you can explain later. Not every comment needs action, but every comment deserves consideration.
Close the loop
End with a list of agreed changes and open questions, with owners.
Why it matters in real projects
Critique is how design improves before it reaches users. Structured critiques catch problems early, spread knowledge across the team and build shared ownership. Feedback grounded in goals is easier to act on and less personal, which keeps the team honest and the atmosphere healthy.
A realistic example
A designer presents wireframes for a parking app's payment flow. They state the goal (pay for parking in under 30 seconds), the main user (drivers standing next to their car) and the feedback wanted (flow order and clarity).
A developer asks what happens when the car's number plate is not recognised. A product manager notes that choosing a duration before the location means the price is unknown. Someone points out the large "Pay" button works well one-handed. The designer leaves with three agreed changes and one question for research.
Step by step
Prepare context
Write the problem, user, goals, constraints and feedback wanted.
Present the flow
Walk through the wireframes as a user would.
Silent review
Give reviewers a few minutes to note thoughts before discussion.
Discuss against goals
Focus each comment on whether the design meets the goals.
Capture actions
Record agreed changes, questions and owners.
Follow up
Share what changed after the critique.
Common mistakes
Mistake Presenting without context.
Instead Always explain goals and the kind of feedback needed.
Mistake Feedback about taste ("I don't like it").
Instead Explain how something helps or hurts the goal.
Mistake Defending every point.
Instead Listen first; decide later.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 45 min
Run a critique
Run a critique of a wireframe you made in this stage with at least two other people.
Steps
- Write a one-paragraph context.
- Present and give silent review time.
- Discuss and capture feedback.
- Write agreed changes and update the wireframe.
Deliverable
Context note, feedback list and updated wireframe.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Critique checks whether a design meets its goals.
- Context focuses feedback.
- Give specific, goal-based feedback; receive it openly.
- End with clear actions.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
Your notes
Marking complete updates your course and roadmap progress.