Admin"I don't love it" is feedback that feels honest and helps nobody. Good design critique is a specific skill, on both sides of the conversation — and it's very learnable.
Critique the work, not the person
"This hierarchy makes the CTA hard to find" is feedback about the work. "You always make this mistake" is feedback about the person, and it triggers defensiveness that shuts down honest conversation. The distinction sounds obvious in theory and is very easy to blur in the moment — it's worth actively watching for.
Anchor feedback to a goal, not a taste
"I don't like this color" is a preference, and preferences are hard to act on productively. "This color doesn't meet contrast requirements for the error state" or "this color doesn't match what we said we wanted — approachable and calm" is feedback tied to a stated goal, and it's immediately more useful and less personal.
Ask questions before asserting
"What was the reasoning behind this layout?" often surfaces context you were missing — a constraint, a piece of user research, a technical limitation — before you critique a decision that actually had good reasons behind it that just weren't visible to you yet.
Receiving feedback: separate the signal from the delivery
Feedback delivered clumsily can still contain a completely valid point. Try to extract the underlying observation — "users might not notice this button" — even if the delivery felt blunt or the tone wasn't ideal. Getting defensive about tone means you can miss genuinely useful signal.
Not all feedback deserves to change your design. All feedback deserves to be genuinely considered before you decide that.
Don't defend on the first response
The instinct to immediately explain "why I did it that way" often reads as dismissing the feedback, even when that's not the intent. Try writing it down and responding after sitting with it for a bit — you'll often find you actually agree with more of it than your first reaction suggested.
The takeaway
Good critique is specific, tied to a shared goal, and delivered without attacking the person. Good feedback-receiving means separating the useful signal from an imperfect delivery, and giving yourself a beat before responding defensively.
Keep reading
Related articles
The Beginner's Guide to Figma: Design Your First Screen
Frames, components, auto-layout and prototyping — everything you need to go from blank canvas to a polished mockup.
Color Theory for People Who Aren't Designers
The three rules that make any palette look intentional — without a design degree.
AI Design Tools: Where They Help and Where They Still Fall Short
Generative AI can produce a decent-looking screen in seconds. It still can't do the part of design that actually matters most. Here's the honest split.
Discussion
Leave a comment
Your email stays private and is never published.