How to Run a Design Critique Session That Actually Improves the Work

A good design critique is one of the fastest ways to level up a team's work — but a bad one wastes an hour and leaves everyone defensive. The difference is almost never talent; it's structure. When people know what they're reacting to, what kind of feedback is wanted, and how to phrase it, critiques get sharper and kinder at the same time. Here's a repeatable way to run one, whether you're reviewing a landing page, an app flow, a logo, or a pitch deck.

Set the frame before anyone speaks

Most critiques go sideways in the first two minutes because the presenter hasn't told the room what they need. Before showing anything, the person whose work is up should answer three quick questions:

• What is this trying to do? The goal, the audience, and the constraint (deadline, brand, platform).
• Where is it in the process? Rough sketch, near-final, or shipped? Feedback on a wireframe should not sweat pixel colors.
• What kind of feedback do you want? "Does the hierarchy read?" is a very different ask than "Is this on brand?"

This one habit prevents 80% of unhelpful comments, because reviewers stop guessing and start aiming.

Give reviewers silent time first

Don't open with "So, what does everyone think?" — the loudest person sets the tone and everyone anchors to them. Instead, give the room two to three minutes of silence to look and jot notes. Silent starts surface more diverse observations and stop the critique from becoming a debate between two strong voices while everyone else nods along.

Structure the feedback so it's usable

Vague praise and vague criticism are equally useless. Ask reviewers to frame comments in a way the presenter can act on. A simple, reliable pattern:

• Observation: what you literally notice ("my eye goes to the footer before the headline").
• Impact: why it matters ("so I miss the main offer").
• Suggestion or question: "could the headline get more contrast?" — offered, not mandated.

Separate the observation from the fix. The presenter owns the solution; reviewers own pointing at the problem clearly. And keep it about the work, never the person — "this section" not "you."

Capture reactions in the moment

The most honest critique feedback is often the instant gut reaction — the split-second "wait, what?" before people politely soften it. Those first impressions are gold, but they evaporate the second the meeting ends. If your team is remote or async, it's hard to get everyone in a room at once anyway.

This is where a quick video reaction tool helps. With Snark you can drop your design, mockup, or deck behind a link and have reviewers record short video critiques on their own time — you see their real face and hear their tone, which carries nuance that a typed comment flattens. It's free, works on any phone, and needs no app to install — reviewers just tap the link and talk. It's an easy way to collect candid, structured feedback from people who could never make the same meeting.

Close the loop

End every critique by having the presenter play back what they heard: "So the big themes are hierarchy and the CTA — I'll rework those, and I'm leaving the color as-is for now." This does two things: it confirms the presenter actually absorbed the feedback, and it gives reviewers the satisfaction of being heard, which makes them show up engaged next time. Assign the takeaways to a specific next step and a date, or the whole session becomes opinions with no follow-through.

Run critiques this way for a few cycles and something shifts: people stop bracing for them and start requesting them. That's the goal — feedback that's frequent, specific, and safe enough that the work genuinely gets better.

Want to collect honest video critiques from your team without scheduling a single meeting? Try it free at snark.video/critique.