How to Give a Good UX Design Critique

What is a design critique

A design critique is a structured conversation where a team looks at a design together and discusses how it could be improved. The goal is to evaluate the work against the problem being solved, user needs, and project objectives rather than personal preferences.

Critiques can happen throughout the design process, but they are especially useful while the work is still flexible enough to change. Sharing designs early gives other people a chance to identify problems, assumptions, inconsistencies, or constraints that the designer may not have noticed alone.

Why design critiques are useful

A critique gives you access to perspectives outside your own.

Developers can point out technical feasibility concerns, designers working on other parts of the product can notice inconsistencies, and people from other disciplines can bring a different perspective to the problem.

Regular critiques can also help teams:

Prepare the critique before the meeting

Before presenting anything, decide what you want to get from the critique.

Instead of asking people what they think about the design in general, explain which parts you want feedback on and which areas are outside the scope of the discussion.

Participants should also understand the problem before they see the solution. Give them the relevant context, including the users and their needs, design objectives, constraints, research, or requirements that influenced the work.

It also helps to explain how mature the design is. Feedback on an early exploration will be different from feedback on something that is approaching final review.

A simple agenda and clear time limits can keep the discussion focused.

Present the design with enough context

Start by briefly restating the problem, goals, users, and the feedback you are looking for.

Explain the reasoning behind important decisions where it is relevant, but avoid spending the session defending every choice you made. A critique should leave room for discussion.

Whenever possible, present the design from the user's perspective. Showing a journey, flow, storyboard, or prototype can provide more context than reviewing individual screens on their own.

How to give useful feedback

Useful feedback focuses on the design rather than the person who created it.

Comments should be specific enough for the designer to understand what the concern is and why it matters. Saying that something feels wrong or that you simply do not like it does not give the designer much to work with.

Instead, connect feedback to the user, the problem, the objectives, or the available evidence.

If the reasoning behind a decision is unclear, ask about it before making assumptions. Open-ended questions can help the designer explain their thinking and can lead to a more useful discussion.

Feedback can also include what is working well. The purpose of a critique is to understand the design as a whole, rather than only looking for mistakes.

Suggestions can be useful too, but they should remain suggestions rather than instructions the designer is expected to follow.

Keep the discussion focused

A facilitator can help:

It can also help to give everyone a moment to think or write down their feedback before the group discussion starts. This gives participants time to form their thoughts before other opinions begin shaping the conversation.

Most importantly, the session should remain focused on improving the design together. Presenting unfinished work can feel uncomfortable, so critiques work better when people can discuss problems openly without turning the session into a competition over who has the better idea.

Receiving and following up on feedback

When receiving feedback, listen before responding. Let people finish explaining their point and ask questions when something is unclear.

Not every comment needs to be implemented. Feedback still needs to be considered in relation to user needs, project goals, and the reasoning behind it. However, if the same concern appears repeatedly, it may be worth looking at more closely.

Document feedback during the session so important observations are not lost. Afterward, organize the notes into patterns and action points.

A critique should finish with a clear idea of what happens next, whether that means making changes, investigating something further, or bringing the work back for another round of feedback.

Conclusion

Design critiques work best when they are focused, constructive, and tied to clear goals. By giving the right context, asking thoughtful questions, and turning feedback into actionable next steps, teams can make stronger design decisions and improve the work together.