Fundamentals
What Is a Design Critique? A practical guide to useful feedback
Critique is not a verdict on whether a designer is good. It is a way to look at the work together, understand what it is doing, and decide what would make it stronger.
The short read
Improve, do not approve
Use critique while the work can still change and the designer needs another perspective.
Frame the question
Share the objective, current stage, constraints, and the kind of feedback that would help now.
Close the loop
Sort the feedback, choose what changes, and explain what you decided when other people need to know.
A design critique helps the work change
A design critique is a focused conversation about whether a piece of work is supporting its objective. The designer brings the work, its context, and a useful question. Reviewers bring observations, interpretations, and possibilities the designer may not be able to see from inside the project.
The point is not to collect as many opinions as possible. It is to see the work more clearly and make a better-informed decision. A critique can happen between two people at a desk, in a class, in an async document, or with a cross-functional team. Structure should fit the question rather than becoming a ceremony of its own.
Critique, review, and feedback are related—not identical
Teams use these words differently. The safest move is to name the outcome you need instead of assuming everyone shares the same definition.
Design critique
Improve the work
- Use it while the work can still respond to feedback.
- Ask what is helping or getting in the way.
- Leave with observations, options, and priorities.
Design review
Make a decision
- Use it when criteria and a decision owner are clear.
- Ask whether the work can move forward and under what conditions.
- Leave with a decision, owner, and next checkpoint.
Feedback is the broad category: a reaction, comment, question, or suggestion about the work. It becomes useful critique when it is connected to the objective and specific enough to inform a design decision. For a deeper comparison, read Design Critique vs Design Review.
Prepare the question, not a defense
Reviewers need enough context to interpret the work without being told what to think. A short frame is usually more useful than a polished presentation.
Bring these five things
- The objective: what this work needs to help a person understand, feel, or do.
- The audience and situation: who encounters it, where, and with what context.
- The current stage: early direction, working draft, refinement, or readiness check.
- The constraints: what cannot change, what is provisional, and what evidence is already known.
- The question: the decision or uncertainty where another perspective would help most.
Run the critique as a sequence
The sequence matters because explanations and senior opinions can shape what everyone else notices. Let the work register before the room starts solving it.
- 1Frame the work and the question.State the objective, audience, stage, constraints, and what kind of help would be useful today.
- 2Give everyone a quiet first look.Let people inspect the work and record what they notice before discussion begins.
- 3Start with observations.Name what is present, missing, prominent, repeated, or difficult to follow without assigning intent yet.
- 4Discuss meaning and tradeoffs.Connect observations to the audience and objective. Ask what changes if one direction is chosen over another.
- 5Explore the smallest useful move.Offer a recommendation or a few distinct options. The designer keeps ownership of the decision.
- 6Close with a record.Capture the priority, unresolved questions, owner, and next checkpoint. Not every comment needs to become work.
Make feedback specific without making it absolute
Useful critique distinguishes what is visible from what it may mean and what the designer might try next. That keeps professional judgment honest without reducing design to a checklist.
Move from reaction to critique
- Instead of “I don’t like it”
- Name the visible choice and the effect it has on the question being asked.“The project title is quieter than the category label, so I read the taxonomy before I understand the work.”
- Instead of redesigning it
- Explain the problem before offering a solution, then leave room for another direction.“The next action is hard to distinguish. You could increase its contrast, reduce the competing actions, or change its position.”
- Instead of claiming user behavior
- Use calibrated language unless research or observed behavior supports the claim.“A first-time visitor may have trouble finding the price” is more honest than “users will leave.”
- Instead of listing everything
- Prioritize the finding that changes the work most, then name supporting observations that explain it.A critique can be broad without making every issue equally important.
Receiving critique is an editing job
You do not have to agree with every comment or implement it literally. Your job is to find the signal, compare it with the project's evidence and constraints, and decide what deserves a response.
- Listen for the problem underneath a proposed solution.
- Ask a clarifying question when you cannot connect a comment to the work.
- Notice repeated friction, but do not treat repetition alone as proof.
- Sort findings into change now, test or investigate, keep as-is, and outside this scope.
- Record why you chose a direction so the next version is a decision, not a pile of edits.
Choose the lightest format that fits the question
- Desk critique
- Use for one focused decision while the work is still moving.Fast, conversational, and easy to repeat.
- Async critique
- Use when people need time to inspect the artifact or work across schedules.Include the frame and deadline so comments do not become an unbounded backlog.
- Facilitated group critique
- Use when several perspectives are relevant to the same design question.Silent first review and clear facilitation reduce anchoring and repetition.
- Gallery or classroom critique
- Use when comparison across several works helps people see principles and possibilities.Give each designer a clear question so the room does not reward only the loudest work.
- Automated critique
- Use for a fast outside read when a person is unavailable or you want to prepare for human critique.Keep the artifact, question, and reviewer limits visible.
Use AI critique without outsourcing your judgment
AI can provide a useful first outside perspective on visible work. It may notice hierarchy, clarity, consistency, or readiness issues you have stopped seeing. It may also misread a detail, miss context, or sound more certain than the evidence deserves.
Give it the same things a person needs: the actual artifact, the audience, the current stage, and the question. Then inspect whether the response points to real evidence and helps you make a better decision. A polished answer is not proof that the answer is right.
Free First Read
Find the center of gravity
- A readiness verdict for the submitted work
- One priority move and why it matters
- One strength when the evidence supports it
- A clear ready-enough standard
$9 Full Crit
Open the wider review
- The complete critique across the important dimensions
- Every finding, notes, questions, and exports
- One newly generated revision check for the project
- Scope matched to the submitted artifact
See what The Crit actually checks and where an automated second opinion has limits.
A critique culture is built after the meeting, too
A recurring calendar invite is not enough. People need evidence that unfinished work is welcome, seniority does not decide what is true, and thoughtful feedback leads somewhere.
- Keep critique about the work and its objective, not the designer’s competence.
- Let people observe before the most senior person gives an opinion.
- Invite the perspectives the question needs rather than everyone who wants visibility.
- Make it safe to disagree, keep a direction, or ask for better evidence.
- Show what changed, what did not, and why when other people contributed to the decision.
Sources and further reading
- Nielsen Norman Group: Design Critiques—Encourage a Positive Culture to Improve Products — framing, facilitation, presenting, and critique pitfalls.
- Figma: How we do design critiques at Figma — several critique formats and the importance of choosing one for the presenter's need.
- Nielsen Norman Group: Closing the Loop After a Design Critique — how communicating what changed supports future participation.
- W3C: Web Content Accessibility Guidelines 2.2 — the current technical source for web accessibility criteria.
QuestionsAnswers
Questions, answered.
A few practical details before you keep going
Share this resource
Written by
Nikki KippleProduct Designer & Design Instructor
Designer, educator, founder of The Crit. I've spent years teaching interaction design and reviewing hundreds of student portfolios. Good feedback shouldn't require being enrolled in my class — so I built a tool that gives it to everyone. Connect on LinkedIn →
Want critique on the work in front of you?
Share one design, page, or project. Your free First Read identifies the decision most worth revisiting; the $9 Full Crit covers the wider review and one revision check.