That thing where feedback sessions go nowhere?
You present your design. People give feedback. Some want to improve it, others want to approve it. Everyone leaves confused about what happens next. Sound familiar? Here's why this happens and how to fix it.
Most design teams treat critique and review as the same thing. They're not. Mixing them up creates confused meetings, frustrated designers, and designs that could have been much better.
Here's what actually works: Use critique to make designs better. Use review to make decisions about them. Simple as that.
Clear Definitions
Design Critique
Constructive feedback focused on improving the design. The goal is to make it better.
Design Review
Evaluation against criteria to make decisions. The goal is to determine next steps.
Key Differences
Understanding these differences will help you choose the right approach for each situation.
| Aspect | Design Critique | Design Review |
|---|---|---|
| Purpose | To improve and refine the design | To evaluate and make decisions |
| Timing | Throughout the design process | At specific decision points |
| Mindset | Collaborative and constructive | Evaluative and decisive |
| Participants | Designers, peers, subject experts | Stakeholders, decision makers, clients |
| Outcome | Actionable feedback for improvement | Approval, rejection, or revision request |
| Questions Asked | How can this be better? | Is this good enough? |
The bottom line: Critique asks "How can we make this better?" Review asks "Is this good enough to move forward?" Both questions are important, but they require different conversations.
When to Use Each
Use Critique When...
Early Design Exploration
When you're exploring different approaches and concepts
Example: Sketching wireframes and need input on information architecture
Iterative Refinement
When you have a direction but need to improve specific aspects
Example: Visual design is set but the interaction details need work
Skill Development
When someone wants to learn and grow as a designer
Example: Junior designer presenting work to learn best practices
Problem Solving
When you're stuck on a specific design challenge
Example: Complex navigation structure that users are struggling with
Use Review When...
Milestone Gates
At predetermined decision points in the project
Example: End of discovery phase, ready to move to detailed design
Client Approval
When external approval is required to proceed
Example: Presenting final designs to client for sign-off
Quality Assurance
Ensuring designs meet standards before handoff
Example: Pre-development review for accessibility and technical feasibility
Budget/Timeline Decisions
When business decisions affect design scope
Example: Determining which features to cut due to timeline constraints
What Makes Each Effective
Good Critique Has...
Specific and Actionable
Points to exact issues with clear suggestions
Example: "The login button gets lost against the blue background. Try white text on orange to match your brand colors."
User-Focused
References user needs and behavior
Example: "Users might not notice the search function in the sidebar. Consider placing it in the header where they expect it."
Constructive Tone
Assumes positive intent and offers help
Example: "I like the clean layout approach. What if we tried grouping related actions to reduce cognitive load?"
Evidence-Based
References design principles or user data
Example: "Research shows users scan in an F-pattern, so important info should align left."
Good Review Has...
Clear Criteria
Evaluates against predetermined standards
Example: "Does this meet our accessibility requirements? Does it align with brand guidelines?"
Business Context
Considers project goals and constraints
Example: "This design achieves the conversion goals we set, but may be too complex for our development timeline."
Decisive Outcome
Results in clear next steps
Example: "Approved to move forward, needs revision before approval, or explore alternative approach"
Risk Assessment
Identifies potential problems before implementation
Example: "This approach might confuse existing users who are familiar with the current navigation."
Common Misconceptions
These mistaken beliefs cause most of the confusion around design feedback.
"Critique and Review are the same thing"
Reality: They serve different purposes and require different approaches
Why this matters: Leads to ineffective meetings where people try to improve and approve at the same time
"You can skip critique and go straight to review"
Reality: Review without critique often results in poor design decisions
Why this matters: Designs that could have been much better get approved prematurely
"Critique should always be gentle and positive"
Reality: Good critique is honest about problems while remaining constructive
Why this matters: Real issues go unaddressed, leading to poor user experiences
"Only senior people can give good critique"
Reality: Anyone can provide valuable perspective when it's well-structured
Why this matters: Teams miss out on fresh perspectives and diverse viewpoints
"Review meetings should include everyone"
Reality: Review meetings should include decision makers and key stakeholders only
Why this matters: Meetings become unfocused and decisions take too long
Practical Examples
Here's how critique and review would work differently for the same design challenges.
New E-commerce Homepage Design
Critique Approach
Participants:
UX designers, visual designer, content strategist
Key Questions:
- • Does the information hierarchy guide users toward key actions?
- • How might we improve the product discovery experience?
- • What if we tested different hero section approaches?
Outcome:
Refined design with better product navigation and clearer value proposition
Review Approach
Participants:
Product manager, marketing director, development lead
Key Questions:
- • Does this achieve our conversion rate goals?
- • Can we build this within budget and timeline?
- • Does it align with our Q4 marketing strategy?
Outcome:
Approved to proceed to development with noted technical considerations
Mobile App Onboarding Flow
Critique Approach
Participants:
UX team, product designer, user researcher
Key Questions:
- • How can we reduce the number of steps without losing key information?
- • What patterns from successful apps could we adapt?
- • How might we make each screen more engaging?
Outcome:
Streamlined flow with progressive disclosure and personality
Review Approach
Participants:
Product owner, engineering manager, business stakeholder
Key Questions:
- • Will this onboarding improve our activation rates?
- • Is the development complexity justified by the business impact?
- • Does this support our user acquisition strategy?
Outcome:
Approved with request to A/B test against current onboarding
Implementation Guide
Here's how to start using critique and review effectively in your design process.
Define Your Process
Establish when critique and review happen in your workflow
Train Your Team
Help everyone understand their role in each type of session
Structure Your Sessions
Use the right format for the right purpose
Follow Up Effectively
Ensure both types of sessions lead to action
Want Better Design Feedback?
Understanding the difference is just the start. Learn specific techniques for giving constructive feedback that actually improves designs.
Design Critique vs Review Questions
Quick answers to help you get started
Master Design Critique
Get practical strategies for running effective critique sessions, structuring feedback, and building better design culture.
Weekly insights on design critique, team feedback, and professional growth. No spam, unsubscribe anytime.