ABOUT THIS EPISODE
Davy and PJ discuss the "liability" of stale documentation and why AI still needs human oversight. They explore using Figma’s API to automate visual updates and kill the "pain in the butt" of manual maintenance.
English
United States
TRANSCRIPT 🔗
Are you the producer of this podcast?
Add a podcast transcript
Need Audio-to-Text?
Transcribe with Listen411 in Just 60 Seconds
SEARCH PAST EPISODES
Search past episodes of Design System Office Hours.
OTHER EPISODES IN THIS PODCAST
Davy and PJ dive into the Zeroheight's 2026 Design Systems Survey to figure out why 61% of teams are drowning in work while a third of them still have "no plans" to automate—plus, Davy forces PJ to listen to some truly questionable AI-generated design jokes.
Davy and PJ dive into the future of design tokens, exploring how to "tokenize everything" from complex color transformations (OKLCH) to utility tokens for motion and content strings.
Davy talks about trading a week of manual Figma updates for a "code-to-canvas" workflow that gets us "close enough" while PJ talks about running multiple worker-based agents to do production and qa work in tandem. Are these burner tasks?
We hit the Centennial! In our 100th episode, Davy and PJ look back on 4 years of our design systems chatter, before diving deep into the future of design systems: a community-driven, machine-readable schema that moves us past the "Figma-as-Source-of-Truth" era.
Davy and PJ discuss why the future of design workflow isn't just better handoff—it’s starting with the code itself.
Disclaimer: The podcast and artwork embedded on this page are from Davy Fung + PJ Onori, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
EDIT
Thank you for helping to keep the podcast database up to date.
