How do you give good design feedback?

Good design feedback is specific, user-centred, and separates observation from interpretation. Reference what you noticed in the design, explain the user problem it might cause, and suggest an alternative rather than a fix. The IDEO 'I Like / I Wish / What If' framework is a useful starting point. Avoid 'I like' or 'I don't like' without a rationale grounded in user goals or design principles.

What is the difference between a design critique and a design review?

A design review checks that a design is complete and meets agreed requirements -- it is a quality gate. A design critique is an evaluative conversation about whether the design effectively solves the user problem -- it is a learning process. Reviews tend to be pass/fail; critiques are exploratory and generative. Both have a place in a design process, but they serve different purposes and should not be conflated.

How should designers respond to criticism?

Designers should separate the work from their identity. When receiving a critique, listen without interrupting, take notes rather than arguing in the moment, and ask clarifying questions to understand the feedback rather than defend your decisions. It helps to remember that the critique is about the work's effectiveness for a user -- not a judgement of your skill. You are not obliged to act on every piece of feedback, but you should be able to explain your reasoning.

What makes feedback useful in UX design?

Useful feedback is anchored to user goals and specific enough to act on. It identifies an observation (what the reviewer noticed), connects it to a potential user problem (why it matters), and opens up an alternative (what could be tried instead). Feedback that amounts to 'I don't like this colour' or 'make it more modern' is not useful because it is not grounded in user need and does not point toward improvement.

Design Critique in UX: How to Give and Receive Feedback That Actually Improves the Work

Q: What is a design critique?

A design critique is a structured conversation about how effectively a design solves a user problem. It is distinct from a design review, which checks whether the work is complete or meets spec, and from informal feedback, which tends to be reactive and unstructured. In a critique, participants evaluate the design against user goals, not personal taste -- asking whether the design achieves its intended outcome and where it falls short.

Design critique is one of the highest-leverage skills in UX -- and one of the most poorly taught. Most designers learn to give feedback by osmosis, absorbing the habits of whoever ran the crits they sat in on. If those habits were good, they got lucky. Most were not.

This post explains what a design critique actually is, how to structure one, and how to give feedback that improves the work rather than just filling the room with opinions.

UX Academy (myuxacademy.com)'s Intermediate UX Design course includes live weekly critique sessions where you give and receive structured feedback on real design work. Or join a free UX Design Masterclass to see the approach in practice.

What is a design critique -- and what it is not

A design critique is a structured conversation about how effectively a design solves a user problem.

That definition has two important parts. "Structured" means it follows a deliberate process -- it is not a free-for-all. "Solves a user problem" means the evaluation is anchored to user goals, not to aesthetic preference or internal opinion.

Critiques are often confused with two other things:

A design review checks whether the work is complete and meets agreed requirements. It is a quality gate -- essentially a pass/fail check against a spec. Reviews are useful, but they do not evaluate whether the design does the right thing; only whether it does what was specified.

Informal feedback is reactive and unstructured. "This looks busy" or "I'm not sure about that colour" are informal observations -- they may contain a useful signal, but they are not critique. Informal feedback tends to reflect the reviewer's taste rather than the user's experience, and it rarely generates anything actionable.

A critique sits between research and final delivery in the UX design process. It is most useful after an initial round of design but before polish -- when there is still room to change direction.

How to structure a design critique session

A well-run critique follows a simple sequence. The designer leads; the reviewers respond.

1. Present the context

Before anyone looks at the design, the designer should frame it: What problem does this solve? Who is the user? What constraints shaped the decisions? What specific questions do you want the critique to address?

Skipping context is the most common mistake in critique sessions. Without it, reviewers default to personal preference -- because they have nothing else to anchor their feedback to. Context gives reviewers a frame of reference: does this design serve that user in that situation?

2. Share the work

Walk through the design without pre-emptively justifying every decision. Present it as it would be encountered -- ideally with a prototype or flow, not a static screen with no context. Explain what you were trying to achieve at each stage, but resist the urge to defend choices before anyone has said anything.

3. Gather feedback

Give reviewers time to look and form observations before speaking. Ask open questions: "What is clear?" "What is confusing?" "Where do you think a user would get stuck?" Start with observations -- what people notice -- before moving to interpretations -- what those observations mean.

4. Discuss

This is where critique becomes genuinely generative. Once observations are on the table, explore the design decisions behind them. Why was that choice made? What alternatives were considered? What would change if the user goal shifted? Good critique is a conversation, not a verdict.

5. Close with clarity

The designer should leave with a clear sense of which feedback they will act on and why. Not every piece of feedback warrants a change -- but every piece should be heard. A brief summary at the end ("I'm going to revisit the navigation, hold the colour change, and test the CTA wording") signals that the session produced actionable output.

How to give feedback that's actually useful

The most common failure mode in critique is feedback that expresses preference without evidence: "I don't like the layout," "It feels off," "Make it cleaner." This kind of feedback is not useful -- it tells the designer nothing about what to change or why.

Useful feedback has three parts:

1. An observation -- what you noticed in the design, described objectively. 2. A user implication -- why that observation might matter for the user experience. 3. An alternative -- not a prescribed fix, but an avenue to explore.

A practical structure: "I noticed [observation]. This might cause [user problem]. What if [alternative]?"

For example: "I noticed there are four calls to action on this screen. That might cause decision paralysis for a first-time user who is not sure what to do next. What if the primary action was more visually distinct?"

This is more useful than "there's too much going on" because it is specific, grounded in user experience, and opens a direction rather than demanding a particular solution.

The IDEO method: I Like / I Wish / What If

One of the most widely used frameworks for giving structured critique is the I Like / I Wish / What If method, developed at IDEO and the d.school at Stanford.

I Like identifies what is working and why -- specific, not generic praise.
I Wish surfaces a problem or friction point -- again, specific and user-centred.
What If opens an alternative possibility -- not a prescription, but an invitation to explore.

The value of this structure is that it starts from what works before moving to what does not, which keeps the conversation generative rather than purely critical. It also separates observation (I Like, I Wish) from possibility (What If), which prevents critique from collapsing into a list of demands.

When using this method, the same rule applies: ground each statement in user goals, not personal taste. "I like the contrast on the CTA because it will be easier for users to identify the next step" is useful. "I like the blue" is not.

How to receive a critique

Receiving critique is a skill that takes practice -- and it is harder than giving it, because the work is yours.

A few principles:

Listen without interrupting. The instinct to explain or defend while someone is still speaking is natural but counterproductive. Let the observation land before you respond.

Take notes, not offence. Writing down feedback as it is given serves two purposes: it signals that you are taking the critique seriously, and it gives you something to review later when the immediate emotional reaction has settled.

Ask clarifying questions, not rhetorical ones. "Can you say more about what you noticed?" is useful. "But didn't you notice that I already addressed that with the tooltip?" is not.

Remember you are not obliged to agree. A critique is not a vote. You can hear feedback, understand it, and decide not to act on it -- as long as you can explain your reasoning. The critique improves your decision-making; it does not make the decisions for you.

Common mistakes that undermine critique sessions

Defensive designers. When the person presenting spends most of the session explaining why their decisions were correct, the critique stops being a learning exercise and becomes a negotiation. If you find yourself defending before others have finished speaking, pause.

Feedback without context. Reviewers who have not understood the problem the design is solving cannot give useful feedback. If context was not presented, ask for it before commenting.

"I like / I don't like" without rationale. Taste-based feedback is the default when reviewers do not have a framework. If you find yourself in a session producing this kind of feedback, redirect: "Can we look at this from the user's perspective? What would they notice first?"

No clear close. Sessions that end without the designer naming what they will do with the feedback tend to produce work that does not change. Build the close into the structure.

Treating critique as approval-seeking. Some designers present work in critique hoping for validation rather than challenge. This misses the point. A critique that only confirms what you already believe is a waste of everyone's time.

How critique develops in practice

Critique is a skill that improves with repetition -- but only if the repetition is structured. Reading about feedback frameworks helps; applying them in real sessions, with real work, under light pressure, is what builds the habit.

At UX Academy, students give and receive live design critique every week throughout the Intermediate UX Design course. The critique sessions are built into the curriculum deliberately -- not as a bonus activity, but as a core part of how the design skills develop. By the end of the course, structured feedback is no longer something students have to think about; it is how they look at design.

This matters because when you enter a professional environment, critique is already happening -- in design reviews, in Slack threads, in stakeholder presentations. Arriving with the habit already formed means you can contribute usefully from day one, rather than spending your first few months learning to take feedback without flinching.

Critique in context: the broader design process

Design critique sits alongside usability testing as one of two primary ways to evaluate a design before it ships. Usability testing answers "can users complete this task?" -- it surfaces problems through observed behaviour. Critique answers "does this design reflect sound thinking?" -- it surfaces problems through structured reasoning.

Neither replaces the other. Wireframes and early prototypes benefit from critique before they are polished enough to test usably. Later-stage designs benefit from both. And ideation sessions that produce multiple directions can use critique to evaluate which direction is most worth developing.

The designers who progress fastest are usually the ones who are good in a room -- who can present their thinking clearly, hear feedback without getting defensive, and give feedback that moves the work forward. Critique is how that skill is built.

If you want to develop this skill in a live environment with weekly practice, Natalia Veretenyk leads the Intermediate UX Design course at UX Academy -- join the next cohort or start with a free UX Design Masterclass to see the approach firsthand.