{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Question: Design System Collaborative Learning","title":"Episode 071 Deep Dive: The Criticality of Design Systems with Ben Callahan & Vitaly Friedman","html":"","width":"100%","height":180,"duration":3120,"description":"Episode 071 Deep Dive: The Criticality of Design Systems with Ben Callahan & Vitaly Friedman\nIn Episode 071, host Ben Callahan is joined by co-host Vitaly Friedman—UX Lead, author, and founder of Smashing Conference—for a deep dive into the criticality of design systems. Vitaly brings experience from complex enterprise environments, including a multi-year engagement consolidating 199 European Parliament websites into one across 25 languages.\nThe survey was sent to over 1,000 design system practitioners, yielding 61 responses. Participants were asked four questions through the lens of their single most critical product: (1) what level of impact would a product failure have on end users—loss of comfort, discretionary money, essential money, or life; (2) the size of their engineering team; (3) how they ensure their design system supports that criticality; and (4) whether anyone in their org is doing workflow analysis with users.\nShow Notes\n00:04  Introduction and episode overview\n01:48  Vitaly's background: complex systems, B2B, insurance, European Parliament\n03:01  The pressure of high-stakes work and measuring before/after impact\n05:19  Ben's upcoming book, published by Smashing Magazine\n05:44  Survey overview: methodology and FigJam data access\n06:11  Q1 Results: 57% selected \"loss of essential money\"; write-in responses\n07:08  Q2 Results: even distribution across team sizes; Cockburn's scale model\n08:03  Vitaly on loss of trust and reputation as missing modern categories\n09:29  Expanding the criticality framework for today's digital landscape\n10:52  Defining workflow analysis vs. task analysis\n14:33  Financial app example: importing a portfolio (task) vs. market analysis (workflow)\n15:56  Key finding: workflow analysis correlates with team size, not criticality\n17:23  Peter: using AI agents as a team of one to conduct workflow analysis\n19:41  Community discussion: respondents who selected \"loss of life\"\n20:09  David (Mayo Clinic): design system tokens and...","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}