Quantifying design system adoption is never as straightforward as it seems. What actually “counts” as a component, and how do we measure coverage across an experience? While many teams try to put numbers to these questions, the reality is messy: definitions are fuzzy, ownership is unclear, and metrics often fail to capture the whole picture. In this talk, we’ll explore the challenges of measuring components in design systems — from coverage metrics to questions of responsibility — and discuss why a shared understanding is just as important as the numbers themselves.

How does a design system win over product developers and designers? Everyone wants to ship new features, but they don't know why they should adopt your components and follow your guidelines. Let’s solve this, and turn apathy into excitement. We’ll explore the many ways to attract attention to your design system, elevate its place in your product, and build a thriving community around your work.

Design systems are often seen as essential in growing organizations. However, where design team is under-resourced, maintaining and evolving a coherent system becomes a challenge. This talk presents a pragmatic, engineer-led approach to promoting, using concrete React patterns and architecture.

Each component property in your design system serves as an entry point to your component library and its developer experience is largely influenced by their structure and implementation. In this talk, we'll explore multiple ideas to refine your thought process when working on components and make your libraries more user-friendly for other developers.