Running a Design Critique: Give Better Feedback

How to run effective design critiques that improve work without damaging morale. Structured formats, facilitation techniques, and rules for giving actionable feedback.

A design critique is a structured conversation where a team evaluates design work against defined criteria. It is not a brainstorming session, not an approval meeting, and not a free-form opinion exchange. Done well, a critique improves the work, develops the team's design skills, and builds shared understanding. Done poorly, it wastes time and damages morale. The difference is almost entirely in the structure and facilitation.

Critique vs Feedback vs Review

These terms are often used interchangeably, but they describe different activities:

Feedback is informal, often one-on-one, and can happen at any time. "Hey, I noticed the button placement might confuse users" is feedback.
Critique is structured, group-based, and focused on improving the work against specific criteria. It happens at defined points in the design process.
Review is evaluative and decision-oriented. "Is this ready to ship?" is a review question. Reviews produce go/no-go decisions. Critiques produce actionable improvements.

The distinction matters because each activity requires different rules. Mixing them (trying to critique and approve in the same meeting) produces confusion and poor outcomes.

Setting Up the Critique

Define the Criteria

Before anyone looks at the design, establish what you are evaluating it against. Criteria might include:

Does it solve the user problem identified in the Define stage?
Is it consistent with the design system and brand guidelines?
Does it satisfy the usability heuristics?
Is it technically feasible within the project constraints?
Does it meet accessibility standards?

Without explicit criteria, critique devolves into "I like it" or "I don't like it," which is not useful. Criteria give the conversation structure and keep feedback objective.

Choose the Right Participants

A critique needs 3 to 6 participants with relevant expertise. More than 6 becomes unwieldy. Fewer than 3 limits perspective. Include people who can speak to user needs, technical feasibility, and design quality. The presenter (the designer whose work is being critiqued) participates but should mostly listen during the feedback phase.

Time-Box the Session

30 to 45 minutes is sufficient for most critiques. Longer sessions lose focus. Structure the time:

5 minutes: presenter shares context (the problem, the constraints, specific questions they want answered)
5 minutes: silent review (participants examine the design without discussion)
20 minutes: structured feedback
5 minutes: summary and next steps

The Presentation: Setting Context

The presenter should share:

The problem being solved. What user need or HMW question does this design address?
Key constraints. Technical limitations, timeline, brand requirements, or other factors that shaped the design.
Design decisions. What choices were made and why? This prevents participants from suggesting alternatives that were already considered and rejected for good reasons.
Specific questions. "I'm unsure about the navigation pattern for mobile" is more useful than "what do you think?" Specific questions focus the critique on areas where the designer needs help.

The presenter should not apologize for the work, pre-emptively defend decisions, or explain every detail. Present the context, then let the work speak for itself.

Giving Effective Critique

The "I Notice, I Wonder, What If" Framework

This structure keeps feedback constructive and specific:

"I notice..." Observations about the design, stated without judgment. "I notice the call-to-action is below the fold on mobile." This grounds the feedback in observable facts rather than opinions.
"I wonder..." Questions that explore implications. "I wonder if users will scroll far enough to see it." This invites discussion without prescribing a solution.
"What if..." Suggestions framed as possibilities. "What if the CTA were sticky at the bottom of the mobile viewport?" This offers alternatives without dictating changes.

This framework works because it separates observation from interpretation from suggestion. Many critique failures happen when participants jump directly to suggestions ("Move the button up") without explaining what they observed or why they think a change is needed.

Rules for Participants

Critique the work, not the person. "This layout creates a confusing hierarchy" is about the work. "You made a confusing layout" is about the person. The distinction matters more than you might think.
Be specific. "Something feels off" is not actionable. "The spacing between the header and the content area feels larger than necessary, which pushes the primary content down" is specific and useful.
Reference the criteria. Connect feedback to the established evaluation criteria. "Based on our usability heuristics, the error state here does not clearly indicate what went wrong" is more persuasive than "I don't like the error handling."
Offer alternatives, not mandates. "You should use a modal" is a mandate. "A modal, a toast notification, or an inline message could each address this; what are the trade-offs?" opens a productive conversation.
Acknowledge what works. Critique is not about finding problems. It is about improving work. If a design decision works well, say so. This reinforces good decisions and gives the designer confidence to build on them.

Receiving Critique

For the designer whose work is being critiqued:

Listen before responding. Your instinct will be to explain or defend. Resist it. Write down the feedback. Ask clarifying questions if needed ("Can you say more about what you mean by 'confusing hierarchy'?"). But do not argue during the critique session.
Separate the signal from the noise. Not all feedback is equally valuable. After the session, review the notes and look for patterns. If three people independently raise the same concern, it deserves attention. If one person dislikes a color, it might be a matter of preference.
You do not have to implement every suggestion. Critique provides input for your design decisions. You are still the designer. Evaluate each piece of feedback against the project criteria and your design judgment. Document your reasoning when you choose not to follow a suggestion.

Facilitating the Critique

A facilitator (someone other than the presenter) keeps the session on track:

Enforce the time structure. Cut off the presentation at 5 minutes if it runs long.
Redirect off-topic comments. "That is a great point about the overall brand strategy. Let us capture it and discuss it separately. For this session, let us focus on the navigation pattern."
Ensure everyone speaks. Actively invite quieter participants: "Sarah, you have expertise in mobile patterns. What do you notice about the mobile navigation?"
Prevent solution-jumping. When someone says "you should do X," redirect: "What problem would that solve? Let us make sure we understand the issue before proposing fixes."
Summarize at the end. Capture the key themes, specific concerns, and suggested explorations. Share written notes with the team after the session.

Design Critique in the Design Thinking Process

Critiques fit naturally at several points:

After Ideate: critique solution concepts before committing to prototyping. This prevents investing in concepts with fundamental flaws.
During Prototype: critique prototypes before user testing. This catches issues that would waste test participants' time.
After Test: critique proposed changes based on test results. Ensure that the fixes address root causes, not symptoms.

Critiques complement user testing because they bring expert evaluation (the team's design knowledge) while user testing brings user perspective (how real people experience the design). Both are necessary. Neither alone is sufficient.

Common Critique Failures

The praise-only critique. Nobody wants to be critical, so everyone says "looks great." The work does not improve. Fix: establish that the purpose is improvement, not approval. Ask specific questions that require substantive responses.
The pile-on critique. One person raises an issue and everyone agrees, creating momentum that amplifies minor concerns into major redesigns. Fix: use silent written feedback before group discussion to prevent groupthink.
The HiPPO critique. The Highest Paid Person's Opinion dominates. Fix: have the most senior person speak last, or use anonymous written feedback.
The redesign-by-committee critique. Participants collaboratively redesign the work during the session, producing a Frankensteined compromise. Fix: separate critique (identifying issues) from solution generation (the designer's job).

A well-run critique is one of the highest-leverage activities a design team can invest in, because it improves both the work and the team's shared judgment simultaneously. The collaborative design guide covers the broader set of cross-functional session formats that critiques fit within, while facilitation techniques will sharpen your ability to keep critique conversations productive rather than defensive. When presenting critique outcomes to stakeholders outside the design team, the presenting results guide helps translate design rationale into language that resonates with decision-makers. And for leaders building a culture where honest critique is expected rather than feared, the leadership guide addresses the organizational conditions that make critique safe and sustainable.

Design Thinker Labs Home · All Guides · How It Works · Pricing