The design system community engaged with practitioners to understand their experiences with tracking deviations from design systems. Questions focused on whether deviations are tracked, methods used, and lessons learned from data collection. A survey received 57 responses revealing a mix of approaches, such as awkward spreadsheets and elegant code instrumentation. Many practitioners cited challenges like organizational fear and complexity in implementation. Adrianne Daley from Honeycomb discussed their strategy using react-scanner scripts for tracking changes, analyzing data quarterly to identify trends in component usage.
Participants in the design system community were asked if they track deviations, how they do it, and what they've learned from gathering these metrics.
Adrianne Daley shared insights on tracking design system deviations, emphasizing the importance of clear naming conventions and data analysis.
Many design system practitioners reported using different methods, including spreadsheets and code instrumentation, to monitor deviations from the design system.
Organizational fear, complexity, and a lack of understanding are significant barriers that prevent teams from effectively tracking design system deviations.
Collection
[
|
...
]