What a critique is, and is not
A design critique is a structured conversation in which a designer shows work and others respond to it with the aim of improving it. It differs from casual opinion-sharing in that it is organized around goals. It also differs from approval: a critique is not a vote on whether the work is good, and it is not a place to decide on a final version.
Critique has long been a part of art and design education, and it is common in studios and product teams. Done well, it helps designers see their work through other people’s eyes and catch problems early, while changes are still cheap.
Set the stage
A few decisions before the session make a large difference.
- State the goal. The presenter explains what the work is for, who it is for and what stage it is in. Feedback on a rough sketch should differ from feedback on a near-final layout.
- Say what feedback you want. “I am unsure about the hierarchy on the first screen” gives reviewers something to focus on.
- Limit the scope. Looking at everything at once leads to scattered comments. One or two questions per round is often enough.
- Agree on roles. Someone presents, someone takes notes, and someone keeps time. The presenter should be free to listen.
Giving useful feedback
Good critique is specific, tied to goals and respectful. A few habits help.
Describe before you judge. Start by saying what you see: “The headline and the image are about the same size.” Then explain the effect: “I am not sure where to look first.” Description grounds the comment in something observable.
Connect comments to the purpose. “I do not like green” is a preference. “The green has low contrast against the background, which could make the text hard to read” points to a design reason, and color contrast is something the group can check. Ideas such as visual hierarchy, alignment and type scale give the group a shared vocabulary.
Ask questions. “What were you hoping people would notice first?” often leads to more useful discussion than a verdict does, and it avoids assuming you understand the intent.
Be balanced and clear. Mention what is working, so the designer knows what to keep, and be direct about what is not. Vague praise and vague criticism are equally unhelpful.
Suggest, do not dictate. Offering a possible direction is fine, but remember that the designer owns the solution. A comment like “Have you considered a larger scale contrast here?” invites exploration.
Stay on the work. Comment on the design, not the person.
Receiving feedback
Hearing criticism of something you made can be uncomfortable, and that is normal. Some practices make it easier.
- Listen first. Resist the urge to defend or explain every choice. If something needs clarifying, do it briefly.
- Take notes. Writing comments down helps you process them later, away from the room.
- Ask for clarification. If a comment is unclear, ask for an example or the reason behind it.
- Separate information from instruction. A comment tells you how one person experienced the work. You can decide what to act on.
- Look for patterns. If several people stumble at the same place, that is a stronger signal than a single opinion.
Taking time before responding is often wise. Some feedback looks different after a night’s sleep. The broader subject of design feedback, including how to handle unclear or harsh comments from clients, is worth reading separately.
Common formats
- Round-robin. Each person shares thoughts in turn, so quieter voices are heard.
- Silent review. Participants write comments on sticky notes or a shared board before discussing, which can reduce the influence of the loudest voice.
- Pairs. A one-to-one review is simple and less intimidating, especially for beginners.
- Structured prompts. Prompts such as “What is working? What is unclear? What could be explored?” keep everyone on track.
Online groups can use shared documents or comment threads to do the same, though tone can be harder to read in writing, so clarity and kindness matter even more.
Pitfalls to watch for
- Solution-jumping. Reviewers sometimes propose fixes before the problem is understood.
- Taste wars. Disagreements about personal preference can use up the whole session.
- Seniority bias. People may defer to the most experienced person in the room. Inviting others to speak first can help.
- Too many comments. A long list can overwhelm the designer. Prioritizing the top few themes is useful.
- No follow-up. If nothing is done with the notes, the exercise loses its value.
After the session
The designer reviews notes, groups comments into themes, and decides what to change. It can help to write a short list of next steps and then revisit the work with fresh eyes. Sharing a revised version with the reviewers, even briefly, closes the loop and builds trust in the process.
Critique is a skill that improves with practice, on both sides of the table. Over time, people who take part regularly often find they get better at spotting problems in their own work before anyone else points them out.