Tracking Design System Deviations

Last summer I had the pleasure of co-facilitating a discussion on tracking design system deviations at one of my favorite design system events, The Question. Ben Callahan wrote a fantastic recap of the conversation, with the key takeaway being that design system deviations are a signal of potential feature gaps, not necessarily a violation that must be “corrected”.

Here’s a video recap and the collaborative Figjam from the discussion.


Curious about the technical implementation of the system I set up to track design system usage at Honeycomb? You can learn more about it in my post: Using Observability Tools to Track Frontend Migrations.