# Design Critique

Design critique is a structured conversation that evaluates work against stated goals and evidence to produce specific, actionable feedback.

- Type: practice
- Domain: Leadership & teams
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/design-critique/>)

## What it means

A design critique is a focused review of design work intended to improve it, not to rate the designer. The presenter supplies context, goals, constraints, evidence, and the kind of feedback needed. Participants examine how well the work meets those objectives, ask clarifying questions, and offer reasoned observations rather than personal taste or instant redesigns.

## Why it matters

Good critique broadens a designer’s perspective, surfaces risks early, develops shared standards, and improves team craft. It also turns feedback from a stream of opinions into a learning practice. When psychologically safe and tied to user needs, critique can challenge weak decisions without turning the room into a referendum on status or personality.

## When to use it

Use critique while work is still changeable: after framing, during concept exploration, and before detailed implementation. It works best for questions that benefit from design peers’ perspectives. Use research, accessibility evaluation, legal review, or a decision meeting when those forms of evidence or authority are actually required.

## How it works

1. The presenter states the user problem, desired outcome, constraints, maturity of the work, evidence, and two or three feedback questions.
2. A facilitator establishes roles, timeboxes, respectful behavior, and whether the session is divergent feedback or a decision point.
3. Reviewers first ask questions, then describe what they observe and connect concerns to goals, principles, research, accessibility, or likely consequences.
4. The presenter listens and records without defending every choice; reviewers avoid prescribing a favorite solution unless invited.
5. Afterward, the designer clusters feedback, decides what to act on, documents rationale, and communicates unresolved risks or research needs.

## A practical example

A team critiques three ways to explain an insurance deductible. The presenter asks whether each concept supports comprehension and informed choice. Reviewers connect feedback to prior usability findings, flag jargon and a misleading visual hierarchy, and recommend testing two revised explanations with participants who have varied health-literacy levels.

## Where it breaks

Critique is still shaped by hierarchy, culture, and who is in the room. It cannot validate usability, desirability, accessibility, or legal compliance without appropriate evidence and expertise. Repeated critique can also homogenize work if teams reward conformity, so facilitators should protect exploration and invite dissenting perspectives.

## Common mistakes

- Offering taste-based judgments such as ‘I don’t like it’ with no objective or evidence.
- Turning feedback into a live redesign competition led by the most senior person.
- Presenting polished work so late that critique cannot meaningfully change it.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/design-critique/#visualization-design-critique>)

## Sources

1. [Design Critiques: Encourage a Positive Culture to Improve Products](<https://www.nngroup.com/articles/design-critiques/>) — Nielsen Norman Group · Professional guidance
2. [How We Do Design Critiques at Figma](<https://www.figma.com/blog/design-critiques-at-figma/>) — Figma · Practitioner case study

## Related topics

- [Design Review](<https://wiki.soroush.uk/topic/design-review/>)
- [Design Maturity](<https://wiki.soroush.uk/topic/design-maturity/>)
- [User Interviews](<https://wiki.soroush.uk/topic/user-interviews/>)
