Bringing truth to Figma - Matt Rosenzweig (Config 2021)

This talk covers methods for auditing the codebase of a product in order to create Styles and Components in Figma that most closely match the Truth of the UI components your real users interact with in Production.

0:00 Introduction
2:15 Operating Environment
7:46 This is all amazing! There’s just one thing…
9:37 Color Styles
11:22 Text Styles
13:49 Notification Component
18:30 Button Component
20:43 Workflow
22:53 Guiding Principles
27:07 Thanks and acknowledgements

#figma #config2021 #EmbracingTheMess #config #design #ProductDesign #FigmaDesign #DesignSystems #Peacock #PeacockDesign #NBC #NBCDesign

[BenKopfLearning]

Excellent talk Matt, we are embarking on a similar journey at UPS. One thing we did in advance was have a substantial component audit done before we started using Figma. That made creating the initial Figma library relatively easy, but it produced the exact same mismatches you ran into between our code nomenclature and Figma. Making this work a shared effort with development also gets everyone sharing the same token/component language which helps in future conversations between teams. For example, we had "alerts", "notifications", "messages", and more talking about the same objects. Thanks for the advice, Ben