Design critiques and review practices are the structured conversations product and UX teams use to turn a work-in-progress design into a better one before it ships, sitting alongside cousins like heuristic evaluation and expert review that inspect a design against known usability principles instead of group opinion. Teams that skip structure end up with critiques that devolve into "I like it / I don't like it" opinion wars, HiPPO-driven decisions, or designers who leave the room more defensive than informed — none of which actually improves the product. The non-obvious insight worth carrying into every table below: the single biggest lever for critique quality isn't finding better critics, it's separating the design from the designer in language and process, so feedback can be specific, goal-tied, and evidence-based rather than a referendum on someone's taste or competence.
What This Cheat Sheet Covers
This topic spans 12 focused tables and 103 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: Critique & Review Foundations
Before running a session, it helps to know the vocabulary practitioners actually use — critique and design review are related but distinct rituals with different goals, and mixing them up is a common source of confusion in teams that are new to structured feedback.
| Concept | Example | Description |
|---|---|---|
A weekly 45-minute meeting where a designer presents a checkout flow and the team discusses whether it meets its goals. | A group conversation that analyzes a design and gives feedback on whether it meets its objectives; not simply judging the work. | |
A dedicated session called just to improve one in-progress screen. | A gathering with the sole purpose of improving a particular piece of work, distinct from a formal design review. | |
A usability expert inspects a finished flow and produces a written findings report. | A broader umbrella term for inspection-based evaluation methods (heuristic evaluation, expert review, standalone critique) that vary by who is doing the reviewing and why. | |
The designer presents the flow; the rest of the room acts as critiquers offering informed perspectives. | Critiques split into two roles — the person sharing the work and the people offering thoughts — and both roles can involve multiple people. | |
"Today we're only critiquing the onboarding flow's navigation logic, not visual polish." | Critiques stay productive only when there are unambiguous boundaries for what can and should be discussed. |