Evolving systems with data and heart
summary
A design system team describes concrete outcomes: they use the Figma REST API and plugin analytics to track component usage, ship an auto‑lint that is later disabled, and iterate quickly. After adjustments the plugin shows an 80% performance improvement, a 50% rise in daily users, double the linting events and 450+ design issues fixed. Examples include real-time lint tradeoffs, dashboarded trends, and AI-driven observations that actually changed priorities.
AI-written summary · about
chapters (10)
- 0:00Design system team intro
- 1:04Why build design tools
- 3:57Plugin growth data
- 6:04Data vs intuition
- 8:33Autolint feature balance
- 10:41Post-autolint iteration
- 11:46Finding balance over time
- 13:11AI-driven design systems future
- 16:05Data and heart tension
- 16:46Getting started guide
related talks
30mEvolutionary Design Systems
57mUnifying design and development through design systems
25mUsing Figma to go beyond Figma
18mDesign Systems in Practice
49mExploring the Anatomy of Design Systems
14mRethinking Designer-Developer Collaboration
14mEmpowering designers: AI, design systems, and quality
19mYou've Built a Design System - Now What?