Design critique is a structured conversation about design work with the goal of making it better. It is one of the most valuable practices a design team can adopt, yet it is often misunderstood, poorly run, or avoided entirely. This lesson establishes the foundation for effective critique by clarifying what it is, what it is not, and how to create the right conditions for it.
Critique vs Feedback vs Opinion
These three terms are often used interchangeably, but they represent different things:
Opinion is a personal preference with no requirement for justification. "I don't like blue" is an opinion. It is about the speaker, not the work. Opinions have their place in casual conversation but are not useful in a design review.
Feedback is a reaction to the work, often informal. "The navigation feels confusing" is feedback. It identifies a problem but may not suggest a path forward or connect to a specific design goal. Feedback is useful but unstructured.
Critique is a structured evaluation of design work against defined objectives. "The navigation may not meet our goal of reducing time-to-task because the primary action is visually equal to secondary actions" is critique. It references a goal, identifies a specific issue, and implies a direction for improvement.
Practical tip: When someone in a review says "I don't like this," ask them to reframe it as critique: "What goal does this not meet, and why?" This simple redirect transforms unproductive opinions into actionable insights.
Why Critique Matters
Teams that practice regular critique produce better work for several reasons:
- Catches blind spots — Designers who have been deep in a problem often cannot see it from a fresh perspective. Critique provides that perspective.
- Raises quality — Knowing your work will be reviewed motivates you to think more carefully about your decisions.
- Builds shared understanding — When the team discusses design decisions together, everyone develops a shared sense of what "good" means.
- Develops skills — Both giving and receiving critique are learnable skills that improve with practice.
- Reduces rework — Issues caught in critique are far cheaper to fix than issues caught in development or after launch.
Setting Ground Rules
Effective critique requires psychological safety. People must feel comfortable sharing incomplete work and receiving honest feedback. Ground rules create that safety.
Essential ground rules for design critique sessions:
-
Critique the work, not the person — Say "the layout makes the hierarchy unclear" instead of "you made the hierarchy unclear." This distinction matters enormously for how feedback is received.
-
Start with the goals — Before any discussion, the presenter states the design goals and what specific feedback they are looking for. This focuses the conversation and prevents tangents.
-
Be specific — Vague feedback like "something feels off" is not actionable. Identify what, where, and why.
-
Connect to objectives — Every piece of critique should reference a user need, business goal, or design principle. "This doesn't meet accessibility contrast requirements" is connected to an objective. "I'd make this bolder" is not.
-
Separate observation from suggestion — First describe what you see and why it might be problematic. Then, if appropriate, offer a suggestion. The designer may have a better solution than what you would propose.
-
Assume positive intent — The presenter made their design choices for reasons. Ask about those reasons before proposing changes.
Structured Critique Format
A reliable structure keeps critique sessions productive and prevents them from devolving into unfocused discussions.
The "I like, I wish, What if" format:
- I like — Identify what is working well and why. This is not just politeness — it ensures good decisions are recognized and preserved.
- I wish — Identify what could be improved, framed as a wish rather than a demand. "I wish the primary action was more visually prominent" is more constructive than "Make the button bigger."
- What if — Propose alternatives or explorations. "What if we tried a full-width button here?" opens a conversation without prescribing a solution.
This format works well for teams new to critique because it balances positive reinforcement with constructive suggestions.
Creating a Critique-Friendly Culture
Ground rules only work if the team genuinely embraces them. As a leader or facilitator, model the behavior you want to see:
- Share your own work-in-progress openly, including rough ideas
- Receive critique gracefully without becoming defensive
- Thank people for honest feedback, especially when it is hard to hear
- Follow up on critique by showing how you incorporated feedback
Key Takeaways
- Critique is a structured evaluation against goals, not personal opinions
- Ground rules create the psychological safety needed for honest discussion
- Always start by stating design goals and what feedback you need
- Use formats like "I like, I wish, What if" to structure the conversation
- Model vulnerability by sharing your own unfinished work