Some of it is genuinely useful. Some of it is personal taste. And some of it is a real problem hiding inside vague words. Working with feedback is one of the most underrated design skills. It decides whether a project moves forward or circles forever.
At OSAM we review work with clients every week, so we’ve had plenty of practice. Here’s how to tell real critique from opinion, and what to do with each.
Critique or opinion? The quick test
Constructive critique is tied to a goal. Subjective opinion is tied to a feeling. That’s the whole difference. Constructive critique usually:
- points to a specific element ("the price is hard to find on the product page")
- connects to users or business ("older customers might not see the light grey text")
- can be checked or tested
- leaves room for the designer to propose the solution
Subjective opinion usually:
- is about personal taste ("I just don’t like green")
- is vague ("it feels off", "make it more premium")
- prescribes a solution without a reason ("make the logo bigger")
- comes from someone who isn’t the target user
One important nuance: opinion isn’t worthless. "It feels off" often means something real is wrong, the client just can’t name it. Your job isn’t to dismiss vague feedback. It’s to dig until you find the actual problem underneath.
Translating vague feedback
When feedback is fuzzy, don’t guess and don’t argue. Ask questions that turn feelings into problems you can solve.
- "Make it pop." Ask: "What should people notice first on this screen?" Often the real issue is that the main action doesn’t stand out.
- "It’s not premium enough." Ask: "Which brands feel premium to you, and what do you like about them?" References turn an adjective into a direction.
- "I don’t like it." Ask: "Which part? What did you expect to see instead?" Narrow it down to an element.
- "Make the logo bigger." Ask: "What are you worried about?" Usually the fear is that people won’t remember the brand, and there are better ways to solve that than a giant logo.
- "Can we try red?" Ask: "What do you want red to communicate here?" Maybe it’s energy, maybe urgency, and the answer guides the solution.
A powerful habit: repeat the feedback back in your own words. "So the concern is that first-time users won’t see the sign-up button, right?" If they agree, you’ve just turned an opinion into a clear task.
When the client is right, even if it’s taste
It’s tempting to treat every subjective comment as an obstacle. But the client knows things you don’t: their customers, their market, their history, the competitor they’re secretly afraid of. Sometimes taste-based feedback is worth following:
- It’s their brand. If a color clashes with how the company sees itself, that matters, even without data.
- It doesn’t hurt users. If the change is neutral for usability, picking your battles is a professional skill, not a defeat.
- They know the audience. "Our customers are conservative accountants" is taste-sounding feedback that’s actually market insight.
And sometimes you need to push back:
- when the change breaks usability or accessibility
- when it contradicts the goals you agreed on together
- when it would hurt the business result the client is paying for
When you push back, argue with goals, not with taste. "I’d keep the button high-contrast because it’s the main conversion action" works. "I just think it looks better" puts your opinion against theirs, and theirs usually wins. If you can’t agree, offer to test both options.
Prevent the chaos before it starts
The best way to handle bad feedback is to set things up so less of it happens.
- Agree on goals first. Before designing anything, write down who the product is for and what it needs to achieve. Later, every piece of feedback can be checked against that list.
- Collect references early. Ask what the client likes and dislikes before you start. It’s far cheaper to learn they hate gradients in week one than in week four.
- Offer directions, not one design. In our process, clients see two design concepts and pick the direction that fits their goals. Choosing between options focuses feedback far better than reacting to a single take.
- Show work often. We share progress with clients every week. Small, frequent check-ins catch misunderstandings while they’re still cheap to fix.
- Ask for feedback in one place. Comments in Figma or a single document, not scattered across chat, email and voice messages.
- Agree on who decides. Five stakeholders with five opinions can stall a project. Ask early who has the final word.
- Define revision rounds. A clear number of rounds keeps feedback focused and prevents endless "one more small change."
Don’t take it personally
The hardest part of feedback isn’t the client. It’s the voice in your head saying "they hate my work, so they hate me." A few things that help:
- The design is not you. Feedback is about a file, not about your worth as a designer.
- Pause before you reply. Read the comments, close the laptop, come back later. First reactions are rarely the most professional ones.
- Thank people for specifics. Even harsh feedback with clear details is a gift. It tells you exactly what to fix.
- Look for the pattern. One person disliking something is an opinion. Three people stumbling at the same spot is a problem.
- Keep a win file. Save the messages where clients loved your work. On rough days, it reminds you that one tough review doesn’t define you.
The designers who grow fastest aren’t the ones who get the least criticism. They’re the ones who use it best.