Design feedback is broken in most settings. Posting work to social media and hoping for useful critique rarely works. Getting "looks great!" from stakeholders doesn't help. And receiving harsh criticism without context or specificity can be worse than getting no feedback at all.
The problem isn't that people are bad at giving feedback. It's that the feedback loop — how we ask, what we provide, and what we expect in return — is usually poorly structured. Fixing the structure fixes most of the problem.
Why most feedback fails
Three things typically go wrong:
- No context — the reviewer doesn't know what problem the design is solving, who it's for, or what constraints exist. Without that, feedback is just personal preference.
- No specificity — "I don't like it" or "something feels off" doesn't give the designer anything actionable. Even positive feedback like "this is great" provides no signal about what's working.
- No relationship — the best feedback comes from people who understand your skill level, your goals, and your project context. Anonymous internet feedback can't provide that.
How to ask for feedback
The quality of feedback you receive is mostly determined by how you ask for it. A good feedback request has three parts:
1. Context — What are you designing? Who is it for? What problem does it solve? What constraints are you working within?
2. Specificity — What part of the design are you asking about? "Can you look at this?" is not a request. "I'm unsure about the visual hierarchy in the card layout — does the title feel prominent enough relative to the metadata?" is a request.
3. What stage you're at — Early exploration, near-final polish, or somewhere in between? This tells the reviewer what level of feedback is useful. Detailed kerning notes on a wireframe are a waste of everyone's time.
A well-structured request looks like:
"This is a pricing page for a SaaS product. The goal is to make the recommended plan visually obvious without making the other plans feel hidden. I'm unsure whether the card elevation difference is enough to create the distinction, or if I need a color treatment too. We're close to final — looking for refinement feedback, not new directions."
How to give feedback
Useful design feedback is objective, specific, and structured around what the work is trying to achieve — not whether you personally like it.
Three lenses to evaluate through:
1. Intuitive reaction — How does it feel when you first see it? Where does your eye go? Is there anything that stops the flow or creates confusion? This is the closest thing to a user's experience.
2. Solution fit — Does the design solve the stated problem? If the goal was to make a pricing plan comparison easy, does it do that? Evaluate against the objective, not against your aesthetic preference.
3. Craft quality — Are there elements that need polish? Alignment issues, inconsistent spacing, type hierarchy that doesn't read clearly? Be specific: "the spacing between the section title and the first card is larger than between subsequent cards" is actionable. "The spacing feels off" is not.
Frame feedback as observations and questions, not directives. "The secondary text competes with the heading for attention — have you tried reducing its weight or size?" gives the designer a problem to solve and a starting point. "Make the subtext smaller" takes away their agency.
Reciprocity
Quality feedback is reciprocal. If you consistently ask for feedback but never give it, you're extracting value from the relationship without returning it. If you want people to invest time and thought in reviewing your work, invest the same in theirs.
The best feedback relationships are ongoing. When someone knows your work over time, they can track your growth, understand your patterns, and give increasingly targeted advice. A single drive-by critique from a stranger can't do that.
Where to get feedback
Ranked by effectiveness:
- A trusted peer or mentor — someone who knows your skill level, your goals, and the context of your work. This is the gold standard.
- A structured feedback group — a small group (3–5 people) who review each other's work regularly. The ongoing relationship builds the context that makes feedback useful.
- Design communities with critique norms — communities that have established feedback formats and moderation. The structure compensates for the lack of personal relationship.
- Public portfolio sites — Dribbble, Behance, etc. Can surface interesting reactions but the feedback is typically shallow. Useful for gauging first impressions, not for substantive critique.
The common thread: feedback quality correlates with relationship depth and structural clarity. Improve either one and the feedback improves.