Reusable UI components make up the meat of most design systems, component libraries, and living style guides. One of the biggest challenges in building a design system is agreeing just how these UI components should look and function. We often forget the small details: - How does the component resize to accommodate varying amounts of content? - How does the component look when its disabled? - How does the component resize to accommodate different viewport sizes? - How does the component transition between its states? Plus, every question a design system team faces poses a new opportunity for them to disagree. I’ve spent days discussing how tables work with design teams, because they’re just so complex. The audience will leave my talk with an understanding of the following: - Which details designers and engineers overlook when building the most common components. - How to drive team agreement on how components look and function.