Giving design critique that is kind and useful

Design critique has a reputation problem. Some people picture a studio review where work is taken apart in front of a room. Others picture a comment thread full of fire emoji and “love this!”, pleasant and useless in equal measure. Good critique sits between the two. It is honest enough to help and warm enough to be heard.

Kindness and usefulness are not opposites. In practice they come from the same place: paying close attention to someone else’s work and telling them what you saw, in a form they can act on. Here is how we try to do that on RyeType.

Read the brief before you look at the pixels

The single most useful thing you can do before commenting is to read what the designer wrote. What is the project? Who is it for? What stage is it at? What did they ask?

A comment that answers the question the designer asked is worth five that answer questions they did not. If someone posts an early wayfinding sketch and asks whether the floor numbers or room names should lead, a note about the corner radius on the signs is beside the point, even if it is correct.

If there is no brief or question, it is fine to ask: “What kind of feedback would help most at this stage?” That one line often turns a vague post into a focused conversation. Our note on sharing work in progress encourages designers to frame their posts this way, so you will increasingly find the question already there.

Describe what you see before you judge it

Start with observation, not opinion. Describe what the design does to you as a viewer: where your eye went first, what you understood, where you hesitated.

• “My eye went to the photo first, then the price, and only then to the button.”
• “I read the second heading as a link; I tried to tap it.”
• “It took me a moment to see that the two columns were separate options.”

Observations like these are hard to argue with, because they are simply reports of your experience. They are also more useful than verdicts. “The hierarchy is weak” leaves the designer guessing. “My eye went to the photo before the button” tells them exactly what happened and lets them decide whether that was the intent.

Tie every point to the goal

Once you have described what you saw, connect it to what the design is trying to do. This is the difference between taste and critique.

“I don’t like the green” is taste. It tells the designer about you. “The green is close to the colour of the success messages, so the warning banner might read as good news” is critique. It tells the designer about their design, and about a risk to the goal.

A helpful sentence shape is: because the aim is X, Y might get in the way. If you cannot finish that sentence, consider whether the point is really about the work, or about your preferences. Preferences can still be shared, but label them as such: “Purely a matter of taste, but I would try a warmer grey here.”

Be specific enough to act on

Vague critique is unkind in a quiet way, because it leaves the designer worried without telling them what to change. Compare:

The typography feels off.

The body text and the captions are very close in size, so the captions don’t read as secondary. Making the captions noticeably smaller, or a lighter colour, might separate them.

The second comment points to a place, names the issue, and offers one possible direction without insisting on it. That is the pattern to aim for: where, what, and one idea. Keep the idea light. The designer knows constraints you do not, and your suggestion is a prompt, not a prescription.

If you are commenting on type in particular, it helps to use plain words alongside any technical terms, as we suggest in explaining a typeface choice. Not every designer has the same vocabulary, and a term that is obvious to you may not be obvious to someone working in a different discipline.

Say what works, and mean it

Positive feedback is not a cushion for the real criticism. It is real information. Designers need to know what is working so they do not accidentally remove it in the next round.

Make praise as specific as criticism. “Great work!” is friendly but tells the designer nothing. “The way the illustration style matches the icon set makes the whole thing feel like one family” tells them something to keep.

Avoid the sandwich, where one compliment is placed on each side of a criticism as padding. People learn to see it coming and stop trusting the compliments. It is better to say what works because it works, and what does not because it does not, in whatever order makes sense.

Mind the tone, especially in writing

Critique in a comment box loses the voice, face and timing that soften it in person. A few habits help written critique land as intended:

• Talk about the work, not the person. “This layout” rather than “you”.
• Use questions where you are genuinely unsure. “Was the low contrast on the labels deliberate?” leaves room for a reason you do not know.
• Keep it proportionate. Three clear points are more useful than fifteen scattered ones. Choose the ones that matter most.
• Read it back once. Imagine receiving it about your own work on a tired day. Adjust anything that would sting without helping.

Our guidelines ask that comments stay on-topic and civil, and that is a floor, not a ceiling. You can be completely civil and still unhelpful, or blunt and genuinely useful. The aim is the overlap: honest about the work, generous to the person.

A last thought. The best critique often ends with an open door rather than a conclusion: “Happy to look again when the next version is up.” That small line says you care how the work turns out, and in a community of designers who write, that is most of what kindness is.