Episode 074 Recap: AI and Design System Visibility with Ben Callahan and Kaelig Deloumeau-Pregent

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.The 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.Show Notes00:00 — Welcome and reintroducing Kaelig00:28 — The 2016 Salesforce symposium and a decade-old magic wand question03:03 — A business opportunity: cross-discipline visibility tooling03:39 — Walking through the four survey questions and methodology (1,000+ sent, 78 responses)05:53 — Kaelig's in-progress article and crowdsourcing community thinking08:26 — Question 1: Self-reported visibility levels and what surprised us09:14 — Why design systems are for people, and the limits of robotized outreach10:38 — Visibility as stacked layers, not a single maturity rung11:00 — Question 2: When every concern is a top concern12:24 — Why feedback loops may be the most critical concern13:04 — Question 3: The balanced split on enforcement vs. enablement14:35 — Pace layers, time, and when to enforce vs. let people roam16:35 — Does accessibility actually belong inside the design system?18:53 — Design system teams becoming the org's AI product-builder definers19:30 — Educating the designers of tomorrow (including agents)20:30 — The legal-approval bottleneck slowing AI enablement20:55 — A standout open response: lightweight embedded signal collection at the point of consumption21:46 — Just-in-time guidance and bringing developer experience to designers22:31 — Pegah Amadi's Magnolia and weaving signals into workflow23:00 — The "Fog of War" metaphor: attention as a system team's scarcest resource24:48 — Sending scouts: proactive visibility across Slack, Drive, and roadmaps27:03 — De-risking and saying no when the landscape shifts28:30 — Cheap scouting with sentiment analysis and lightweight tooling29:26 — Mapping Question 1 against Question 4: a clear visibility-to-enablement gradient31:22 — Taming chaos vs. the plateau of sameness (Polaris, CalPete, Yesenia)33:20 — Curiosity over policing: the posture of successful system teams34:23 — What this means for designers facing a big role pivot35:10 — Redwoods Community Hike at Muir Woods in June37:11 — Closing thanksWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bencallahan.com/redwoods). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comKaelig Deloumeau-Pregent is a design systems leader with experience at Salesforce, Shopify, and beyond. Connect with him on LinkedIn: https://www.linkedin.com/in/kaelig/Get the Raw DataAccess the complete survey data from Episode 074 to conduct your own analysis: https://bit.ly/4t4rYv6Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/3OWYGk3Join the ConversationThe Question explores design systems topics through community research and deep-dive discussions. Participate in future episodes and contribute to the next survey: https://bit.ly/answerTheQuestion