How do you give design feedback that improves the work instead of bruising it?

Published Read 3 min read

On this page

You give feedback that improves the work instead of bruising it by aiming at the work against its goals, naming the problem instead of prescribing the fix, separating objective issues from personal preference, and keeping everything anchored to what the user needs. Done this way, critique sharpens the design without putting the designer on the defensive, because you are talking about the work and not the person, and about the problem and not your solution to it. The shift is from taste to goals.

The common habit, just say what you would change, fails on two fronts at once. First, prescribing a fix skips the diagnosis, so the designer never learns what was actually wrong and cannot solve it better than you would; you have handed them your answer instead of their problem. Second, a stream of changes reads as personal, because it sounds like a list of ways the designer fell short of your preferences rather than ways the work falls short of its goals. The same observation framed as a problem invites collaboration; framed as a fix, it invites compliance or resentment. Naming the problem keeps the designer in the driver’s seat.

Specificity is what separates useful critique from noise. This feels off helps no one, because it gives the designer nothing to act on and nothing to disagree with, so it lands as a verdict on their ability. Locate the issue against a goal instead: the primary action is hard to find because it competes visually with three secondary buttons, and the goal is to get people to that action quickly. Now there is a real problem on the table, tied to a purpose, and several ways to solve it. The designer can reason about it, push back if you have misread the goal, and own the fix. You have made the work better without grading the maker.

A concrete example shows the two modes side by side. Suppose a signup page has a long form and a quiet submit button. The bruising note is move the button up and make it blue, a prescribed fix delivered as taste, and the designer either obeys or argues color. The useful note is the submit button is easy to miss at the end of a long form, and we need people to actually finish signing up, which names the problem and ties it to the goal. The designer might raise the button, or restyle it, or shorten the form, or add a sticky action bar, all of which solve the stated problem, several of which are better than the original prescription. You got a better outcome precisely because you did not hand over the answer.

The line worth respecting is the one between objective issue and personal preference, because conflating them is what turns review into a contest of tastes. Say which is which out loud. An accessibility failure, a broken hierarchy, a flow that strands the user, these are problems against goals and should be raised as such. A leaning toward a different typeface or a warmer palette, when the current choice meets the goals, is a preference, and it should be offered as one or held back. When you label your preferences as preferences, the designer can weigh them freely, and your genuine problems carry more weight because they are no longer buried among your tastes.

To make this routine, before you speak, run each reaction through a short filter. What goal is this serving, what specifically is going wrong against that goal, and is this an objective problem or my preference? Then voice the problem, tied to the user’s needs, and stop short of prescribing the cure unless asked. Frame feedback around goals and specific problems rather than fixes and taste, and the work gets sharper while the designer stays standing, which is the only kind of critique that survives more than one round.

Related posts:

  1. When is an icon clearer than a word, and when is it the opposite? An icon is clearer than a word when the concept is universally understood and space is tight; a word is clearer when the action is abstract or ambiguous in a......
  2. When should headings get their own typeface vs share the body’s? Default to one family for both, and give headings their own typeface only when the brand genuinely needs a distinct voice at display sizes and you can pair the two......
  3. How do you keep contrast intact across both light and dark mode? You keep contrast intact by verifying it separately in each theme, because a color pairing that passes in light mode can fail in dark and the reverse, so each mode......
  4. What makes a touch target accessible beyond just its visual size? An accessible touch target needs more than a big-enough icon: it needs an adequate hit area, enough spacing from its neighbors, and a clear name and state for assistive technology.......
  5. How few fields can a form have before you’re asking too little to be useful? A form has too few fields the moment it stops capturing what it needs to do its job, which means the real floor is not zero or even one, it......
  6. When does a microinteraction earn its complexity vs add overhead? A microinteraction earns its complexity when it does a real job, confirming an action, communicating a state, or smoothing a transition the user actually benefits from, and it becomes overhead......
  7. Should you build a color system from one hue or several? Start from one hue and expand only when the product proves it needs more. A single-hue system, built from one color stretched across tints, shades, and a neutral ramp, reads......
  8. What breaks when you design only for the two most common screen sizes? What breaks is everything you never checked: the widths in between your two snapshots and the widths beyond them. Designing to the most common phone and the most common desktop......
  9. Gradient or flat fill, when does each fit? Reach for a flat fill when a surface should be clear, calm, and content-forward, and reach for a gradient only when a surface should add depth, energy, or focus, used......
  10. Why do stock photos often make a design feel less trustworthy? Stock photos often make a design feel less trustworthy because generic, obviously staged imagery reads as inauthentic, and a viewer who recognizes it instantly registers it as filler that says......
  11. How many CTAs should one page have before they start competing? The honest number is one primary action, not one button, and CTAs start competing the moment the page offers two different actions of roughly equal weight that pull the visitor's......
  12. How do you make an icon-only button understandable without a visible label? An icon-only button becomes understandable when its meaning travels through several channels at once: a conventional, recognizable glyph for people who scan visually, an accessible name that assistive technology can......
  13. How do you test whether a design is actually accessible vs technically compliant? You test for real accessibility by putting the interface through a keyboard, a screen reader, and ideally people who actually rely on assistive technology, because an automated checker proves only......

Leave a comment

Your email address will not be published. Required fields are marked *