What is Design Critique?
A design critique is a structured discussion where team members provide specific, actionable feedback to improve design work. It's not about approval or personal preferences—it's about making the design better serve users and business goals. If you're unclear on the difference between critique and review, our guide ondesign critique vs design review breaks down when to use each approach.
Design Critique
Collaborative improvement process
- • Happens during design
- • Goal: improve quality
- • Focus: user and business needs
- • Outcome: better design
Design Review
Approval and sign-off process
- • Happens at milestones
- • Goal: approval to proceed
- • Focus: requirements met
- • Outcome: go/no-go decision
General Feedback
Informal opinions and reactions
- • Happens anytime
- • Goal: share thoughts
- • Focus: personal preference
- • Outcome: mixed results
Why Most Critiques Suck
Bad critiques happen when there's no structure, unclear goals, or the wrong people in the room. They devolve into personal preferences ("I don't like blue") or vague complaints ("this doesn't feel right").
Good critiques have clear rules, focus on specific improvements, and connect feedback to user goals. Everyone leaves knowing exactly what to do next.
The Golden Rules
These five rules turn chaotic feedback sessions into productive improvements. Non-negotiable for any team that wants critiques to actually work.
Be specific
Instead of "this doesn't work," say "the CTA button lacks contrast and might not be accessible."
"This feels off"
"The spacing between these cards creates too much visual separation - consider reducing from 32px to 24px"
Make it actionable
Every piece of feedback should give the designer a clear next step.
"The colors are wrong"
"Try using the secondary blue (#4F46E5) instead of this bright blue to match our brand palette"
Focus on the work, not the person
Critique the design decisions, not the designer's abilities.
"You always make things too complicated"
"This flow has 6 steps where users might expect 3-4. What if we combined steps 2 and 3?"
Reference goals and users
Connect feedback to business objectives and user needs.
"I don't like the layout"
"Since our users scan quickly, this layout buries the key benefits below the fold"
Suggest, don't dictate
Offer options and reasoning rather than demands.
"Change the font to Arial"
"Consider a more readable font like Inter or Roboto for better accessibility at small sizes"
Step-by-Step Process
Every effective critique follows this four-step structure. It keeps discussions focused and ensures you get actionable outcomes, not just opinions.
Present
The designer sets context: user goals, constraints, and specific feedback needed.
What to Cover (5-7 minutes)
- • Project goals and user needs
- • Key constraints (technical, business, time)
- • Specific areas where you want feedback
- • Current design decisions and reasoning
Pro tip: Be specific about what kind of feedback you need. "How does this flow feel?" gets better input than "What do you think?"
Discuss
Team provides structured feedback following the golden rules.
Discussion Framework (15-20 minutes)
- • Start with what's working well (builds confidence)
- • Focus on specific, actionable improvements
- • Reference user goals and project constraints
- • Ask questions to understand design decisions
Facilitate well: Keep discussions on track, redirect vague feedback, and ensure everyone gets heard. Timebox each topic.
Capture
Document key decisions, open questions, and action items while they're fresh.
What to Document (3-5 minutes)
- • Top 3 improvements to implement
- • Design decisions that were validated
- • Questions that need research or stakeholder input
- • Any major direction changes
Tools: Shared docs, Figma comments, Notion pages, or even photos of whiteboard sketches. Pick something everyone can access later.
Next Steps
Clear actions, owners, and timeline so momentum doesn't die.
Before Everyone Leaves (2-3 minutes)
- • What specific changes will the designer make?
- • What questions need answering from other stakeholders?
- • When will revised designs be ready for review?
- • Who needs to be looped in on major changes?
Follow through: Check in during standups or next critique. Great feedback is worthless if it never gets implemented.
Common Formats
Different formats work for different team sizes, project types, and goals. Here are four proven approaches you can adapt for your situation.
Round-Robin
Regular team critiques, multiple projects
Process
- 1Designer presents work (5 mins)
- 2Silent observation period (2 mins)
- 3Each person gives feedback in turn (3-4 mins each)
- 4Designer responds and asks clarifying questions (5 mins)
- 5Next designer presents
Pros
- • Everyone gets to speak
- • Structured and predictable
- • Good for introverts
Cons
- • Can feel formal
- • Longer sessions
- • Less spontaneous discussion
Silent Critique
Written feedback, detailed analysis, async elements
Process
- 1Designer posts work in shared space (Figma, Slack, etc.)
- 2Team reviews silently and leaves written comments (10 mins)
- 3Open discussion about common themes (10 mins)
- 4Designer summarizes key takeaways (5 mins)
Pros
- • Thoughtful, written feedback
- • Less groupthink
- • Introverts can participate fully
Cons
- • Less energy and collaboration
- • Requires good writing skills
- • Async elements slow iteration
Dot Voting
Multiple concepts, quick decisions, consensus building
Process
- 1Designer presents 3-5 concepts (10 mins)
- 2Team silently places dots on strong/weak elements (3 mins)
- 3Discuss patterns and clusters (10 mins)
- 4Identify top direction and specific improvements (2 mins)
Pros
- • Visual feedback patterns
- • Quick consensus
- • Works with larger groups
Cons
- • Less detailed feedback
- • Can become popularity contest
- • Needs clear voting criteria
I Like, I Wish, What If
Early concepts, brainstorming, positive team culture
Process
- 1Designer presents work (5 mins)
- 2I Like: What's working well (5 mins)
- 3I Wish: What could be improved (10 mins)
- 4What If: New ideas and possibilities (8 mins)
- 5Synthesize and prioritize (2 mins)
Pros
- • Balanced positive/constructive
- • Generates new ideas
- • Builds confidence
Cons
- • Can feel formulaic
- • May avoid tough feedback
- • Longer format
Remote Critique Tips
Remote critiques require different tools and approaches. You can't rely on in-person energy and spontaneous collaboration, so structure and async elements become even more important.
Use Figma Comments Effectively
Drop contextual comments directly on designs rather than general feedback.
How to: Click on specific elements, use @mentions for clarity, and include screenshots for complex feedback.
Record Loom Videos
Screen recordings show your thinking process and feel more personal.
How to: Record 2-3 minute Loom videos walking through designs and explaining your feedback.
Create Async Threads
Use Slack threads or comments for ongoing discussions about specific design decisions.
How to: Start threads for each major topic, keep discussions organized, and summarize decisions.
Shared Miro Boards
Visual collaboration spaces for ideation and feedback synthesis.
How to: Create feedback boards with sticky notes, voting dots, and clear sections for different types of input.
Synchronous Video Calls
Some feedback requires real-time discussion and energy.
How to: Schedule focused 30-min video critiques for complex projects or when team alignment is needed.
Remote Critique Checklist
Before the Session
- ✓ Share designs 24 hours ahead
- ✓ Include context and specific questions
- ✓ Test video/screen sharing setup
- ✓ Send calendar invite with agenda
During the Session
- ✓ Record for team members who can't attend
- ✓ Use shared documents for note-taking
- ✓ Share your screen while presenting
- ✓ Use breakout rooms for larger groups
Why Critiques Fail
Most critique sessions fail for predictable reasons. Here's what kills productive feedback and how to fix it before it happens.
No Clear Structure
Impact: Conversations meander, time is wasted, designers leave confused about next steps.
Solution: Use a consistent format like present → discuss → capture → next steps. Set time limits.
Ego and Defensiveness
Impact: Designers shut down, team members avoid giving honest feedback, quality suffers.
Solution: Establish psychological safety. Start with what's working. Frame feedback as helping the work succeed.
Vague Feedback
Impact: "Make it pop" and "I don't like it" provide no actionable direction.
Solution: Require specific, actionable feedback. Ask "what exactly would you change and why?"
Wrong People in the Room
Impact: Stakeholders derail with personal preferences or people without context give irrelevant feedback.
Solution: Invite only people who understand the project context and can contribute meaningfully.
No Follow-Through
Impact: Great feedback gets lost, same issues repeat, team feels their input doesn't matter.
Solution: Document decisions, assign owners, and follow up in next critique or standup.
Red Flags to Watch For
- • Discussions that go over 45 minutes without clear outcomes
- • The same feedback issues coming up week after week
- • Designers seeming defensive or checked out during feedback
- • Feedback that's mostly personal preference ("I like/don't like")
- • Team members avoiding giving honest feedback
How to Receive Critique
Receiving feedback well is a skill. It determines whether critiques improve your work or turn into defensive battles. Here's how to get the most value from every session.
Listen First, Defend Later
Your first instinct might be to explain why you made certain choices. Instead, listen to understand the feedback fully.
In practice: Take notes during feedback. Ask clarifying questions only after the person has finished their full thought.
Separate Yourself from Your Work
Critique of your design isn't critique of you as a person or professional.
In practice: Use phrases like "the design" instead of "my design" when discussing feedback. It creates psychological distance.
Look for Patterns
If multiple people mention the same issue, it's probably real—even if you disagree.
In practice: Keep a tally of similar feedback points. Three people saying the same thing is data, not opinion.
Ask Questions, Don't Argue
Instead of explaining why they're wrong, ask questions to understand their perspective better.
In practice: "Can you help me understand what makes this feel complicated to you?" vs. "Actually, I made it simple because..."
Filter Through Your Goals
Not all feedback is good feedback. Evaluate suggestions against your project objectives.
In practice: Ask yourself: "Does this feedback help achieve the user goal? Does it solve the business problem?"
The Designer's Critique Mindset
Productive Responses
- • "Can you help me understand why?"
- • "What would you try instead?"
- • "Let me make sure I understand..."
- • "That's a pattern I'm hearing from others too"
Avoid These
- • "Actually, I did that because..."
- • "The client/stakeholder wanted it this way"
- • "I tried that but it didn't work"
- • "You don't understand the constraints"
Templates & Frameworks
Copy-paste templates you can use immediately. Customize for your team and project needs.
Critique Agenda Template
Design Critique - [Date]
Project: [Project Name]
Designer: [Name]
Duration: 30 minutes
Context (5 mins)
• User goals:
• Business objectives:
• Key constraints:
• Specific feedback needed:
Discussion (20 mins)
• What's working well?
• Areas for improvement
• Questions/clarifications
Next Steps (5 mins)
• Actions: [Who, What, When]
• Follow-up needed:
• Next critique date:
Feedback Framework
✅ I Like
What's working and should be kept:
- • Clear user flow
- • Strong visual hierarchy
- • Consistent with brand
🤔 I Wonder
Questions and areas to explore:
- • How will this work on mobile?
- • What happens when content is longer?
- • Is this accessible to screen readers?
💡 What If
Specific suggestions to try:
- • Try increasing button contrast
- • Consider left-aligning this text
- • Add micro-interactions here
Async Feedback Template (Slack/Comments)
🎯 Context:
[Brief project context and what feedback you need]
✅ Works well:
[Specific things that are effective]
🔍 Consider:
[Specific, actionable suggestions]
❓ Questions:
[Clarifying questions about decisions or constraints]
⚡ Priority:
[High/Medium/Low - helps designer prioritize]
Everything You Need to Know
Quick answers to help you get started
Stay in the Loop Design Updates
Get practical design tips and new updates. No spam, unsubscribe anytime.
Related Resources
Best Design Critique Tools
Compare AI feedback, async tools, and collaborative platforms to find your perfect setup.
Building Design Team Culture
Create psychological safety and productive collaboration in design teams.
Design Feedback Best Practices
Master the art of giving and receiving constructive design feedback.