What is a design critique?

A design critique is a structured conversation that evaluates a design against its goals. It is not a taste contest.

Every designer gets feedback. The question is whether it's useful. A comment dropped in a chat thread, a hallway "have you tried making it blue?", or a manager's opinion in passing are all drive-by feedback: reactions without context. The person reacting doesn't know what problem you're solving, what constraints you have, or what stage the work is at.

A critique fixes this by adding structure. The work is framed before anyone reacts, the goals are stated up front, and every comment is measured against those goals. The value of a critique comes from the shared frame: everyone in the room evaluates the same design against the same goals, instead of against their personal preferences. That's why a thirty-minute critique often moves a design further than a week of scattered comments.

    keywords
  • #DesignCritique
  • #Feedback
  • #SharedGoals

The presenter's job

A critique lives or dies on how the work is framed. Before showing a single screen, do three things:

Frame the problem. Remind the group what user problem this design solves and who it's for. One or two sentences is enough: "Returning customers abandon checkout when they're forced to re-enter shipping details."

State the goals. Say what success looks like for this design, because that's the yardstick the group will use. "The goal is to let returning users complete checkout in one screen without creating an account."

Say what kind of feedback you need, and what's already decided. Feedback on a rough flow is wasted if everyone comments on button styling. Be explicit: "I want feedback on the order of steps. The visual style and the payment provider are already decided, so please skip those." Telling people what is out of scope is just as important as telling them what is in scope.

Then show the work and stop talking. Presenters who narrate every screen defensively leave no room for the group to think.

    keywords
  • #FrameTheProblem
  • #StateGoals
  • #ScopeFeedback

The critic's job

Giving good critique is a skill, and it rests on three habits.

Critique against the goals, not your preferences

The difference is in the sentence structure. "I don't like the stepper" is a preference. "The stepper doesn't meet the one-screen goal because it splits shipping and payment into separate views" is a critique. Useful critique always connects an observation back to a stated goal: this doesn't meet the goal because... If you can't connect your comment to a goal, either the goals were framed too narrowly or your comment is a preference. Say which one it is.

Ask questions before prescribing solutions

Designers often had a reason for the choice you're about to attack. Ask first: "What led you to put the coupon field above the order summary?" Maybe research showed users hunt for it. Maybe it was arbitrary. Questions surface the reasoning behind a decision; prescriptions bury it. Once you understand the intent, your feedback gets sharper and less redundant.

Be specific and kind

"This feels off" gives the presenter nothing to act on. "The error message appears below the fold, so users on small screens won't see why the form failed" is specific enough to fix. And aim the critique at the work, never the person: be hard on the work, soft on the person. Say "the flow loses the goal here," not "you got lazy here." Vague praise is as useless as vague criticism, so when something works, say exactly why.

    keywords
  • #GoalsNotTaste
  • #AskQuestions
  • #SpecificAndKind

Formats that work

You don't need an elaborate ritual. Three simple formats cover most teams:

Round-robin. Go around the room and each person gives one piece of feedback before anyone gives a second. This stops one loud voice from consuming the session and guarantees everyone contributes.

Silent notes first. Everyone writes their feedback silently for five minutes before discussion starts. Writing before talking prevents the first comment in the room from steering everyone else's opinion.

I like / I wish / I wonder. Each comment starts with one of three openers: "I like" for what works, "I wish" for what falls short, "I wonder" for open questions. The phrasing keeps feedback constructive without softening it into mush.

    keywords
  • #RoundRobin
  • #SilentNotes
  • #LikeWishWonder

Receiving critique

The hardest part of critique is sitting through it without defending every choice. The instinct to explain is strong, but a critique that turns into a debate produces nothing.

Use a simple discipline: capture, clarify, decide later. Capture every comment in writing, even the ones you disagree with. Clarify when a comment is ambiguous: "When you say the summary is buried, do you mean it's below the fold or that it's visually flat?" Then decide later, away from the room, which feedback to act on. Critique informs your decisions; it doesn't make them for you. Defending in the moment teaches people to stop giving you honest feedback.

    keywords
  • #Capture
  • #Clarify
  • #DecideLater

Building a critique culture

One good session is easy. A culture takes habits:

Run critiques on a regular cadence. A weekly slot on the calendar means designers plan for feedback instead of scrambling for it the day before a deadline. Regularity also lowers the stakes: when critique happens every week, no single session feels like a trial.

Juniors speak first. Once a senior designer has spoken, everyone else quietly adjusts toward their opinion. Reverse the order and you get the room's honest read.

Seniors don't anchor. Senior designers and leads should hold their opinions until the end, ask more questions than they answer, and flag their comments as one voice among many. A critique where everyone converges on the most senior person's opinion is just a slow way of asking one person what to do.

    keywords
  • #RegularCadence
  • #JuniorsFirst
  • #NoAnchoring

Takeaways

Critique is a conversation about whether the work meets its goals, run with enough structure that everyone can be honest.

Frame the problem and the goals before showing the work, and say what feedback you need. As a critic, tie every comment to a goal, ask before you prescribe, and stay hard on the work but soft on the person. As a presenter, capture and clarify instead of defending, and decide later. Do it every week, and let the quietest voices go first.