The art of design feedback: how to say it so your teammates want to listen

Remote work and why quality feedback matters

On many of my projects as a Product Designer, my team and I have worked remotely from day one. We are spread across locations and time zones, yet we stay effective thanks to a disciplined approach to communication and feedback.

Over time, we have come to realize that feedback given the right way not only raises the quality of the product but also helps each team member grow their own skills. Handled badly, though, a design review can turn into a nightmare that drains the team's motivation and even sparks conflict - "the work itself isn't exhausting, but the psychological pressure of working together is..."

According to research from Harvard Business Review:

• Negative feedback often backfires, leaving employees less confident and inclined to avoid the person who gave it.
• Employees tend to seek out positive feedback from others to balance their emotions and feel better about themselves.

Negative feedback triggers the brain's fight-or-flight response, reducing creativity and problem-solving ability by 27%.

I have always believed that a design review and feedback session should be a place that inspires, not one that intimidates. If your team doesn't feel energized when receiving feedback, it is time for a change!

5 tactics for giving effective feedback in UX/UI design

1. Focus on one point at a time

Before: "This button is wrong, the spacing is off, the color doesn't fit the brand, the user flow is broken, do you even understand the business logic and what the stakeholders asked for? ..."

More effective: "Let's focus first on the purpose of this product or feature, then on the user flow. I see a few steps in the payment confirmation flow that could be optimized. Can we talk through that first?"

The human brain can only process one problem effectively at a time. Focusing on a single aspect keeps the designer from being overwhelmed and lets them improve each point thoroughly.

Imagine weekly meetings where the air is filled with nothing but criticism and unconstructive comments from stakeholders and managers. Not only do you feel hurt, you may also fail to retain much of the feedback that was actually valuable. For these reasons, instead of listing a long string of problems, focus on just one aspect and discuss it in depth. This gives you or the designer the chance to explain the design fully, gives everyone the chance to listen and reflect, and produces more valuable feedback.

2. Target the design, not the designer

When giving feedback to a designer, talk about their work, not their character. Otherwise, they may feel you are attacking them personally. For example:

❌ "Do you not know how to handle spacing or what?!"

✅ "I think the spacing here could be improved to help readability and information hierarchy. What do you think?" Attacking the person not only triggers a defensive reaction, it can also do irreparable damage to your working relationship. Feedback should be aimed at the product, not the individual.

Separating the product from the person who made it keeps the discussion more objective, avoids defensiveness and keeps the focus on solutions.

3. Give specific examples

Lexi Croswell stresses the importance of giving your teammates specific feedback. That feedback can be praise or redirection, and it helps teammates learn and improve. When you pair feedback with a concrete solution, you are not just pointing out a problem, you are building a path toward improvement. To do this, ask yourself the following questions:

• What behavior do I appreciate? This helps you identify the positive behaviors your teammate is showing that deserve praise.
• What behavior do I want to see more of? Identify the behaviors you would like your teammate to practice more often to improve performance.
• Why? Be clear about why you want to see more of those behaviors. This helps you give feedback that is meaningful and tied to the organization's goals.

4. Choose the right moment

According to HR expert Susan M. Heathfield, feedback should be given right after the event so that employees can easily connect it to what they did. Whether it is praise or a critique, give the feedback as soon as possible after the fact. That way, people can readily understand what they did well or not so well, and why.

5. Keep feedback regular

Retaining and engaging team members should start with sincere feedback. Instead of commenting only when there is a problem, make feedback a regular habit (weekly or every sprint). According to Google's Project Aristotle, "psychological safety" is the single most important factor in team performance. You can discuss ways of working in recurring meetings, and give specific comments on designs right in the flow of work. Feedback that flows in every direction creates a culture of openness and continuous learning.

This approach helps the team keep improving quality, and it lets each member feel that their value is recognized. A team with clear direction will stay and grow with the company for the long term.

One feedback technique to avoid

"Sandwich feedback" - praise, criticism, praise

This method was once popular but is now outdated. Employees often skip over the praise and focus only on the negative part.

Claire Lew (CEO of Know Your Team) puts it this way:

Many people use praise as a sugar coating over criticism to make themselves more comfortable. But this strips the feedback of its sincerity.

Instead, be honest but respectful.

Communicating effectively when working remotely

1. Avoid dull text

Words carry only 7% of a message. The other 93% comes through nonverbal cues such as gestures and body language (55%) and tone of voice (38%). When working remotely, emoji, GIFs and video convey emotion much better.

2. Direct but tactful

• Be straightforward about the problem, but propose a solution.
• Example: "This color is hard to read on screen. Shall we try #4D4D4D?"

3. Clear and with full context

Don't assume everyone understands what you mean. Explain in detail to avoid misunderstandings.

4. Mind cultural differences

The same sentence can mean different things in different cultures. Read "The Culture Map" (Erin Meyer) to understand this in more depth.

1. Create a "feedback style guide"

Put together a short document on how your team gives feedback, including:

• Preferred language
• Tools for feedback
• The process from receiving feedback to implementing it

Conclusion

Feedback in UX/UI and Product Design not only helps improve the product but also builds a positive team culture. Apply the 5 tactics above to turn every review into a chance to learn, not something to dread.

The harshest feedback is sometimes the most valuable feedback. - Shawn Lan, Design Lead at Zoom

Are you ready to change the way you give feedback?