“The most useful critique I ever gave was when I stopped scoring the mock and started naming the single decision that would make or break the idea. Designers want ownership, trust, and accountability, and feedback that respects that lands very differently than a list of fixes.”
“The most useful critiques I run start with the designer stating what stage the work is at and what feedback they actually need, because half the room will otherwise solve a different problem than the one in front of them. I ask more than I tell: clarifying the intent and constraints first usually surfaces better options than jumping in with fixes.”
“The critiques that actually helped me were the ones that stung a little, because sharing work is vulnerable and hearing what's broken never stops being hard. Now I try to make feedback sessions feel safe enough that people can be direct without being cruel: say what you see, say why it matters, and offer a path forward.”
“I ground my critiques in what the design is trying to solve before I say what I would change, because feedback without that context usually just becomes personal taste. I also try to name the tradeoff: this helps X but it might hurt Y, so the designer can decide rather than feel ordered around.”
“I learned at Facebook that a critique only helps when the room feels safe enough for raw, embarrassing work to show up. We kept ours small, named a facilitator, and asked the presenter to state exactly what feedback they needed before anyone spoke. The trust is the product.”
“I always start a critique by asking what the designer needs from the room, because feedback without a clear goal becomes performance review by committee. Then I make people say what works before they tear into what doesn't, which keeps the session from becoming a pile-on.”
“I run critiques as conversations with a clear agenda, not presentations where everyone reacts. I start by naming what works, then point to the one or two things that feel off and why, and I ask the designer what they were trying to solve before I suggest a fix.”
“I used to run critiques where everyone pointed out what was broken, and the designer left with a list of fixes but no clearer sense of what the work was actually trying to do. Now I start by asking what problem this solution is betting on, because the rest of the feedback only lands once that bet is named.”
“I stopped doing critiques where everyone shares an opinion and started making the room answer one question: what does this need to do for the user right now. That alone kills most noise.”