Design System Tactics.
Whether you're starting fresh or maintaining a mature system, this growing collection of tactics is designed to help you make progress at every stage.
Design Crit
A design crit is a collaborative session focused on improving the work—not signing it off. Unlike a review, it invites diverse perspectives to stress-test the design while it’s still flexible. The goal is shared progress, not perfection.
When to Use
Use when a component is mostly designed but still open to change. Crits are ideal for getting feedback before handoff and aligning across disciplines. Involve designers, engineers, content, accessibility, and product teams to uncover blind spots and edge cases.
Steps
-
Define the invite list. Include people from different roles and teams to get a full view of use cases and constraints.
-
Set the tone. Frame the session as a crit, not a review. Make clear it’s about improving the work, not approving it.
-
Provide context. Share the component’s purpose, where it fits, and what kind of feedback you’re after.
-
Guide the discussion. Ask open questions like “What’s missing?” or “Where could this break?” Encourage practical, constructive input.
-
Capture outcomes. Summarise key insights, decisions, and next steps so they feed into the next iteration.
Outcomes
- Stronger, more resilient designs
- Fewer surprises at dev time
- Healthier feedback culture
