Design System Component Audit
What are they designing?
An audit of our button, input, and card components ahead of consolidating three slightly different design systems into one.
Who is it for?
Engineers and designers across three product teams who currently maintain their own component variants.
What are they trying to improve?
I've mapped where the components diverge, but I'm not confident I've picked the right components to prioritize first. Looking for a sanity check on scope and sequencing.
Feedback requested
Discussion (2)
Starting with buttons and inputs is the right call — they're the highest-usage, highest-divergence components, so consolidating them first unblocks the most teams.
The audit doesn't mention accessibility state parity (focus states, contrast ratios) across the three variants, which is often where the real inconsistency lives, not just visual styling.
Add an accessibility pass to the audit itself before prioritizing — a component that looks 90% aligned visually can still have wildly different focus/contrast behavior underneath.
Really thorough mapping — the side-by-side component comparison table makes the divergence obvious at a glance.
Cards feel deprioritized here, but they're used in more places than buttons across our team's product, so I'd push back a little on the sequencing.
Worth a quick usage-count pass across all three teams' codebases before finalizing the order — actual usage frequency might reorder the priority list.