{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Question: Design System Collaborative Learning","title":"Episode 076 Recap: Enabling Craft Through a Design System with Ben Callahan and ToniAnn Drenckhahn","html":"","width":"100%","height":180,"duration":2230,"description":"Episode 076 Recap: Enabling Craft Through a Design System with Ben Callahan and ToniAnn Drenckhahn\n\nBen 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.\nShow Notes\n0:02 — Ben introduces ToniAnn and the episode topic\n0:30 — Overview of the four survey questions\n3:20 — Survey methodology: 1,105 practitioners, 64 responses\n3:48 — ToniAnn on her expectations for the results\n4:05 — Tension around whether teaching craft is the DS team's job\n5:26 — Org size and career stage as factors in that tension\n6:57 — Teaching craft requires becoming educators, not just practitioners\n7:38 — Natural leaders and the weight of carrying craft alone\n8:11 — Distinguishing craft from quality: craft as input, quality as output\n10:55 — ToniAnn: craft is care embedded throughout the process, not just polish\n12:01 — Donnie's framing: craft is subjective, quality is objective\n12:17 — Sean's point: craft means something different for each role\n13:59 — AI enters: can AI produce quality without craft?\n15:32 — ToniAnn: craft requires care — and AI doesn't care\n17:08 — ToniAnn on why she resists calling AI output \"crafted\"\n19:11 — Googling the definition: \"made with high skill, care, or ingenuity\"\n19:45 — Craft requires sentience; quality may not\n20:39 — The order of operations framework: define quality first, then offer\n21:33 — When teams skip the definition and offer assets first\n23:08 — Leadership's role in setting and calibrating the craft bar\n24:06 — The build-vs-buy question and what it reveals about craft\n25:18 — The floor-ceiling framework: DS raises the floor,...","thumbnail_url":"https://img.transistorcdn.com/8ZoZhDyVederAFF-YGuNFdyaUvqzao3a6rYS6VFp3F4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9kMjQ2/MjJjYzdiYmY4MWU0/NGQzMjJmOGUyNzlj/YmMwZS5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}