{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Question: Design System Collaborative Learning","title":"Episode 072 Recap: Extreme Design System Support with Ben Callahan and Doug Neiner","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/0150a7a4\"></iframe>","width":"100%","height":180,"duration":1944,"description":"Episode 072 Recap: Extreme Design System Support with Ben Callahan and Doug Neiner\nHost Ben Callahan and co-host Doug Neiner, a design system practitioner at Planview, sit down immediately following the Episode 072 deep dive to reflect on what they heard from the community. The survey was sent to 1,081 design system practitioners and received 49 responses across four questions: what support do you currently offer; how would you change it without constraints; what prevents better support; and share a story of going above and beyond. The conversation covers the standout data points: the written vs. video documentation gap, the surprisingly high rate of dev environment access, embedding, private vs. public support channels, the balance between high-touch support and burnout, and the importance of being perceived as a helper rather than a blocker.\nShow Notes00:00 - Introduction and episode overview\n01:46 - Q1 data highlights: written vs. video documentation gap\n02:13 - Dev environment access: higher than expected at nearly 50%\n02:48 - Lowering the bar for video production with modern tooling\n03:15 - The perfectionist/design system practitioner Venn diagram\n04:00 - Q3 data: unclear ownership is low; headcount and competing priorities dominate\n04:30 - What \"competing priorities\" really means for system teams\n05:46 - Doug's support approach at Planview: docs, Slack channels, onboarding, and local debugging\n07:53 - Going beyond \"access\": running consumer products locally for deeper support\n08:28 - The most extreme example: getting an org-issued PC to support a heavy product\n09:42 - DMs vs. open channels: why private requests matter for trust\n10:34 - Not everyone is comfortable asking publicly—meeting people where they are\n11:20 - The problem with ticketing systems and over-streamlining support\n11:49 - How private support builds trust that eventually leads to public participation\n13:25 - Prioritizing relationship over efficiency: creating tickets on behalf of consumers...","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}