Episode 074 Deep Dive: AI and Design System Visibility with Ben Callahan and Kaelig Deloumeau-PregentIn this deep dive, Ben Callahan is joined by Kaelig Deloumeau-Pregent—a veteran design system practitioner whose career has spanned the BBC, The Guardian, Financial Times, Salesforce, Shopify, Netlify, and most recently Intuit—to explore the intersection of AI and design system visibility. Kaelig shares how a question raised back in a 2016 design systems symposium ("If you had a magic wand, what would you change?") still resonates today: practitioners want more visibility into how their systems are actually being used. The survey was sent to 1,081 design system practitioners and received 78 responses across four questions: current level of visibility into design system asset usage, biggest concerns as AI agents produce content at scale, how the enforcement vs. enablement balance has shifted with AI, and what one thing they'd implement to improve visibility without becoming the "design police." The conversation explores the "fog of war" metaphor for incomplete knowledge in systems work, the tension between surveillance and creative freedom, librarians vs. police as governance models, and how AI changes who (or what) is deviating from the system. Show Notes00:39 — Kaelig's background: from a French web agency to BBC, Guardian, FT, Salesforce, Shopify, Netlify, and Intuit06:56 — Becoming a systems thinker before "design systems" was a career07:38 — The 2016 magic-wand question and why visibility is still the wish08:34 — Walking through the four survey questions09:22 — Survey methodology: 1,081 practitioners, 78 responses10:04 — Reviewing Q1: most teams have manual or partial visibility, very few have robust automated tracking12:01 — Visibility isn't just internal; the end customer dimension and zombie code12:27 — Q2 results: AI concerns are "all of the above," and Brandon's optimistic reframe13:26 — Q3 results: enforcement vs. enablement is balanced, with 14% choosing "other"14:35 — The "fog of war" metaphor and the risk of a design system surveillance state17:02 — Peter on cultural contracting and counterbalancing forces in an org18:58 — The "helpful Clippy" view: visibility as a signal for better docs and training21:24 — Doug's question: is resistance to tracking a designer-specific concern?22:13 — Greg on discipline, rigidity, and adapting design practices for AI workflows24:22 — Lightweight, embedded signal collection at the point of consumption25:31 — Magnolia and ESLint-style "disable with a reason" patterns for design27:10 — Jeff on measuring adoption and building relationships to capture wins for leadership29:48 — Alexander on percentile-matching to surface emerging patterns and snowflakes32:02 — Pedro on treating deviations as a "confession room," not policing33:53 — The correlation between visibility (Q1) and enablement (Q4) responses35:20 — The "plateau of sameness" and how the design system kicks back at scale36:16 — ToniAnn: less visibility breeds more assumptions; talk to people37:44 — Stephen on AI flipping enforcement toward enablement, and tracking why agents deviate39:41 — Robin on enforcement and enablement as intertwined, not opposing42:00 — Greg on building decision points into AI skills and rules44:57 — Danita: what level of accountability belongs to the human using AI?45:27 — Trust cultures, talent pools, and where the cursor sits on enforcement47:38 — Non-negotiables: accessibility and regulated environments49:01 — Closing announcements: Redwoods Compass alpha, Config hike, Sparkbox, Southleft Where to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bit.ly/44lzHL5). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.com Kaelig Deloumeau-Pregent writes about design systems and AI at https://www.kaelig.fr Get the Raw DataAccess the complete survey data from Episode 074 to conduct your own analysis: https://bit.ly/4t4rYv6 Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/3OWYGk3 Join 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
