Design FeedbackCollaborationDesign process

Giving effective design feedback

Vague feedback slows projects down. Clear feedback makes designs better, faster.

UUIUX Studio Editorial Team 5 min read
Design
Giving effective design feedback
How designers and clients can give feedback that moves work forward
The problem
“Make it pop”
Vague comments leave designers guessing and add rounds of changes.
VAGUE✕Make it pop✕I don’t like it✕Try something else
USEFUL✓Price is hard to find✓CTA blends with the background✓Checkout step 2 confuses users
The method
Goal, problem, specifics
Comments tied to goals help designers solve the right problem.
review-comments
// goal: more trial sign-ups
hero: value unclear in 5 seconds
cta: low contrast on mobile
pricing: plans hard to compare
3 clear actions
THE SHORT ANSWER

Effective design feedback ties every comment to the project goals, describes the problem rather than prescribing a fix, is specific about what and where, balances what works with what does not, and is given at the right stage. Structured critiques with clear roles make feedback faster and less personal.

KEY TAKEAWAYS
  • ✓Tie feedback to goals and users
  • ✓Describe the problem, not the solution
  • ✓Be specific: what, where and why
  • ✓Match feedback to the stage of work
  • ✓Use structured critique sessions

Why feedback makes or breaks design projects

Design is a collaborative process. Even the most experienced designer relies on input from clients, product owners, developers, researchers and users to shape the work. The quality of that input has a huge effect on the outcome. Clear, specific feedback tied to goals helps designers make better decisions quickly. Vague or contradictory feedback leads to endless revisions, frustrated teams and designs that try to please everyone but solve nobody’s problem.

Many project delays blamed on design are really feedback problems: comments arriving late, coming from too many people at once, focusing on personal taste rather than user needs, or prescribing solutions instead of describing problems. Improving how feedback is given and received is one of the cheapest ways to speed up projects and raise quality at the same time.

Principles of good feedback

G
Goal-based
Link comments to user and business goals.
P
Problem, not solution
Say what is not working and let the designer solve it.
S
Specific
Point to the exact screen, element and reason.
B
Balanced
Note what works so it is not lost in revisions.

Turning vague comments into useful feedback

Most unhelpful feedback can be made useful by adding three things: which element it refers to, what the problem is, and why it matters to users or the business. The table below shows how common comments can be reworded.

Vague comment
Useful version
Make it pop
The main call to action does not stand out from the secondary links, so users may miss it
I don’t like the colours
The grey text on the light background is hard to read, especially on mobile
It feels cluttered
There are six competing elements above the fold; users may not know where to start
Can we try something different?
The current layout does not show pricing early enough, which our sales team says is the top question

How designers can receive feedback well

Receiving feedback is a skill too. Designers get the most out of reviews when they set context first, explaining the goal of the work and what kind of feedback they need at this stage. During the discussion, they listen for the underlying problem behind each comment, ask clarifying questions rather than defending the design immediately, and separate the comment from the person giving it.

  • State the goal and stage of the work before showing it
  • Ask for specific types of feedback, such as flow or content
  • Ask "what problem are you seeing?" when a solution is suggested
  • Write down every comment and confirm actions at the end
  • Follow up with what changed and why
Omantel case study
Case study · Omantel Service reporting unified in Power BI Incident, SLA and workload reporting brought into one Power BI suite for Oman’s first telecom operator.
1Reporting suite
3Report areas
View case study →

Feedback by stage

Stage
Focus on
Avoid
Concepts
Direction and fit with goals
Pixel details
Wireframes
Flow, structure, content
Colours and imagery
Visual design
Hierarchy, brand, clarity
Reopening the structure
Final polish
Details, consistency, accessibility
New features

Running a design critique

  1. 1
    Set context
    The designer states the goal and what feedback they need.
  2. 2
    Review quietly
    Everyone looks before talking.
  3. 3
    Discuss by goal
    Comments framed around the agreed goals.
  4. 4
    Agree actions
    Summarise changes and owners.

Good feedback is part of a healthy creative process and a strong client-studio partnership.

Giving feedback asynchronously

Many teams now review designs through comments in design tools rather than in meetings. This is efficient, but written feedback loses tone and context. Keep comments focused on one point each, attach them to the exact element, and use a short structure: what you see, why it matters and a question or suggestion. Consolidate feedback from several reviewers before sending it to the designer, so they are not left resolving contradictions.

O
One point per comment
Easier to track and resolve.
P
Pin to the element
Avoid ambiguity about what is meant.
U
Use a simple format
Observation, impact, question.
S
Set a deadline
Collect all comments by an agreed time.

Feedback between clients and studios

When working with an external studio, agree up front how feedback will work: who gives it, how many review rounds are included, how decisions are made when stakeholders disagree and how quickly comments will be returned. Clear rules protect both sides from scope creep and missed deadlines. Our guide to finding the right creative partner covers what to discuss before a project starts.

Feedback from users matters most

Internal feedback is valuable, but the most important feedback comes from the people who will use the product. Testing designs with real users regularly settles many internal debates, because the evidence shows what works rather than what anyone prefers. When stakeholders disagree, proposing a quick test is often the fastest way forward. Our post on sharing research insights covers how to present user evidence so it informs decisions.

Frequently asked questions

Describe what is not working and why, relative to the goals, and point to specific elements. Let the designer propose the solution.

Keep it small and consolidate comments, with one decision-maker to resolve conflicts.

Ask clarifying questions, separate the comment from the person, and confirm agreed actions at the end.

Bring both back to the agreed goals and user evidence. If the conflict remains, the named decision-maker decides, or the team runs a quick user test.

Agree a timeframe at the start, often two to three working days, so designers can plan and projects stay on schedule.

Not when the feedback is about the work and its goals. Clear, respectful critique helps designers do their best work.

U
Written by UIUX Studio Editorial Team
Design & engineering leads, Dubai · India · Australia

For Ambitious Founders

Startup Strategy Session Discuss Your Project with Our Senior Experts

  • No Obligation
  • Expert Insights
  • Tailored Guidance