It would be hard to argue that there is no place for subjectivity in design. Unfortunately, this is the very reason that makes giving constructive design feedback a daunting challenge. Add to this the fact that not all of us are designers: sometimes we just feel that something is not right, but we can’t explicitly put it into words. Needless to say, unconstructive criticism is the worst thing that could happen to a designer: not only it demotivates, but it also causes considerable delays due to random blind revisions that end up making things more complicated for both sides.

For better results, here are five things to avoid when criticizing design:

1. Vague statements

Avoid generic sentences that are too vague to communicate anything to the designer. Lines like “It’s looks horrible”, “It’s off the mark” etc won’t cut it. They just end up confusing the designer and delaying the project . Make an effort to pinpoint what bothers you, even when you lack the jargon to clearly express it.

2. Personal tastes

NEVER EVER criticize design based on your personal tastes. Once a work satisfies the basic principles of design and respects the project guidelines, it becomes counter-productive to bring personal tastes and preferences into play.

3. Uninformed criticism

Before voicing your opinion, always ask for the Why. Judging a design work without seeking to know about the designer motives behind it is plain amateurish. Mutual understanding is key.

4. I-can-design-too attitude

Do not underestimate design. I know you can use Photoshop. I know you had already made a website or a logo for your college Art club. But let’s be honest: If you know that much about design, you wouldn’t be seeking the expertise of a designer in the first place. And even if you DO really know about design, do not get too cocky, as this won’t make things any easier.

5. Superfluous comparison

Do not try to constantly compare the work at hand with what you have seen elsewhere. External references should be used moderately, as every project is unique. Also, do not bring the argument of best practices, as there are no best practices anyway.

A problem well defined is a problem -mostly- solved. And when it comes to design, it gets even harder to define the problem. So let’s not make it any harder.