{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Question: Design System Collaborative Learning","title":"Episode 074 Recap: AI and Design System Visibility with Ben Callahan and Kaelig Deloumeau-Pregent","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/c6658b60\"></iframe>","width":"100%","height":180,"duration":2298,"description":"In this recap of Episode 074, Ben Callahan is joined by Kaelig Deloumeau-Pregent to share what we learned on the subject of AI and design system visibility. The conversation traces a question Kaelig first answered nearly a decade ago at a Salesforce symposium: How do we actually know how our design system is being used? We wondered how that question lands today as AI accelerates content, design, and code production.\nThe survey was sent to over 1,000 design system practitioners and received 78 responses across four questions: (1) current level of visibility into how design system assets are used across disciplines, including by AI; (2) biggest design system concerns as agents and automation produce more content at scale; (3) how the right balance between enforcement and enablement has shifted as AI enters the picture; and (4) the one thing they'd implement today to improve visibility without becoming the design police. Ben and Kaelig dig into a striking correlation between visibility maturity and enforcement-versus-enablement preferences, the \"fog of war\" metaphor for systems work, why accessibility may not belong inside design systems, and what shifting roles mean for designers in an agent-driven future.\nShow Notes\n00:00 — Welcome and reintroducing Kaelig\n00:28 — The 2016 Salesforce symposium and a decade-old magic wand question\n03:03 — A business opportunity: cross-discipline visibility tooling\n03:39 — Walking through the four survey questions and methodology (1,000+ sent, 78 responses)\n05:53 — Kaelig's in-progress article and crowdsourcing community thinking\n08:26 — Question 1: Self-reported visibility levels and what surprised us\n09:14 — Why design systems are for people, and the limits of robotized outreach\n10:38 — Visibility as stacked layers, not a single maturity rung\n11:00 — Question 2: When every concern is a top concern\n12:24 — Why feedback loops may be the most critical concern\n13:04 — Question 3: The balanced split on enforcement vs. enablement\n14:35...","thumbnail_url":"https://img.transistorcdn.com/8ZoZhDyVederAFF-YGuNFdyaUvqzao3a6rYS6VFp3F4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9kMjQ2/MjJjYzdiYmY4MWU0/NGQzMjJmOGUyNzlj/YmMwZS5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}