Where can I listen to this podcast?

This podcast is available on 4 platforms including Apple Podcasts, Spotify, and more. You can also use the RSS feed directly.

Does this podcast accept guests?

Yes, this podcast regularly features guests.

The Question: Design System Collaborative Learning

Claim This Podcast

by Ben Callahan

21 episodes

Updated Daily

Accepts GuestsHas Sponsors

Podcast Overview

The Question is a collaborative learning podcast about Design Systems. Smart people like you sign up, answer a few niche questions about design systems for each episode, and then we all get together to unpack the data we've gathered. Each week, I'll invite a new co-host to help facilitate the conversation. After the deep dive, the co-host and I record a recap of what we learned. That means, for each episode, you can listen to the recap and the full deep dive! If you're a design system practitioner, subscribe today (https://bencallahan.com/the-question) to receive an invitation to each episode. This only works if the community joins in! Stay in learning mode ❤️

Language

🇺🇲

Publishing Since

1/16/2026

Visit Website View on Apple Podcasts RSS Feed

Reach the team behind The Question: Design System Collaborative Learning

Verified contact details for this show aren't on file yet — sign up to get notified when they land.

Recent Episodes

June 15, 2026

Episode 075 Recap: The Design System Identity Crisis with Ben Callahan and Cassie Groos

Episode 075 Recap: The Design System Identity Crisis with Ben Callahan and Cassie Groos In this recap of Episode 075, Ben Callahan and Cassie Groos unpack what they learned from the community on the subject of the design system identity crisis. Cassie is preparing a talk on this theme for Hatch Conference in Berlin and used The Question as her research engine. The survey was sent to 1,083 design system practitioners and received 60 responses across five questions: team posture toward AI, belief in the "design systems as AI's necessary foundation" narrative, how roles have changed in the past 12 months, how respondents would redefine a design system today, and the bets they're making that might be wrong by next year. Ben and Cassie dig into what's actually driving AI adoption when only 25% believe it protects their roles, how DS practitioners can use their outsized organizational influence to own the AI quality bar, how the definition of "design system" is quietly expanding to include AI as an audience, and whether writing context files for AI means double work or just different work.Show Notes00:03 — Welcome and intro00:18 — Recap of all five survey questions and methodology: 1,083 sent, 60 responses02:25 — Acknowledging ongoing layoffs and supporting the community03:34 — A standout open response: "from clear vision to navigating the moment"04:08 — Cassie's reframe: an opportunity to decide where we end up04:48 — DS practitioners as an unseen but outsized influence in organizations06:33 — What's actually happening in Cassie's world right now: architecting under shifting ground07:40 — The tweet that kicked this all off: "we don't need component libraries anymore"08:11 — Cassie's talk at Hatch Conference, Berlin, September 1809:05 — Q1 and Q2 combined: 3 in 4 actively adopting AI; only 1 in 4 believes it protects their role10:27 — Owning AI workflows as the stronger protection narrative11:12 — Who's most protected: those managing the AIs and staying in the loop11:48 — Cassie on going straight in on AI from day one — and why12:01 — Ben's kids as gen-Z AI skeptics; the ethics of how models are trained15:04 — Question 4: what even is a design system? Neither of them can answer it cleanly15:29 — How respondents split: ~half said unchanged, ~40% said definition is expanding, ~12% not ready to define it yet16:32 — Cassie: at the top level, it's still just a system for designing stuff17:17 — Skills and agents casually showing up in answers as design system resources17:23 — Ben on culture as the real substance of a design system program18:42 — The new work layer: context files, components as data, AI-readable rules19:58 — Living in the seams: juggling human-serving and AI-serving outputs simultaneously21:18 — Why visual components won't disappear: people still like to look at things with their eyes22:46 — Token efficiency and the rising cost of AI: CRDs, compounding context, and who actually pays23:26 — Cassie: maybe we don't care — and maybe that's fine24:29 — Cassie's takeaway: want to see more demos and hear what others are actually building25:24 — Don't let pressure to adopt AI make us abandon our principles on quality and accessibility27:34 — Does Claude show up in Cassie's morning routine? Yes — Figma work via Claude Code, Copilot at work29:28 — Closing thanksWhere to Find the HostsBen Callahan is Founder of Sparkbox (<a href="https://sparkbox.com">https://sparkbox.com</a>) and Redwoods Design System Community (<a href="https://bencallahan.com/redwoods">https://bencallahan.com/redwoods</a>). Read his writings, have him present at your event, or engage with him as a coach or consultant at <a href="https://bencallahan.com">https://bencallahan.com</a>Cassie Groos is a freelance design systems specialist and senior product designer currently at Unily. Connect with her on LinkedIn: <a href="https://bit.ly/4tsihGU">https://bit.ly/4tsihGU</a> Get the Raw DataAccess the complete survey data from Episode 075 to conduct your own analysis: <a href="https://bit.ly/4tz9kLX">https://bit.ly/4tz9kLX</a> Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: <a href="https://bit.ly/42LJtWk">https://bit.ly/42LJtWk</a> 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: <a href="https://bit.ly/answerTheQuestion">https://bit.ly/answerTheQuestion</a>

June 15, 2026

Episode 075 Deep Dive: The Design System Identity Crisis with Ben Callahan and Cassie Groos

Episode 075 Deep Dive: The Design System Identity Crisis with Ben Callahan and Cassie Groos In this deep dive, Ben Callahan is joined by Cassie Groos — a freelance design systems specialist whose work spans consultancy, multi-brand systems, and the Hermes-to-Every rebrand — to explore what she calls the design system identity crisis. Cassie comes prepared: she's building out this topic as the focus of an upcoming talk at Hatch conference, and the community survey served as her research engine. The survey was sent to 1,083 design system practitioners and received 60 responses across five questions: team posture toward AI, belief in the "design systems as AI's necessary foundation" narrative, how roles have changed in the past 12 months, how respondents would redefine a design system today, and the bets they're making that might be wrong by next year. The conversation covers layoffs and job market anxiety in the DS community, whether the "moat narrative" holds up under scrutiny, the rising cost of AI tooling and what it means for democratized access to design, and the double work of living in the seam between old and new ways of working.Show Notes00:06 — Welcome and episode intro00:41 — Cassie's background: from NectarCard and Sketch symbols to multi-brand CMS-driven systems03:10 — Connecting with the community and how The Question was designed to serve talks and articles04:06 — Walking through all five survey questions05:33 — Survey methodology: 1,083 sent, 60 responses06:01 — Acknowledging ongoing layoffs and the design systems job market07:20 — A standout open response: "from clear vision to navigating the moment"07:46 — Cassie's reframe: this is our opportunity to decide where we end up08:15 — Q1 results: ~70% leaning in or experimenting carefully09:08 — Q2 results: 75% say the "DS as AI foundation" narrative won't hold for long09:37 — Cassie's reaction: DS practitioners are used to being ahead of the curve11:03 — Protection without job protection: AI still needs systems, but not as many people17:27 — Stephen Greco on going pedal-to-metal on AI because adopters already are18:31 — Owning the AI workflow as a competitive advantage: "we're in 30 products already"19:28 — Pedro Martins on system thinking as a demonstration of AI value20:26 — The cost of AI and what it means for design system teams21:22 — Kele on AI shifting from democratization to pay-to-play23:44 — Ismail Hamila on methodology versus superficial prompting26:07 — Cassie: DS practitioners can define and own the quality bar for AI component work27:03 — Peter Allen on cutting token consumption 87% through multi-agent MCP architecture28:18 — Michael Whitaker on leaning into AI personally after a recent layoff34:00 — The double-work problem: living in the seam between old and new workflows34:46 — Cassie: use AI to generate what AI needs; humans still must check the output35:40 — Hattie Tadsen on AI burnout and the cost of learning-while-reviewing37:04 — Mike Riley on context-specific prompt files for adopting dev teams37:33 — Joanna Kirtley on team burnout from constant AI tool churn38:02 — Kevin on leadership excitement creating downstream pressure on DS readiness39:14 — Cassie on AI burnout hitting high achievers hardest41:32 — Stephen Greco on betting that humans won't read docs directly within a year42:32 — "What do we actually do with all of this?" — new FigJam section for action items43:59 — Closing thanks and Redwoods demos as a next step44:27 — Announcements: Muir Woods hike, Sparkbox, Southleft, AI and Design Systems courseWhere to Find the HostsBen Callahan is Founder of Sparkbox (<a href="https://sparkbox.com">https://sparkbox.com</a>) and Redwoods Design System Community (<a href="https://bencallahan.com/redwoods">https://bencallahan.com/redwoods</a>). Read his writings, have him present at your event, or engage with him as a coach or consultant at <a href="https://bencallahan.com">https://bencallahan.com</a>Cassie Groos is a freelance design systems specialist and senior product designer currently at Unily. Connect with her on LinkedIn: <a href="https://bit.ly/4tsihGU">https://bit.ly/4tsihGU</a>Get the Raw DataAccess the complete survey data from Episode 075 to conduct your own analysis: <a href="https://bit.ly/4tz9kLX">https://bit.ly/4tz9kLX</a>Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: <a href="https://bit.ly/42LJtWk">https://bit.ly/42LJtWk</a>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: <a href="https://bit.ly/answerTheQuestion">https://bit.ly/answerTheQuestion</a>

May 13, 2026

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 Notes 00:00 — Welcome and reintroducing Kaelig 00:28 — The 2016 Salesforce symposium and a decade-old magic wand question 03:03 — A business opportunity: cross-discipline visibility tooling 03:39 — Walking through the four survey questions and methodology (1,000+ sent, 78 responses) 05:53 — Kaelig's in-progress article and crowdsourcing community thinking 08:26 — Question 1: Self-reported visibility levels and what surprised us 09:14 — Why design systems are for people, and the limits of robotized outreach 10:38 — Visibility as stacked layers, not a single maturity rung 11:00 — Question 2: When every concern is a top concern 12:24 — Why feedback loops may be the most critical concern 13:04 — Question 3: The balanced split on enforcement vs. enablement 14:35 — Pace layers, time, and when to enforce vs. let people roam 16:35 — Does accessibility actually belong inside the design system? 18:53 — Design system teams becoming the org's AI product-builder definers 19:30 — Educating the designers of tomorrow (including agents) 20:30 — The legal-approval bottleneck slowing AI enablement 20:55 — A standout open response: lightweight embedded signal collection at the point of consumption 21:46 — Just-in-time guidance and bringing developer experience to designers 22:31 — Pegah Amadi's Magnolia and weaving signals into workflow 23:00 — The "Fog of War" metaphor: attention as a system team's scarcest resource 24:48 — Sending scouts: proactive visibility across Slack, Drive, and roadmaps 27:03 — De-risking and saying no when the landscape shifts 28:30 — Cheap scouting with sentiment analysis and lightweight tooling 29:26 — Mapping Question 1 against Question 4: a clear visibility-to-enablement gradient 31:22 — Taming chaos vs. the plateau of sameness (Polaris, CalPete, Yesenia) 33:20 — Curiosity over policing: the posture of successful system teams 34:23 — What this means for designers facing a big role pivot 35:10 — Redwoods Community Hike at Muir Woods in June 37:11 — Closing thanksWhere to Find the Hosts Ben 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 Data Access the complete survey data from Episode 074 to conduct your own analysis: https://bit.ly/4t4rYv6Review the FigJam Notes Dig into the collaborative notes we took as a community during the deep dive: https://bit.ly/3OWYGk3Join the Conversation The 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

21 total episodes available

Similar Podcasts

Discover related shows you might enjoy

99% Invisible

Roman Mars

Pod Save America

Deep-dive analytics for The Question: Design System Collaborative Learning

Frequently asked questions

Have a different question and can't find the answer you're looking for? Reach out to our support team by sending us an email and we'll get back to you as soon as we can.

What is The Question: Design System Collaborative Learning?: The Question is a collaborative learning podcast about Design Systems. Smart people like you sign up, answer a few niche questions about design systems for each episode, and then we all get together to unpack the data we've gathered. Each week, I'll invite a new co-host to help facilitate the conversation. After the deep dive, the co-host and I record a recap of what we learned. That means, for each episode, you can listen to the recap and the full deep dive!

If you're a design system practitioner, subscribe today (https://bencallahan.com/the-question) to receive an invitation to each episode. This only works if the community joins in!

Stay in learning mode ❤️
How often does this podcast release new episodes?: This podcast updates daily.
Where can I listen to this podcast?: This podcast is available on 4 platforms including Apple Podcasts, Spotify, and more. You can also use the RSS feed directly.
Does this podcast accept guests?: Yes, this podcast regularly features guests.

Legal Disclaimer

Pod Engine is not affiliated with, endorsed by, or officially connected with any of the podcasts displayed on this platform. We operate independently as a podcast discovery and analytics service.

All podcast artwork, thumbnails, and content displayed on this page are the property of their respective owners and are protected by applicable copyright laws. This includes, but is not limited to, podcast cover art, episode artwork, show descriptions, episode titles, transcripts, audio snippets, and any other content originating from the podcast creators or their licensors.

We display this content under fair use principles and/or implied license for the purpose of podcast discovery, information, and commentary. We make no claim of ownership over any podcast content, artwork, or related materials shown on this platform. All trademarks, service marks, and trade names are the property of their respective owners.

While we strive to ensure all content usage is properly authorized, if you are a rights holder and believe your content is being used inappropriately or without proper authorization, please contact us immediately at hey@podengine.ai for prompt review and appropriate action, which may include content removal or proper attribution.

By accessing and using this platform, you acknowledge and agree to respect all applicable copyright laws and intellectual property rights of content owners. Any unauthorized reproduction, distribution, or commercial use of the content displayed on this platform is strictly prohibited.