A design crit is a structured feedback session to strengthen your work before it is final. Unlike a review, crits are about progress, not approval. By gathering perspectives from across disciplines you uncover blind spots, improve resilience, and build a healthier feedback culture. Use this when a component, token, or pattern is mostly designed but still flexible.
How to
(Optional call-out: a simple loop diagram showing "Context → Feedback → Iteration" to reinforce the cycle.)
-
Plan the invite list
Bring together people from different roles including design, engineering, product, accessibility, and content to get a full picture of use cases and constraints.
-
Choose a format
Decide how feedback will be gathered. Use a visual board, a short presentation, or a group discussion. This keeps the session focused and stops you from just taking notes on the day.
-
Set the tone
Frame it as a crit not sign-off. Make clear it is about improving the work not approving it.
-
Provide context
Share the component's purpose, where it fits, and what stage it is at. Explain what kind of feedback is most useful now.
-
Guide the discussion
Ask open questions like "What is missing?" or "Where could this break?" Respond to suggestions without leading or dismissing. Keep an open mind and avoid giving your own solutions.
-
Capture and share outcomes
Summarise insights, decisions, and actions. Share them back with the group and feed them into the next iteration.