It’s important to think through how you’ve set up your libraries and what you’re most interested in tracking in order to get the most out of Design System Analytics.
Here are some tips to get you started:
With the ability to create an unlimited number of teams on the Figma Organization tier, consider what level of usage information you would like to learn about your libraries. Design System Analytics can provide a breakdown of your library usage across teams, so for larger groups working within one team, if you desire more granular visibility into usage, consider dividing the work into smaller teams based on product focus or feature.
If you’re looking to roll out a new design system, a brand new library will allow you to track adoption of your new system and continue to measure usage of your old one. This can help you assess the ongoing usage of a legacy library and make informed decisions about the right time to stop supporting and fully deprecate an existing library.
If you’re interested in understanding how your team designs for different platforms or users, think about creating a different library for each. For example, you may want to create a library for iOS and a separate library for Android so you can ensure both platforms are being designed for equally. Since this approach also results in an increasing number of libraries, you should consider the trade-offs of having multiple libraries to maintain and the user experience of your designers.
Using Design System Analytics to find and update frequently detached components is one of the most common use cases we’ve heard from customers. While this is a great way to use the feature, it’s important to keep your original intentions in mind when evaluating component usage. For example, certain components are designed to be detached (for instance, a template for an entire screen to use as a starting point), so a high detachment rate for those components is not necessarily a bad thing. In fact, it’s an indication that the component is being used appropriately. However, in other scenarios this could be an indication that a component is not meeting designers’ needs and requires further investigation.
While the analytics themselves offer a number of interesting insights, you can also use Design System Analytics to supplement your design system documentation or to identify teams for additional context. If you click through to a component, you’re now able to access the files where this component is used, allowing you to easily grab real-life examples to share in your design system documentation. You can also identify which teams are using these components so you know who to follow up with for more qualitative feedback.
We hope these tips help you think through which analytics you’re most interested in and how to make sense of the numbers for your organization.
For a quick overview of what you can do with Design System Analytics, check out this video.