Design criticism: experiences, insights and tips
In the process of working on a project, most of the solutions the designer proposes lend themselves to analysis and criticism. The latter is an integral part of the process of creating good design. But only on one condition: criticism must be constructive.
The purpose of the critique is to improve the design, not just to evaluate it.
The other day I came across an article about design critique, in particular why it is useful to get feedback from the team and why it is important to learn how to present design competently to the client and colleagues. I decided to share our team’s experiences and insights.
Design critique team
For myself, I distinguish types of criticism: criticism of the design team and criticism (feedback) from the client.
A design critique by the team usually has one goal: to find a better solution.
We have two rallies every week, where everyone presents the results of the week’s work and talks about the planned tasks. At the rally, the team can discuss the design, critique it, and look for a better solution together.
Since each team member knows what his or her colleague is doing and what challenges he or she is facing, that is, everyone is involved in the process of creating the product, criticism is not destructive or hurtful. On the contrary, it benefits the project.
I like collective discussions of UX design and two approaches to its criticism are close:
- Circle, where each team member takes turns sharing comments and offering ideas to improve the design. Yes, yes, we have a rule in our team: if you criticize, offer a solution. It’s a perfect way to make criticism more meaningful, because it invests the time you spend looking for an alternative solution.
- According to quotas, when each panelist has to name a certain number of positive and negative comments. For example, you could name one aspect of the UX design that accurately meets users’ needs, and another that the designer should improve. I’ve noticed that this method works great at the beginning of a discussion. And once we’ve exchanged views, we stop at the most problematic part of the design and discuss what to change about it and how to improve it.
I should add that I myself don’t take criticism of the team lightly, because I understand that in this way:
- each of us learns how to sell our idea and present our design,
- the product as a whole becomes better,
- We grow together as a team: professionalism increases, trusting relationships arise, work becomes as coherent as clockwork.
But, of course, you have to remain tactful, be able to criticize and turn criticisms into objectives and immediate goals.
Client criticism
When a UX designer works directly with the client, difficulties arise more often.
And here you need to be very flexible and stress-resistant, learn to defend the idea and present the design.
You should also take into account the client’s experience with similar projects. It is desirable, before presenting the design for criticism to a new client, to answer questions for yourself:
- Does the client have any experience in launching similar projects?
- What is his or her level of observation?
- is he confident in your expertise or does he always question every step?
If the client has little experience, set the rules and expectations in advance to make sure he understands what the purpose of criticism at a particular stage of the project work, in what format you expect feedback.
Be prepared to provide several design options for analysis, because discussing one solution can put a fat cross on it, and the collaboration can be the final point.
What is the right way to critique a design?
If I need to critique a colleague’s UX design, I stick to the simple tips below.
- Ask questions
By getting more information, you will understand the reasons for the UX design, what goals the designer had.
Examples of questions:
- Why did you choose this approach to implement this element?
- why did you add this design element?
- how will this element help the user solve the problem faster?
2. Hold back your first reaction
Before you say, “I don’t understand,” or “What is this?” take a pause. Let the designer explain the idea or solution. Only then give feedback.
3. Don’t criticize based on assumptions
If you don’t fully understand the designer’s idea, ask questions until the situation becomes clearer.
4. If you’re not asked for advice, don’t give it.
If the designer hasn’t asked for feedback, hold your opinion until the design presentation and team discussion.
5. Look for design weaknesses as well as strengths
Try using a sandwiching technique to balance positive and negative feedback.
6. Think in terms of perspective
When critiquing a design, remember that you are NOT the target audience. Ask questions by putting yourself in users’ shoes and drawing on focus group testing.
How often do you have to criticize a team’s design or decisions? Do you also think that constructive criticism is a great way to improve a project and grow professionally?
Share your opinion.
You can follow me here
