Why the Way You Give Feedback to Your UX Designer Matters More Than You Think
You hired a talented UX designer. The first draft lands in your inbox. You open it, stare at it for a moment, and type: “I don’t really like it. Can you make it pop more?”
Sound familiar? If so, you are not alone. But vague feedback like this is the single biggest reason design projects spiral into endless revision cycles, missed deadlines, and growing frustration on both sides.
The truth is, feedback is not rejection. It is collaboration in disguise. When you learn how to give feedback to your UX designer in a clear, structured, and respectful way, something remarkable happens: revisions get faster, the final product gets better, and nobody ends up dreading the next review round.
This guide is written specifically for clients, startup founders, and project managers who work with freelance or in-house UX designers but do not have a design background themselves. Below you will find eight practical tips, real examples of good vs. bad feedback, and a framework you can start using today.
The Real Cost of Bad Design Feedback
Before diving into the tips, let’s look at what unclear feedback actually costs your project:
- Extra revision rounds: What should take two rounds balloons into five or six.
- Wasted budget: Every unnecessary revision is billable time (yours and your designer’s).
- Delayed launches: Weeks slip by while both sides try to decode what the other meant.
- Damaged relationships: Designers lose motivation; clients lose trust.
The good news? Almost all of this is preventable with a few simple habits.
8 Tips for Giving Better Feedback to Your UX Designer
1. Start With the User’s Needs, Not Your Personal Taste
UX design exists to solve problems for real users. When reviewing a wireframe or prototype, the first question should never be “Do I like it?” Instead, ask yourself:
- Does this help our target user accomplish their goal?
- Is the flow intuitive for someone who has never seen this product before?
- Does it align with the user research or personas we established?
Grounding your feedback in user needs and business objectives immediately makes it more useful than subjective reactions. Your designer can work with “Our users are mostly over 55, so the tap targets may need to be larger” far more easily than “I just feel like the buttons are off.”
2. Be Specific. Then Be More Specific.
Vagueness is the enemy of progress. Compare these two pieces of feedback:
| Vague Feedback | Specific Feedback |
|---|---|
| “The homepage feels boring.” | “The hero section does not communicate our main value proposition. Can we test a version with a stronger headline and a visible CTA above the fold?” |
| “I don’t like this layout.” | “The two-column layout on the pricing page makes it hard to compare plans side by side. A three-column table might work better for our four tiers.” |
| “Make it more modern.” | “I noticed competitors X and Y use more whitespace and larger typography. Could we explore a cleaner look that is closer to that direction?” |
The rule of thumb: If your designer could interpret your comment in three different ways, it is not specific enough.
3. Describe Problems, Don’t Prescribe Solutions
This is one of the most important distinctions in giving design feedback. Your job as a client or PM is to clearly articulate what is not working and why. The designer’s job is to figure out how to fix it.
Instead of saying “Move the navigation to the left sidebar,” try “Users might struggle to find secondary pages because the current nav feels hidden. What options do we have to improve discoverability?”
When you describe the problem and let the designer propose solutions, you get the benefit of their expertise. That is, after all, why you hired them.
4. Separate Your Feedback Into Categories
Not all feedback carries the same weight. Mixing critical issues with minor preferences in a single unstructured email creates confusion. Try organizing your comments into clear tiers:
- Must fix: Anything that breaks the user flow, contradicts brand guidelines, or blocks a business requirement.
- Should improve: Items that are functional but could be better (readability, hierarchy, consistency).
- Nice to have: Minor suggestions, polish items, or personal preferences that are optional.
This prioritization helps your designer focus their time where it matters most and avoids the trap of spending hours tweaking a button color while a critical navigation issue goes unaddressed.
5. Use Visual Annotations When Possible
A screenshot with a circle drawn around the problem area is worth a thousand words. Tools that make this easy include:
- Figma comments (directly on the design file)
- Loom (record a quick screen walkthrough with voiceover)
- Markup Hero or CleanShot (annotate screenshots)
- Google Slides (paste screenshots, add arrows and text boxes)
Visual annotations remove ambiguity because the designer can see exactly which element you are referring to. This alone can cut a full revision cycle from many projects.
6. Consolidate Feedback From All Stakeholders Before Sending
Few things derail a project faster than receiving conflicting feedback from multiple people at different times. The CEO wants it “bold and edgy.” The marketing director wants it “clean and minimal.” The product manager just wants the form fields reordered. The designer is stuck in the middle.
Best practice: Designate one person as the feedback point of contact. Have all stakeholders share their thoughts internally, resolve disagreements, and then deliver one unified set of feedback to the designer.
This single habit can reduce revision rounds by 30 to 50 percent on most projects.
7. Acknowledge What Is Working (Not Just What Isn’t)
Highlighting the effort and acknowledging what works well is not just about being polite. It serves a strategic purpose: it tells the designer what direction to continue in.
If you only point out problems, the designer might scrap elements that were actually on the right track. Instead, try:
- “The onboarding flow feels really intuitive. Let’s keep that structure.”
- “I love the visual hierarchy on the dashboard. The way the key metrics stand out is exactly what our users need.”
- “The use of iconography in the sidebar is great. It keeps things scannable.”
Positive feedback is a compass. It saves time because the designer does not have to guess which parts you approved.
8. Build a Foundation of Trust and Set Expectations Early
The best feedback relationships do not start at the first design review. They start during the project kickoff. Before any design work begins, align on:
- Goals and success metrics: What does this design need to achieve?
- Brand guidelines: Colors, fonts, tone, existing design systems.
- Reference examples: Sites or apps you admire (and why).
- Feedback process: How many rounds are included? What tool will you use? What is the turnaround time for feedback?
- Decision makers: Who has final sign-off authority?
When both sides agree on these elements upfront, every feedback conversation that follows becomes faster, clearer, and less emotionally charged.
A Simple Feedback Framework You Can Copy
If you want a ready-to-use template, here is a simple structure you can paste into an email, a Notion doc, or a project management tool every time you review a design:
| Section | What to Include |
|---|---|
| Overall Impression | One or two sentences on how close this feels to the vision. Set the tone positively. |
| What’s Working | List specific elements you want to keep. Reference screens or sections by name. |
| Must Fix (Priority 1) | Critical issues. Describe the problem, explain why it matters, link to a screenshot if possible. |
| Should Improve (Priority 2) | Important but not blocking. Include context and reference user needs or business goals. |
| Nice to Have (Priority 3) | Minor polish items or personal suggestions. Make it clear these are optional. |
| Questions for the Designer | Anything you are unsure about. Asking “Why did you choose this approach?” often reveals smart reasoning you had not considered. |
Common Feedback Mistakes to Avoid
Even well-intentioned clients fall into these traps. Here is a quick list of what not to do:
- Design by committee: Getting 10 people to weigh in without a single decision maker leads to Frankenstein designs.
- Drip-feeding feedback: Sending one piece of feedback per day across a week instead of consolidating it into one round.
- Skipping the brief, then over-correcting later: If you do not invest time in the kickoff, you will pay for it in revisions.
- Saying “I’ll know it when I see it”: This forces your designer into a guessing game. Provide references, examples, and criteria instead.
- Critiquing the designer, not the design: Keep feedback focused on the work. “This layout is confusing” is productive. “You clearly did not understand what I wanted” is not.
How This Applies When Working With a Freelance UX Designer
If you are working with a freelance UX designer (as many of our clients at Aaron Mallen do), the stakes for clean feedback are even higher. Freelancers typically scope projects with a set number of revision rounds. Every round of unclear feedback that leads to a misfire eats into that budget.
Here are a few extra tips for the freelance context:
- Respect the agreed revision rounds. If the contract includes two rounds of revisions, make each one count by consolidating all feedback.
- Provide all assets and content early. Missing copy, logos, or brand assets mid-project is a hidden cause of unnecessary revisions.
- Use asynchronous tools. Freelancers may work across time zones. Tools like Figma comments and Loom videos keep the project moving without needing everyone online at the same time.
- Trust their expertise. You hired a specialist. If they push back on a suggestion, listen to their reasoning before insisting.
Frequently Asked Questions
What are the 3 C’s of feedback?
The 3 C’s of feedback are Clear, Constructive, and Collaborative. Clear means being specific about what you are referring to. Constructive means focusing on improvement rather than criticism. Collaborative means treating the feedback process as a two-way conversation where both sides contribute to the best outcome.
How do I give feedback on a design if I am not a designer?
You do not need to be a designer to give great feedback. Focus on the user experience rather than aesthetics. Describe what feels confusing, what information seems hard to find, or where the flow breaks down. Provide context about your users and business goals, and let the designer handle the visual and interaction solutions.
How many revision rounds should I expect with a UX designer?
Most freelance UX designers include two to three revision rounds in their project scope. If you follow the tips in this guide (especially consolidating feedback and being specific), two rounds are usually enough to reach a polished final design.
What tools are best for giving feedback on UX designs?
The most popular tools in 2026 include Figma (for inline comments directly on design files), Loom (for screen-recorded walkthroughs), and annotation tools like Markup Hero or CleanShot. For teams that prefer structured feedback, a shared document or project management tool like Notion or Asana works well.
How do I compliment a UX designer’s work?
Be specific about what you appreciate. Instead of “Looks great,” say something like “The checkout flow is really streamlined. I love how the progress indicator keeps users oriented.” Specific compliments tell the designer what to continue doing, which is just as valuable as pointing out what needs to change.
What should I include in a design brief to minimize revisions later?
A strong brief includes your project goals, target audience profiles, brand guidelines, competitor examples, content or copy, technical constraints, and a clear list of pages or screens needed. The more complete your brief, the closer the first draft will be to your expectations.
Final Thoughts
Learning how to give feedback to your UX designer is one of the highest-leverage skills you can develop as a client or project manager. It does not require design knowledge. It requires clarity, empathy, and a willingness to treat the review process as a collaboration rather than a correction.
Start with the user’s needs. Be specific. Describe problems instead of dictating solutions. Consolidate your team’s input. And always acknowledge what is working alongside what needs to change.
Do these things consistently and you will not just get faster revisions. You will get better designs, stronger working relationships, and products that genuinely serve your users.
Need help with your next UX project? Get in touch with us at Aaron Mallen and let’s build something great together.