Guide5 min readUpdated
How to Give Design Feedback That Gets Better Results
How to give design feedback to a freelance designer: describe problems, batch comments, use one decision-maker and make revision rounds count.
By Tithi Mondal, UI/UX Designer
Most design projects do not go wrong because of bad design. They go wrong because feedback is vague, scattered or contradictory. If you know how to give design feedback, you get better work, faster, and you use your revision rounds well. This guide is for clients: founders, business owners and managers working with a freelance designer for the first time.
Why feedback matters more than you think
A designer works from a brief, but the brief cannot cover every detail. Feedback is where the real preferences appear. Good feedback steers the design. Poor feedback makes the designer guess, and guessing costs time on both sides.
Many freelance designers include a fixed number of revision rounds. My own terms include two to three rounds. A round is one full set of changes based on one set of comments. That makes the quality of each round important, so it is worth preparing for.
Describe the problem, not the solution
This is the single most useful habit. You know your customers and your business. The designer knows how to solve a visual or flow problem. When you give a solution ("make the logo bigger"), you may fix the wrong thing. When you give the problem ("the logo is hard to notice on the first screen"), the designer can pick the best fix, which might be size, contrast or position.
| Solution-style comment | Problem-style comment |
|---|---|
| Make the button red | I do not notice the Pay button quickly enough |
| Change the font | The text feels too formal for our young customers |
| Add more space here | This section feels crowded on my phone |
| Move the menu to the bottom | My customers use the app with one hand and struggle to reach the menu |
| Use a different photo | This photo does not look like our real shop |
Both can be useful. But start with the problem. Add your idea afterwards as a suggestion: "I wonder if a stronger colour would help, but you may have a better idea."
Say who and why
Every comment gets stronger with a reason. "I do not like it" gives the designer nothing. "I think our customers in smaller towns will not understand this icon" gives a direction.
Connect your comments back to the brief: the audience, the goal and the main action. If you have not written one yet, my guide on how to write a design brief helps. It also makes feedback easier, because everyone is judging the work against the same goals.
Batch your feedback
Do not send comments one by one over WhatsApp as they occur to you. Fragmented feedback leads to contradictions, lost points and wasted rounds.
- Look at the whole design first, then write.
- Collect comments from everyone on your side.
- Remove duplicates and resolve disagreements internally.
- Group the comments by screen or section.
- Mark what is must-fix and what is nice-to-have.
- Send one clear list.
A short numbered list with the screen name beside each item is ideal. If your tool allows comments on the design file itself, use them for precise points and keep a short summary message for the big picture.
Appoint one decision-maker
When three people each send separate changes, the designer receives opposing instructions. One wants a bolder look, another wants it quieter. No round of revisions can satisfy both.
Choose one person who owns the final call. Others can give input, but only that person sends the consolidated feedback to the designer. This is the single biggest way to keep a project on schedule. App and website projects usually take two to four weeks, and delays often come from late or conflicting feedback rather than the design work itself.
Make your revision rounds count
Think of rounds as a budget. Here is how I suggest using them on a typical app or website project.
- Round one: direction and structure. Is the flow right? Is the layout clear? Big changes belong here.
- Round two: visual detail. Colours, type, spacing, imagery.
- Round three, if included: polish and small fixes.
Avoid reopening decisions you approved earlier. If the wireframes were signed off, changing the whole structure at the visual stage is a new piece of work. That is why I treat wireframes as a checkpoint, as I explain in the mobile app design process.
It also helps to know what counts as a revision and what is new scope. Ask this at the start. Terms differ between designers, so check what is included before you begin. For a wider view of working terms, see how to hire a freelance UI/UX designer in India.
Be honest, kind and specific
Tone matters. A designer who feels respected will fight harder for your project.
- Start with what works. It tells the designer what to keep.
- Be direct about what does not work. Politeness is not the same as vagueness.
- Avoid words like "nice", "modern" or "clean" without detail. Everyone hears different things.
- Use examples if they help, such as screenshots of apps you like, and say what exactly you like about them.
- Do not compare with a competitor's app and ask for a copy. Point to the quality you want instead.
- Say when you are unsure. "I cannot tell why this feels off" is useful. The designer can help you find it.
Test, do not only opine
Your own taste is one data point. Before sending feedback, show the design to two or three people from your real audience and watch them. Ask them to find a button or finish a task. If they hesitate, that goes into the feedback list. It is more convincing than any opinion, including mine.
A simple feedback template
Copy this structure for each round:
- What is working well.
- The three most important problems, in order, each with the reason.
- Smaller points, grouped by screen.
- Questions for the designer.
- Who approved this list, and the date you need the next version.
Clear feedback is a small effort that pays back in every project. If you would like to work together, see my UI/UX design service or get in touch.
Frequently asked questions
How many revision rounds should a freelance designer include?
It varies by designer. My own terms include two to three rounds. Ask before you start, and ask what counts as a revision and what counts as new work.
Should I send feedback in a call or in writing?
Both help. A call is good for the big picture, and a written list afterwards avoids misunderstanding. I take meetings over Google Meet, WhatsApp or phone, and a short written summary keeps everyone aligned.
What if my team disagrees about the design?
Settle it on your side before sending feedback. Name one decision-maker who sends one consolidated list to the designer.
Is it okay to say I do not like a design?
Yes, as long as you say why. Explain what feels wrong for your audience or goal, and the designer can find the right fix.