Design Feedback That Doesn’t Suck
A collection of beautiful mesh gradients made with pure CSS. Click on any gradient to copy its CSS.
Design feedback can be one of the most powerful tools on a product team—when it’s done right. Great feedback sharpens ideas, reveals blind spots, and pushes work to the next level. But bad feedback? It slows things down, kills momentum, and often leaves designers confused or defensive.
“The goal of feedback isn’t to fix the design—it’s to improve the thinking behind it.”
Start with Context
Before giving any feedback, ask yourself: What is this design trying to achieve? What’s the user’s goal? What problem is this screen or flow solving?
Without that clarity, you’re just reacting to visuals—and that rarely leads to meaningful improvements.
Be Specific, Not Vague
General comments like “It feels off” or “I don’t love this” don’t help. Instead, focus on what’s not working and why.
For example:
“The CTA blends into the background—I didn’t notice it right away. Try increasing the contrast or changing placement.”
Concrete observations lead to actionable changes.
Focus on the Work, Not the Person
Feedback should never feel like a personal attack. It’s not about ego—it’s about outcomes.
Use neutral, collaborative language. Say things like:
“What if we tried…” or “This might work better if…” instead of “You did this wrong.”
Make it a conversation, not a critique session.
Receiving Feedback? Stay Open
If you're on the receiving end, don’t rush to defend every detail. Listen fully, clarify when needed, and then step back to evaluate. Some feedback will help. Some won’t.
It’s okay to ignore what doesn’t align with the vision—as long as you’ve considered it thoughtfully.
Make It a Habit, Not an Afterthought
Design feedback isn’t a box to check at the end of a sprint. It should be a regular, collaborative part of the process. The earlier and more often it happens, the better the work becomes.
TL;DR
Set context before giving feedback
Be specific and actionable
Focus on the design, not the designer
Stay open to input, but filter it
Make feedback part of the workflow
Design is collaboration. Make it count.