The Question: Design System Collaborative Learning

Ben Callahan

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 ❤️

  1. 3 hr ago ·  Bonus

    Episode 079 Recap: The Evolution of Design System Documentation with Ben Callahan and Afyia Smith

    Episode 079 Recap: The Evolution of Design System Documentation with Ben Callahan and Afyia SmithBen Callahan and Afyia Smith, a content designer and technical writer specializing in design systems, recap what the community said about who owns documentation and where docs are headed now that machines are reading them too. The survey went to more than 1,100 design system practitioners and drew 61 responses across five questions. The conversation covers the shift from prose to structured content, the case for a dedicated documentation owner, the design system knowledge architect role, the DSDS spec work with PJ Onori, and the fourteen respondents who said machines will be the only future readers of their docs. Show Notes00:00 — Welcome and introductions00:14 — Black-and-white prints and a giraffe collection01:00 — Almost 80 episodes, and the first one on docs01:24 — Survey setup: 1,100 practitioners, 61 responses02:34 — Afyia answers the open-ended question herself02:41 — Documentation as a knowledge layer, not just content03:20 — Focused ownership and just-in-time documentation04:08 — What docs looked like in the early design system days04:30 — Bare, scattered, outdated, ungoverned06:17 — The case for a point person07:53 — The design system knowledge architect role08:20 — Coming back a year later to the same mess11:03 — Question one results: who owns documentation11:57 — By design or by default?12:24 — Digging into the 30% who answered "other"13:36 — Question two: everyone figuring agentic workflows out alone14:24 — The correlation that wasn't in the data15:00 — Question three: reporting on agentic workflow success16:07 — Ownership reveals visibility more than success17:00 — Machine readable versus machine parsable17:20 — Surface-level changes versus foundational ones17:49 — Bad docs surfaced everywhere are still bad docs18:49 — Working upstream of AI19:38 — The component schema work with PJ Onori20:45 — DSDS, doc origin, and metadata as a trust layer23:32 — Question five: writing for humans, machines, or both24:48 — What we would lose without human-readable reference sites26:48 — Why documentation has always been the passion Where 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.com Afyia Smith is a content designer and technical writer focused on design system documentation, governance, and knowledge architecture. Connect with her: https://bit.ly/4vVUhNP Get the Raw DataAccess the complete survey data from Episode 079 to conduct your own analysis: https://bit.ly/4yV4JrD Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4gismBZ 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 Music licensed through Soundstripe.Code: C1COHEMFO6L4XE0H

    Episode 079 Recap: The Evolution of Design System Documentation with Ben Callahan and Afyia Smith

  2. 4 hr ago

    Episode 079 Deep Dive: The Evolution of Design System Documentation with Ben Callahan and Afyia Smith

    Episode 079 Deep Dive: The Evolution of Design System Documentation with Ben Callahan and Afyia Smith Ben Callahan is joined by Afyia Smith, a content designer and technical writer who spent five years as a documentation specialist on the design system team at Epic Games, built AI readiness frameworks and governance models there, and now collaborates with PJ Onori on the DSDS documentation spec. Together with the community, they dig into who owns design system documentation and what changes when agents start reading it. The survey went to more than 1,100 design system practitioners and drew 61 responses across five questions. The conversation covers machine readable versus machine parsable formats, recipes and gotchas files, decision trees for agents, the split between reference and guidance documentation, just-in-time docs, and whether AI should be writing documentation at all. Show Notes 00:07 — Welcome to the Episode 079 deep dive 00:40 — Afyia's path into design system documentation 02:25 — Five years as a documentation specialist at Epic Games 03:50 — Emailing PJ Onori to contribute to DSDS 06:21 — This week's five questions, 1,100 sent, 61 responses 09:18 — Breaking down the responses that chose "other" 10:15 — Everyone figuring agentic workflows out on their own 11:04 — Looking for a correlation that isn't there 12:56 — Robin Di Capua on encoding compositional do's and don'ts 14:24 — Patterns, templates, and recipes in the DSDS spec 18:08 — Doug Neiner on recipes and gotchas files 19:16 — Kelby Gassman on docs turning into decision trees 23:52 — Kevin Coyle on machine readable versus machine parsable 26:09 — Surface-level delivery versus foundational content 27:04 — Stephen Greco on moving from Markdown to JSON and YAML 29:27 — Robin Di Capua on keeping prose alongside structured data 30:56 — Stephen Greco on reference documentation versus guidance 34:05 — Question five: humans, machines, or somewhere between 35:54 — Doug Neiner's Kindle and recipe book analogy 37:14 — Shaun Bent on two clients at opposite extremes 38:41 — Afyia on not picking a side 42:30 — Hattie Tadsen on meeting people where they are 44:02 — Just-in-time documentation as the goal 45:28 — Doug Neiner on AI-generated docs and false productivity 46:22 — Afyia: don't use AI to write the docs 47:19 — Hattie Tadsen on AI-assisted first drafts Where 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.com Afyia Smith is a content designer and technical writer focused on design system documentation, governance, and knowledge architecture. Connect with her: https://bit.ly/4vVUhNP Get the Raw Data Access the complete survey data from Episode 079 to conduct your own analysis: https://bit.ly/4yV4JrD Review the FigJam Notes Dig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4gismBZ 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 Music licensed through Soundstripe.Code: C1COHEMFO6L4XE0H

    Episode 079 Deep Dive: The Evolution of Design System Documentation with Ben Callahan and Afyia Smith

  3. 3 Aug ·  Bonus

    Episode 078 Recap: The Psychology of Design Systems with Ben Callahan and Kacey Wood

    Ben Callahan and Kacey Wood, Product Designer for Design Systems at Tabs, explore the psychology behind design system buy-in, the question Kacey brought after wondering what a design systems college curriculum would actually need to cover beyond tokens and components. The survey went out to over 1,100 design system practitioners and drew 50 responses across four questions. The conversation covers reactance theory, the endowment effect, curse of knowledge, social proof, the IKEA effect, foot-in-the-door, Aristotle's modes of persuasion, and where influence ends and manipulation begins. Show Notes00:00 — Welcome and introductions00:12 — Where the question came from: a design systems degree00:43 — The people layer matters as much as IC fundamentals01:32 — The four questions we asked this week02:44 — Craft, care, and reasoning as what actually convinces03:49 — The escape route as a pressure relief valve04:25 — Reactance theory, explained through a picky eater05:31 — Telling designers they don't have to use the system05:55 — Endowment effect and resistance to change06:48 — Does reactance skew young and endowment skew experienced?07:32 — Curse of knowledge: explaining tokens on day one08:10 — Writing for the people just behind you09:07 — Social proof and design system advocate groups09:39 — How social proof showed up in the open text answers10:40 — The IKEA effect, and a listener assembling IKEA furniture11:35 — Finding the small systems already scattered across an org12:35 — Flow, difficulty, and whether adoption can be too easy13:24 — Make it so easy they can't not use it14:07 — Foot in the door: a small yes leads to a bigger yes14:48 — Broadening what counts as adoption15:20 — Aristotle's ethos, pathos, and logos16:29 — Setting up the influence versus manipulation question17:20 — Is influence versus manipulation even the right question?18:34 — Hierarchy, company values, and team goals19:04 — Power dynamics and psychological safety19:44 — Skills you don't realize you're building20:40 — Building the curriculum for the people side of the work Where 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.com Kacey Wood is a Product Designer for Design Systems at Tabs, previously building systems at BetMGM and EY. Connect with her here: https://bit.ly/4aOYcV0 Get the Raw DataAccess the complete survey data from Episode 078 to conduct your own analysis: https://bit.ly/4w3P47v Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4fhdlkz 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 Music licensed through Soundstripe.Code: XXANWFJBSMJEM81F

    Episode 078 Recap: The Psychology of Design Systems with Ben Callahan and Kacey Wood

  4. 3 Aug

    Episode 078 Deep Dive: The Psychology of Design Systems with Ben Callahan and Kacey Wood

    On Episode 078, Ben Callahan is joined by Kacey Wood, Product Designer for Design Systems at Tabs and member of Redwoods design system community. She and Ben open the floor to the community on the psychological side of systems work. The survey went out to over 1,100 design system practitioners and drew 50 responses across four questions. The community digs into reactance theory, where influence becomes manipulation, power dynamics and reporting structure, the behavioral concepts behind buy-in, and what any of this means when the consumer is an AI agent. Show Notes00:04 — Welcome and episode framing00:36 — Kacey Wood's path from data analytics to design systems01:21 — Building 0 to 1 at BetMGM, then starting over at Tabs03:45 — The four questions we asked this week04:41 — 50 responses from over 1,100 practitioners09:12 — Janesa Chan on how org placement shapes perception10:43 — Nobody relies on just one buy-in tactic11:38 — Data isn't enough, the story is what convinces12:31 — Peter Allen on collaboration versus mandate13:27 — Guy Segal challenges the influence/manipulation framing15:08 — Kacey on whether you're willing to lose16:11 — Steven Deeds on manipulation as disingenuous influence18:37 — Reactance theory, explained through a picky eater20:03 — Daniel Florez on skin in the game21:01 — Janesa Chan on giving designers the choice22:53 — Amy Ogg on power dynamics and reporting lines25:19 — Guy Segal on why educating people doesn't work28:40 — Endowment effect, curse of knowledge, social proof29:36 — The IKEA effect and giving people a win31:00 — Aristotle's modes of persuasion33:58 — Rebecca Ostrich on not condescending to people38:19 — ToniAnn Drenckhahn: design systems makes me a better person39:17 — Kyle Hyams on soft skills over craft41:22 — AI has no reactance, so what changes?43:56 — Peter Allen's personal note to his AI agents Where 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.com Kacey Wood is a Product Designer for Design Systems at Tabs, previously building systems at BetMGM and EY. Connect with her here: https://bit.ly/4aOYcV0 Get the Raw DataAccess the complete survey data from Episode 078 to conduct your own analysis: https://bit.ly/4w3P47v Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4fhdlkz 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 Music licensed through Soundstripe.Code: XXANWFJBSMJEM81F

    Episode 078 Deep Dive: The Psychology of Design Systems with Ben Callahan and Kacey Wood

  5. 13 Jul ·  Bonus

    Episode 077 Recap: Culture vs Compliance in Design Systems with Ben Callahan and Lauren LoPrete

    Ben Callahan welcomes Lauren LoPrete, Head of Design Foundations at Mercury, back to the show to talk through design system culture versus compliance—the tension between earning adoption and enforcing it. Fresh off Lauren's Config talk on design systems anarchy, the two dig into what it means to relinquish control, and why letting go tends to improve adoption rather than threaten it. The survey went to 1,105 design system practitioners and drew 61 responses across four questions. The recap covers the belief-versus-reality gap in the data, a layered model of embedding, enabling, and enforcement, the venue-and-band metaphor for systems work, how AI is reshaping who builds and who reviews, and the scope of a design foundations role that owns both the system and the tooling. Show Notes00:00 — Welcoming Lauren LoPrete back to the show00:45 — Lauren recaps her Config talk on design systems anarchy01:19 — The community's shift away from control01:55 — The episode's mood: hard-won equanimity02:29 — Becoming the ocean: a Leonard Cohen reminder03:20 — "Be the water" and the responsive web parallel04:28 — Tying back to the systems-brain mindset05:17 — Leading a team through constant industry thrash06:35 — Owning both design systems and tooling07:40 — Framing the topic: culture versus compliance08:10 — The four questions, 1,105 sent, 61 responses09:27 — Is culture bottom-up and compliance top-down?10:27 — Culture as the overlap of shared beliefs11:45 — Walking through the layers-of-governance diagram13:55 — Enforcement, enabling, embedding as seasons15:53 — Letting agents carry the enforcement layer17:26 — Documentation as the objective standard18:48 — The venue-and-band metaphor for systems19:18 — Detaching components as part of designing20:37 — Judgment, safety, and the public-channel callout21:14 — When AI empowers PMs to prototype everything22:51 — Titles dissolving into subject-matter expertise24:37 — Connecting the system to prototyping tools25:47 — Design foundations as context for agentic work26:44 — Holding two speeds at once27:34 — The relief of not being alone Where 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.com Lauren LoPrete is Head of Design Foundations at Mercury and has built and led design systems at Expedia, Dropbox, and Block. Connect with her on LinkedIn: https://bit.ly/LaurenLoPreteLinkedIn Get the Raw DataAccess the complete survey data from Episode 077 to conduct your own analysis: https://bit.ly/4v3uKSc Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/44UhlkK 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 Music licensed through Soundstripe. Codes: RWX0YUSGWXLGICPW, SBJUDQ7C3ULIOBOM

    Episode 077 Recap: Culture vs Compliance in Design Systems with Ben Callahan and Lauren LoPrete

  6. 13 Jul

    Episode 077 Deep Dive: Culture vs Compliance in Design Systems with Ben Callahan and Lauren LoPrete

    Ben Callahan hosts the Episode 077, full community deep dive with Lauren LoPrete, Head of Design Foundations at Mercury, who has built and led design systems at Expedia, Dropbox, and Block. Lauren opens with her own arc, years spent grasping for control and pressuring leadership to mandate adoption, and how things improved once she let go. From there the room takes over, working through where culture ends and compliance begins. The survey reached over 1,100 design system practitioners and drew 61 responses across four questions. The conversation moves from the belief-versus-reality gap in the data through the timing of mandates, the accessibility "Trojan horse," internal versus external culture, a layered model of embedding, enabling, and enforcement, and a long thread on AI, prototyping, and whether teams will keep caring about output. Community voices include Erin Potter, Peter Allen, Greg Johnson, Michael Warren, Guy Segal, Rebecca Ostrich, Jeff Pelletier, Kele Webner, Alicia Payette, and more. Show Notes00:00 — Cold open: a system needs an opinion00:45 — Lauren on leading her fifth design system02:30 — Giving up the fight for a leadership mandate03:30 — "Design systems are culture work in disguise"05:00 — The four questions, restated06:30 — The mood: hard-won equanimity08:10 — 1,100+ surveyed, 61 responses09:40 — The belief-versus-reality gap in the data11:30 — Erin Potter on timing and system maturity14:00 — Peter Allen on Venmo's culture-plus-mandate moment15:40 — Greg Johnson on the accessibility backdoor16:30 — Lauren on the business-value Trojan horse19:00 — Michael Warren on internal versus external culture22:00 — Ben's embedding, enabling, enforcement layers23:30 — Lauren on seasons of enforcement and flexibility25:00 — Guy Segal on layers of company culture27:00 — Designing conditions where good choices emerge30:00 — Building prototyping tools for designers first32:00 — Rebecca Ostrich on intrinsic motivation34:00 — Question four themes: letting go paid off36:00 — Jeff Pelletier on the vibe-coding-to-agentic spectrum38:00 — Michael Warren on AI being oversold41:00 — Kele Webner on prototypes with no basis in reality43:00 — Lauren on choosing influence and authority44:30 — Alicia Payette on enterprise-trained AI and risk47:00 — Peter Allen on building context for your system49:30 — Lauren's last word: same old struggles, new user Where 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.com Lauren LoPrete is Head of Design Foundations at Mercury and has built and led design systems at Expedia, Dropbox, and Block. Connect with her on LinkedIn: https://bit.ly/LaurenLoPreteLinkedIn Get the Raw DataAccess the complete survey data from Episode 077 to conduct your own analysis: https://bit.ly/4v3uKSc Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/44UhlkK 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 Music licensed through Soundstripe. Codes: RWX0YUSGWXLGICPW, SBJUDQ7C3ULIOBOM

    Episode 077 Deep Dive: Culture vs Compliance in Design Systems with Ben Callahan and Lauren LoPrete

  7. 29 Jun ·  Bonus

    Episode 076 Recap: Enabling Craft Through a Design System with Ben Callahan and ToniAnn Drenckhahn

    Episode 076 Recap: Enabling Craft Through a Design System with Ben Callahan and ToniAnn DrenckhahnBen Callahan and ToniAnn Drenckhahn recorded this recap the morning after their community deep dive, reflecting on what stood out from the data and the conversation. The survey went out to 1,105 design system practitioners; 64 responded. Topics include the distinction between craft and quality, two frameworks for thinking about how systems enable craft, the role of leadership in setting a craft culture, and how AI is complicating the idea of what it means to make something well. Show Notes0:02 — Ben introduces ToniAnn and the episode topic0:30 — Overview of the four survey questions3:20 — Survey methodology: 1,105 practitioners, 64 responses3:48 — ToniAnn on her expectations for the results4:05 — Tension around whether teaching craft is the DS team's job5:26 — Org size and career stage as factors in that tension6:57 — Teaching craft requires becoming educators, not just practitioners7:38 — Natural leaders and the weight of carrying craft alone8:11 — Distinguishing craft from quality: craft as input, quality as output10:55 — ToniAnn: craft is care embedded throughout the process, not just polish12:01 — Donnie's framing: craft is subjective, quality is objective12:17 — Sean's point: craft means something different for each role13:59 — AI enters: can AI produce quality without craft?15:32 — ToniAnn: craft requires care — and AI doesn't care17:08 — ToniAnn on why she resists calling AI output "crafted"19:11 — Googling the definition: "made with high skill, care, or ingenuity"19:45 — Craft requires sentience; quality may not20:39 — The order of operations framework: define quality first, then offer21:33 — When teams skip the definition and offer assets first23:08 — Leadership's role in setting and calibrating the craft bar24:06 — The build-vs-buy question and what it reveals about craft25:18 — The floor-ceiling framework: DS raises the floor, product teams set the ceiling26:38 — ToniAnn: the system as quality floor, not limiting factor27:35 — AI as a tool to test the ceiling and inform what gets encoded28:33 — ToniAnn: "Full freedom. Please do it."29:39 — Competing values framework: system teams shifting from internal to external orientation30:51 — ToniAnn on the "hold the line" era and how posture has evolved33:29 — The vision for the system has to be bigger than components34:40 — ToniAnn's takeaway: lean into the floor-ceiling narrative next week35:49 — Closing reflections from Ben and ToniAnn Where 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.com ToniAnn Drenckhahn is a design systems leader currently at Etsy, previously at BetMGM. Connect with ToniAnn: https://bit.ly/ToniAnnLinkedin Get the Raw DataAccess the complete survey data from Episode 076 to conduct your own analysis: https://bit.ly/4vb9Cuh Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4a5V6LP 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

    Episode 076 Recap: Enabling Craft Through a Design System with Ben Callahan and ToniAnn Drenckhahn

  8. 29 Jun

    Episode 076 Deep Dive: Enabling Craft Through a Design System with Ben Callahan and ToniAnn Drenckhahn

    Episode 076 Deep Dive: Enabling Craft Through a Design System with Ben Callahan and ToniAnn Drenckhahn Ben Callahan is joined by ToniAnn Drenckhahn, a design systems leader currently at Etsy and formerly at BetMGM, where her work on primitive components and foundational design quality prompted this episode's question. The survey drew 64 responses from 1,105 practitioners and surfaced a striking finding: not a single respondent said their organization has no craft gap. Topics include a floor-ceiling framework for how systems teams and product teams share responsibility for craft, the difference between craft and quality, community perspectives on teaching versus encoding, the role of leadership and culture, and what AI means for the future of craft as a human skill. Show Notes0:09 — Ben introduces Episode 076 and co-host ToniAnn Drenckhahn0:46 — ToniAnn on what led her to this topic: BetMGM, Etsy, and AI pressure1:49 — The arc from policing to enabling — and the pendulum swinging back2:25 — Survey overview: four questions, 1,105 practitioners, 64 responses4:46 — Ben's read of the data: "accumulated realism"5:15 — Zero respondents said their org has no craft gap5:44 — Time and authority: the two blockers named most6:42 — 72% said teach and encode both; 67% rely on opinionated components8:11 — 70% cited no shared definition or speed pressure as the root cause8:39 — ToniAnn introduces the floor-ceiling framework9:36 — Ben: the floor is what we build in; the ceiling is how it gets used10:32 — Mike Riley on the wide quality gap between adopters using the same components12:21 — Janesa Chan on guiding consumers through the contribution process13:48 — Janesa Chan on educational techniques that ebb and flow14:48 — Ilya Grey on views, floor plans, and embracing the front-end stack16:24 — ToniAnn on co-designing screens and templates with consuming teams17:21 — Vision has to go beyond components17:49 — Shaun Bent on culture and department leadership overriding education18:48 — Lauren on hiring visual designers with a systems mindset19:45 — Lauren: before that, the feedback loop was too big20:39 — Lauren on closing the loop when teams deviate (data viz token example)22:09 — Jesse James: encoding is tactical and measurable; culture takes time22:38 — Jesse James: craft is like authenticity — it takes time to become the team's voice23:36 — Greg Johnson on system maturity, adoption, and finding patterns in the wild25:54 — The order of operations diagram: offer first vs. define first26:21 — Flipping the order: define quality, then offer27:18 — What happens when systems teams only offer the basics28:16 — Workshop approaches for building a shared definition of quality28:49 — ToniAnn on the BetMGM vision work and staying out of the way30:12 — Ilya Grey on customer expectations as a layer above the quality ceiling30:41 — Robin Di Capua on defining quality across departments32:07 — Caroline Horn: what customers actually said quality means to them34:17 — Donnie D'Amato: craft is subjective, quality is objective35:15 — Donnie on the button example: readable labels vs. border radius36:40 — Robin on how even "objective" quality resists consensus38:06 — Donnie on design attractors and the best button42:18 — Peter Allen: DS solves 80% of problems, but craft still matters in the 20%42:58 — Ben: does AI lower the need to learn design at all?44:21 — Automating craft vs. automating the basics45:20 — Derek Onay: does encoding lower the skill, or free up time for it?46:44 — Ilya Grey: high-taste environments improve taste over time47:34 — ToniAnn's closing thought: using AI to democratize education, not just speed48:49 — Ashley and Casey's series on education in design systems49:18 — Ben wraps up; Donnie previews the Undefined event in NYC Where 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.com ToniAnn Drenckhahn is a design systems leader currently at Etsy, previously at BetMGM. Connect with ToniAnn: https://bit.ly/ToniAnnLinkedin Get the Raw DataAccess the complete survey data from Episode 076 to conduct your own analysis: https://bit.ly/4vb9Cuh Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4a5V6LP 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

    Episode 076 Deep Dive: Enabling Craft Through a Design System with Ben Callahan and ToniAnn Drenckhahn
See All (29)

About

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 ❤️

Information

  • Creator
    Ben Callahan
  • Years Active
    2026
  • Episodes
    29
  • Rating
    Explicit
  • Copyright
    © Copyright 2026, Learning Mode, LLC
  • Show Website
    The Question: Design System Collaborative Learning
  • Provider