Design critique is a valuable skill for UX designers, as it helps them improve their work, learn from others, and collaborate effectively. However, giving and receiving feedback can also be challenging, especially if it is not done well. In this article, we will discuss some of the most common mistakes when giving design critique, and how to avoid them.
One of the worst things you can do when giving design critique is to be vague or general. For example, saying "I don't like it" or "It looks good" does not provide any useful information or guidance for the designer. Instead, you should be specific and concrete, and explain why you have a certain opinion or suggestion. For example, saying "The contrast between the text and the background is too low, which makes it hard to read" or "The layout is clear and consistent, which helps the user navigate the interface" gives the designer more insight and direction.
The main idea here is that when giving feedback on designs, it's a big mistake to be vague or general. Instead of just saying you like or dislike something, it's crucial to be specific. For example, pointing out a specific issue like "the text is hard to read due to low contrast" or praising a good aspect such as "the layout helps users navigate" provides better guidance. The insight is that clear and detailed feedback is key to helping designers improve their work effectively.
To ensure specificity in design critique, anchor your feedback to design principles. Break it down: identify the element, relate it to a design rule or goal, and suggest a measurable improvement. This method transforms vague impressions into actionable insights, fostering a constructive dialogue that can lead to real enhancements in the design.
Crafting an optimal online community user interface demands precision. When offering design critique, avoid the pitfall of vagueness. Instead of generic statements like "I don't like it," delve into specifics. For instance, pinpoint concerns like "Low text-background contrast impairs readability" or commend with clarity, such as "The layout's consistency aids seamless navigation." Concrete feedback provides designers with actionable insights, fostering a collaborative and growth-oriented design process. Let's elevate our interfaces with purposeful critique and refinement.
I've heard quite a number of times people say that,"something feels off" or "I can't point it out." Vague critiques like this should not be employed in design critiques. A clear and consistent message is key and gives the designer direction in order to improve the product.
Being vague or general in design critique is like trying to navigate with a blurry map—it leaves everyone unsure of the destination. It's not about pointing fingers; it's like offering clear directions. Instead of saying, "I don't like it," pinpoint specific aspects. It's like saying, "Let's turn left at the confusing color choice." Precision turns critique into a useful roadmap for improvement. So, if you want your feedback to be a guiding light, steer clear of the fog of vagueness.
Another common mistake when giving design critique is to be personal or emotional. For example, saying "You are a bad designer" or "You have no taste" is not only rude and unprofessional, but also irrelevant and unhelpful. Design critique should focus on the work, not the person, and should be objective and respectful. Instead of attacking or praising the designer, you should focus on the strengths and weaknesses of the design, and how it meets or fails the user needs and goals.
Design critique should center around the work or project itself. Focus on evaluating the strengths and weaknesses of the design in relation to user needs and objectives. This fosters a respectful work environment, centered on collaboration and continuous improvement.
Ideally personal opinions and emotions should not be part of a design critique. Focusing on data, known UX patterns, heuristics and user research helps taking a more scientific approach to a design decision. Of course it's not always easy, often there are visual design decisions (regarding a color, radius, spacing...) where it will end up being a personal preference. In this case it's important to look if it's possible to find a parallel with a visual decision made in the past (for example, we used a 6px radius already for all the other containers so we should stay consistent). When it really gets down to aesthetics it's also possible to call a vote between X people and ask to vote the favorite version between A, B and C for example.
Crafting an effective user interface for online communities demands a nuanced approach. It's crucial to hone the skill of design critique, fostering improvement, learning, and collaboration. A prevalent misstep is injecting personal or emotional elements. Constructive feedback delves into the design, steering clear of personal remarks. It's counterproductive to label someone as a "bad designer." Instead, focus on the design's merits and shortcomings in meeting user needs. Objectivity and respect are paramount, creating a space for growth and collaboration in the dynamic realm of UX design.
Dudo que haya mayor error que abordar un proceso de design critiques desde el estómago, con la emoción en la mano o desde el "me gusta" o no. Para que un feedback sea efectivo, es clave que lo abordemos desde la intención sana y constructiva y, para ello, es necesario enfocarse en datos obtenidos, contextos de usuario y sus objetivos y desde las claves del negocio. Solo cuando tratamos de ser lo más objetivos posible, realmente aportamos valor a nuestros compa?eros y compa?eras en el proceso de crítica de sus dise?os, aportando valor extra al resultado :)
Being sentimental, especially for people in the position of power, can happen often times in the case where they do not like the designer or person handling the project. Design critiques should focus solely on the work.
A third common mistake when giving design critique is to be biased or subjective. For example, saying "I don't like this color" or "This font is outdated" is based on your personal preferences or assumptions, not on the user research or design principles. Design critique should be based on evidence and logic, not on opinions or feelings. Instead of imposing your own taste or style, you should consider the context and purpose of the design, and how it aligns with the user expectations and behaviors.
Crafting an optimal online community interface involves strategic choices. Reflecting on UX principles, it's crucial to avoid a common pitfall: subjective critique. Rather than saying, "I dislike this color," a more effective approach is anchoring feedback in evidence and logic. Aligning design choices with user expectations is pivotal. Consider the context and purpose, referencing user research and principles. A well-crafted interface is a marriage of functionality and user-centric design, steering clear of personal bias for a seamless user experience.
Strategic UX Designer | Driving User-Centric Solutions in Complex Environments |?Ambient
Bias in design critique isn't limited to personal taste; it can also stem from current trends, past experiences, or even the halo effect, where one aspect of the design unduly influences overall judgment. A key strategy is to consciously adopt multiple perspectives during a review. For instance, consider asking, "How would this design be received by a new user versus a power user?". This helps to uncover blind spots and ensures that the critique is balanced, comprehensive, and empathetic to diverse user needs.
Letting bias or subjectivity creep into design critique is like adding a personal filter—it distorts the view. It's not about personal taste; it's like evaluating a recipe based on objective ingredients. Instead of saying, "I prefer blue," focus on universal principles like readability or contrast. Stripping away bias ensures your critique is a fair judge. So, if you want your feedback to be clear and unbiased, stick to the universal design cookbook and leave personal flavors aside.
A fourth common mistake when giving design critique is to be negative or destructive. For example, saying "This is terrible" or "This will never work" is demoralizing and discouraging for the designer, and does not offer any constructive feedback or solutions. Design critique should be positive and supportive, not harsh or critical. Instead of pointing out only the flaws or problems, you should also acknowledge the achievements or potentials, and suggest ways to improve or enhance the design.
I kinda' hate the sandwich method ?? I know when people are doing it and I feel it's slightly demeaning. That doesn't mean you shouldn't commend someone for good work, but do it in a natural, authentic way. People sense when you're just doing a "method" and offering gratuitous praise. Instead, try to share feedback in a way that recognizes the receiver as the expert. Here are 2 methods: 1. Talk about the problem and let them come up with a solution. Instead of "Contrast on this text is too low. You need to increase it" say "I'm having difficulty seeing that text. Can we make it more visible?" or 2. Formulate it as a question. Continuing the example, it could be "Do you think it would be good to bump up the contrast of this text? "
What works best for me is the sandwich method: start with a positive, follow with constructive feedback, and end on an encouraging note. This not only maintains morale but also propels the design forward with actionable steps, fostering a culture of growth and collaboration. The goal is to ensure the designer feels challenged yet supported, turning the critique into a stepping stone for excellence rather than a stumbling block.
The focus here is to provide feedback from our perspective on some design decisions. It is important to be constructive in our feedback, as we are collaborating to solve problems. When providing criticism, it is helpful to include reasons and suggestions. This will help to keep the focus on product development, rather than on criticism itself.
Crafting an interface for online communities demands thoughtful design critique. A critical misstep, often encountered, involves negativity or destructiveness. Simply labeling a design as "terrible" or doomed without offering constructive insights hinders collaboration. Effective feedback balances acknowledgment of achievements, highlighting potential, and suggesting improvements. Encouraging a positive, supportive atmosphere in design critique fosters growth and innovation. Remember, every flaw is an opportunity for enhancement in the intricate canvas of online community interfaces.
A fifth common mistake when giving design critique is to be prescriptive or authoritative. For example, saying "You should do this" or "You must change that" is imposing your own vision or decision on the designer, and does not respect their autonomy or creativity. Design critique should be collaborative and dialogical, not directive or dictatorial. Instead of telling the designer what to do or how to do it, you should ask questions or offer alternatives, and invite them to explore or experiment with different options.
Encouraging designers to think critically about their work is more effective than dictating changes. This not only respects the designer's autonomy but also prompts them to consider alternatives from a place of ownership. The aim is to guide them to their own insights, fostering an environment where creativity and innovation are achieved through collaboration, not command.
When crafting a user interface for online communities, I prioritize a collaborative approach to design critique. One common misstep is being overly prescriptive or authoritative. Rather than dictating changes, I believe in fostering a dialogue. Instead of saying, "You should do this," I opt for posing questions or suggesting alternatives. This approach respects the designer's autonomy and encourages exploration. Effective critique, in my experience, embraces a collaborative spirit, ensuring a more enriching and creative design process.
A sixth common mistake when giving design critique is to be unprepared or uninformed. For example, saying "I don't know" or "I don't care" is showing a lack of interest or involvement in the design process, and does not contribute to the feedback or learning. Design critique should be prepared and informed, not spontaneous or ignorant. Before giving design critique, you should review the design brief, the user research, the design goals, and the feedback criteria, and familiarize yourself with the design context and constraints.
Be prepared for the design critique session because everyone else has put in a lot of effort to get ready. The last thing designers want is no feedback. If you're not ready to provide feedback, it's better to reschedule for another day. This way, you'll have extra time to review the design brief, wireframes, prototypes, and everything else. It'll also save time for everyone else in the meeting.
Designer - Here is what I made because of... Others (start looking at the UI and zone out on what the designer is saying)- The icon looks off, alignment is off, visual hierarchy blah blah... Let the designer talk. Let them express. Probe them on why THEY did something the way they did it. Figure out what is THEIR take on the problem and the solution. Help them to critique THEIR own work.
By extending Design Critique sessions to all team members, the team can achieve a broader sharing of knowledge, promoting a deeper understanding of all projects. This practice creates an environment where everyone perceives themselves as co-owners, driving collaboration and increasing understanding of the implications of design and development decisions throughout the organization. Implementing Critique sessions also reinforces the entire design process. By presenting and discussing work with colleagues, designers have the opportunity to refine their solutions, identify potential blind spots, and improve them. This contributes to a more robust and effective design.
Timing is a crucial factor when providing design feedback. To enhance the receptiveness of the person receiving the critique, it's essential to be mindful of when you approach them. Instead of bombarding individuals with feedback unexpectedly, take a moment to ask them about their availability and willingness to receive constructive input. This demonstrates respect for their time and workflow but also ensures that your message is received with a more open mindset.
Here's more food for thought: remember that effective design critique is a two-way street, like a friendly game of catch. Encourage open dialogue, listen actively, and embrace diverse perspectives—it's like adding different ingredients for a richer recipe. And just like a good story, end on a positive note by highlighting what works well. So, if you want your design critique to be a collaborative masterpiece, consider these extra ingredients for a successful feedback session.