Episode 073 Recap: Design System AI Automation with Ben Callahan and Davy Fung

Episode 073 Recap: Design System AI Automation with Ben Callahan and Davy FungHost Ben Callahan and co-host Davy Fung, a product designer on the Atlassian Design System and host of the Design System Office Hours podcast, sit down immediately following the Episode 073 deep dive to reflect on what they heard from the community. The survey was sent to 1,077 design system practitioners and received 101 responses across four questions: what percentage of your workflow could be automated with AI today; what percentage should be automated; in what areas should we avoid AI automation and why; and what does craft mean to you in a 2026 design systems context. The conversation covers the gap between "could" and "should," the fear of loss embedded in resistance to automation, how process maturity should gate automation decisions, Bill's insight that automating broken processes masks their flaws, and the community's rich catalog of ways AI is already being put to practical, targeted use in design system workflows.Show Notes00:00 - Introduction and episode overview00:14 - Topic recap: AI as automation in design systems, four questions asked01:51 - Davy's starting point: Zero Height report showing 63% not using design system automation02:48 - Top-down AI mandates vs. practical decisions about what to automate03:18 - What's missing from the conversation: automation's impact on human connection rituals03:40 - The "could vs. should" gap: respondents who decreased their answer between Q1 and Q204:00 - What the decreasers said: loss of organizational context, institutional memory, and learning05:01 - Davy's pushback: documented knowledge scales better than single points of contact05:58 - The language of "loss" as sensitivity to losing control, not losing value06:16 - Ben's process maturity model: automate after you've learned the lessons manually07:11 - The risk of skipping straight to AI before understanding the work07:45 - Davy: scalability vs. the trap of being the sole expert in your org08:10 - Bill's insight from the deep dive: automating a process exposes its flaws — AI won't17:24 - Ben recaps Bill's argument: AI is powerful enough to automate things you shouldn't18:40 - Davy on CI pipeline linting: signals over blockers, data over gatekeeping19:55 - Ben: injecting human review earlier in the process keeps the PR doing its job20:35 - FigJam roundup: how community members are already using AI for automation21:00 - Use cases shared: single-use plugins, token automation, GitHub workflows, dashboards, prototyping21:37 - Davy: Atlassian's push toward higher-fidelity prototyping with AI tools22:35 - Davy's underrated use case: Slack MCP to capture keywords and surface support patterns23:11 - Ben: thin slices of AI help throughout the process vs. wide-scope automation24:15 - Closing reflections on craft: Samantha's quote — "AI is the average; craft is rising above it"25:21 - Thanks and outroWhere 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.comDavy Fung is a Product Designer on the Atlassian Design System and host of the Design System Office Hours podcast (https://bit.ly/3AQYjjI). Connect with him on LinkedIn (https://bit.ly/3XrcF2W).Get the Raw DataAccess the complete survey data from Episode 073 to conduct your own analysis: https://bit.ly/4cIjAv8Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4tW5ZHAJoin 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