udsen11golden – https://medibang.com/author/28579327/

Design critique — structured review of design work with the goal of identifying weaknesses and opportunities for improvement — is one of the most valuable practices available to design teams for improving design quality before work is built and shipped. Critique that is conducted well accelerates the design process by surfacing problems early when they are least expensive to address. Critique that is conducted poorly — either too gentle to identify real problems or too harsh to be received constructively — produces work that is not improved by the review process and a team whose willingness to share work in progress deteriorates over time.Separating Description from JudgmentThe most important discipline in effective design critique is separating description — what is actually present in the design — from judgment — whether what is present is right or wrong. Critique that leads with judgment (“this button is in the wrong place”) is harder to receive constructively than critique that leads with observation (“I notice that this button is positioned after the content it acts on”). The observation creates space to examine the design decision; the judgment implies it is settled. Descriptive critique invites the designer to participate in evaluating the observation (“yes, I put it there because…”) in a way that judgmental critique does not, and produces better quality conversation about the design.Design Critique vs. Design Review https://dnsk.work/blog/wireframes-the-grayscale-lies-we-tell-before-the-real-design-happens Design critique — examination of design work from multiple perspectives to identify weaknesses and opportunities — is different from design review, which typically means approval of design work for the next stage of development. The distinction matters because critique should welcome challenging questions and uncomfortable observations, while review tends toward gatekeeping, and the psychological framing affects the quality of discussion. Critique asks “how can this be improved?” and welcomes uncertainty; review asks “is this good enough to proceed?” and tends toward yes/no judgments. Both are valuable in appropriate contexts, but mixing them — treating critique as approval-seeking — undermines the quality of both processes.Giving and Receiving CritiqueGiving effective critique requires: grounding observations in the design’s goals and user needs rather than personal preference, providing specific and actionable feedback rather than vague dissatisfaction, and distinguishing between problems that need to be addressed before proceeding and observations that are worth considering but not critical. Receiving critique effectively requires: listening without defending before fully understanding the observation, asking clarifying questions before explaining rationale, and evaluating critiques on their merits rather than on the authority or relationship of the person offering them. Both giving and receiving critique are skills that improve with practice, and teams that invest in developing these skills produce better work at lower cost than teams that avoid critique because it is uncomfortable.