Design Critique & Review Process
Critique is one of the few design rituals nearly every team runs, and each team runs it a little differently. When it works, people leave with feedback they can act on. When it drifts, it turns into a status meeting or a round of personal taste.
The design organizations that publish their process agree on the basics. All 7 have the presenter open by stating the goal and the kind of feedback they want, and all 4 that cover scheduling hold critique on a fixed recurring slot. The details vary. 4 of 6 keep it a live session while Atlassian and Figma add written feedback for remote teams, and GitLab keeps the room to designers where 4 of 5 others invite product, engineering, and research.
- systems tracked
- 19
- sources cited
- 14
- evidence cards
- 87
- questions tallied
- 7
Popular questions
Each one is researched across every system we track. Pick one and it opens in chat, ready to send.
Systems tracked
The same core design systems are tallied on every topic, so answers compare like with like. See every source
- GOV.UK
- Shopify Polaris
- Google Material 3
- Atlassian
- GitHub Primer
- Salesforce Lightning
- Ant Design
- Mozilla Acorn
- Stripe Apps
- Adobe Spectrum
- Porsche Design System
- Intercom
- shadcn/ui
- Base Web
- GitLab Pajamas
- Radix UI
- Figma
- Microsoft Fluent
- IBM Carbon
Got a design critique & review process question?
Your first 3 questions are free. Every answer comes with the sources behind it.