Bad design feedback sounds like taste: "I do not love it", "make it pop", "can we try blue". Good design feedback sounds like a question about the goal: "will a first-time user know what to do here?" The difference is learnable, whether you are a designer, a product manager or a founder.
Start from the goal
Before any feedback, the presenter states what the design is for and what kind of feedback they need. "This is the checkout for repeat buyers. I want feedback on the flow, not the visuals yet." Without this, feedback scatters across everything at once.
Describe, then interpret, then suggest
- Describe what you see. "The total is below the fold on my screen."
- Interpret its effect. "So a buyer might not see the price before paying."
- Suggest only if asked. "Could the total stick to the bottom?"
Skipping straight to suggestions is the most common mistake. It replaces the designer's thinking with yours and often fixes the wrong problem.
Ask before you tell
Questions beat statements: "What happens if the user has no saved card?" surfaces a missing state without making the designer defensive.
Separate problems from preferences
Say which one you are giving. "This is a preference: I would like more contrast in the header." "This is a problem: the error message is not readable." Problems get fixed; preferences get considered.
Use references to make feedback concrete
"It feels cluttered" is hard to act on. "It feels cluttered; here is a settings page with similar content that feels calmer" is easy. A reference turns a feeling into a target. It also works in the other direction: designers can show references that explain why they made a choice.
This is one of the best uses of a reference library during critique. Search it for the pattern under discussion and put two or three examples on screen. In GetRef a search such as "dense settings page" brings back real examples in seconds, and a shared collection lets the whole team see them afterwards.
Running the session
- Keep it to 30 to 45 minutes with one or two pieces of work.
- One person presents, one person takes notes.
- Feedback is about the work, never the person.
- End with a short list of agreed next steps.
Receiving feedback
Write everything down, ask clarifying questions, and decide later. You do not have to accept every suggestion; you do have to understand it.
For presenting to clients rather than colleagues, see how to present design references to clients.
Common questions
- What is a design critique?
- A structured conversation where a team reviews work in progress against its goals. The aim is to improve the design, not to approve it or judge the designer.
- How do I give feedback on design if I am not a designer?
- Describe your reaction and what you expected, rather than prescribing a fix. "I could not find how to cancel" is more useful than "make the cancel button red."
- How do I make vague feedback more specific?
- Point to an example. "This feels cluttered" becomes useful when paired with a reference that shows the density you mean.
