The Question: Design System Collaborative Learning

Episode 071 Deep Dive: The Criticality of Design Systems with Ben Callahan & Vitaly FriedmanIn 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.The 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.Show Notes00:04 Introduction and episode overview01:48 Vitaly's background: complex systems, B2B, insurance, European Parliament03:01 The pressure of high-stakes work and measuring before/after impact05:19 Ben's upcoming book, published by Smashing Magazine05:44 Survey overview: methodology and FigJam data access06:11 Q1 Results: 57% selected "loss of essential money"; write-in responses07:08 Q2 Results: even distribution across team sizes; Cockburn's scale model08:03 Vitaly on loss of trust and reputation as missing modern categories09:29 Expanding the criticality framework for today's digital landscape10:52 Defining workflow analysis vs. task analysis14:33 Financial app example: importing a portfolio (task) vs. market analysis (workflow)15:56 Key finding: workflow analysis correlates with team size, not criticality17:23 Peter: using AI agents as a team of one to conduct workflow analysis19:41 Community discussion: respondents who selected "loss of life"20:09 David (Mayo Clinic): design system tokens and cascading patient-room risk21:32 Taylor: higher criticality means more questions and stakeholders, not a different process23:52 Vitaly: poor data visualization choices can cascade into financial loss24:20 Reference: The Fifth Discipline by Peter Senge (1990)25:08 Hattie (John Deere): autonomous vehicle safety warnings and multi-team sign-off26:41 Jesse (NAVA): public benefits delivery—if this fails, someone doesn't eat28:10 Vitaly: legacy systems as an underappreciated source of fragility and criticality30:06 Taylor: legacy is an iceberg—you don't know what you've got until you knock31:58 Kele: integrating a design system and AI tooling into existing enterprise SaaS33:17 Level-setting AI expectations with leadership35:42 Greg: AI tooling as a potential accelerator for legacy accessibility migration39:38 Vitaly: migrating away from legacy means designing the change, not just the UI40:06 Ben: FOMO-driven AI adoption decisions41:32 Taylor: legacy systems are often politically protected44:15 Ben: systems thinkers evaluated on product KPIs—structural misalignment46:35 Kele: reframing "healthy tension" as creative friction with different mandates49:22 Closing and thank-yous49:48 Redwoods membership, UX London, previous episode with HannahWhere to find the hostsBen Callahan is Founder of Sparkbox and Redwoods Design System Community. Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comVitaly Friedman is a UX Lead and founder of Smashing Conference. Connect with him on LinkedIn: https://bit.ly/43Iig8BGet the Raw DataAccess the complete survey data from Episode 071: https://bit.ly/4rYcRTkReview the FigJam notesDig into the collaborative notes from the deep dive: https://bit.ly/4bKWSltJoin the conversationParticipate in future episodes and contribute to the next survey: https://bit.ly/answerTheQuestion

Episode 071 Recap: The Criticality of Design Systems with Ben Callahan & Vitaly FriedmanIntroductionHost Ben Callahan and co-host Vitaly Friedman reflect on the insights from the Episode 071 deep dive on the criticality of design systems. Vitaly is a UX lead, founder of Smashing Conference, and practitioner working in complex enterprise environments—most recently with the European Parliament.The survey was sent to 1,069 design system practitioners and received 61 responses. Respondents were asked four questions through the lens of their single most critical product: how failure would impact end users (loss of comfort, discretionary money, essential money, or life); the size of the engineering team; how their design system supports that criticality and scale; and whether anyone in their org is doing workflow analysis with product users.Show Notes00:00 - Welcome and introductions; Vitaly reflects on surprises from the deep dive00:27 - How The Question works: survey Monday, deep dive Thursday, recap to follow01:41 - The Coburn Scale and how it shaped the survey questions03:45 - Survey results: why "loss of essential money" topped the criticality scale04:23 - Vitaly's take: loss of reputation and trust as proxies for financial loss05:30 - Write-in responses: loss of transparency, essential data, and future compatibility07:28 - Hyper-personalization and ephemeral UI: validating experiences we can't fully see08:50 - Decisions as infrastructure: encoding decisions into markdown and design systems11:57 - Automation and AI across design, code, and UI—and what that means for human oversight13:52 - "Flying blind": the risks of building layers atop systems we don't fully understand16:30 - Defining workflow analysis vs. task analysis and why it matters19:37 - The hypothesis: does higher criticality correlate with more workflow analysis? The data didn't confirm it.22:01 - What the data did show: team size as a stronger predictor than criticality25:32 - Design systems sandwiched between product teams and top-down quality guidelines29:35 - Legacy software: an underappreciated risk factor and political minefield32:39 - Migrating legacy means migrating flows, habits, and ways of working—not just UI34:46 - What Vitaly is working on: events, video courses, design patterns, and upcoming books36:14 - How to stay connected; Redwoods community open for membership---Where to Find the HostsBen Callahan is Founder of Sparkbox and Redwoods Design System Community. Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comVitaly Friedman is a UX Lead and founder of Smashing Conference. Connect with him on LinkedIn https://bit.ly/43Iig8BGet the Raw DataAccess the complete survey data from Episode 071 to conduct your own analysis: https://bit.ly/4rYcRTkReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4bKWSltJoin 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

IntroductionHost Ben Callahan is joined by co-host Hannah Clarke, UI Engineer at Intapp, for a live deep dive on building design system infrastructure that lasts. The survey went to 1,061 practitioners and received 45 responses across four questions: company leadership model, dedicated team roles, who owns coded component delivery, and what actions create a system that endures. The conversation spans surprising results, web component delivery strategies, the framework agnostic debate, the unicorn-hire problem, API flexibility, and the human community that makes any system worth building.This episode is made possible by Mintlify. If your design system documentation lives in five places and satisfies no one, Mintlify can provide one beautiful, AI-powered home for everything your team builds (and the why behind those decisions).Try it free → https://bit.ly/try-mintlify (use code MINT-THEQ for 50% off Pro for 6 months)Show Notes00:02 — Welcome, Hannah's intro, and sponsor message (Mintlify)01:07 — Hannah's background: UI Engineer at Intapp, full-stack roots, how she found the design systems space03:25 — Survey overview: Four questions, 1,061 sent, 45 responses04:39 — Q1: "Led by product" came in at ~40%, surprising Ben; Hannah less shocked given her experience06:31 — Q2: Front-end dev outranked UI design in dedicated roles; reference to Sean Bent's post on design system hiring trends08:22 — Community as infrastructure: Awareness and human connection matter as much as tooling; user showcase idea from Hannah's team retro11:14 — Joshua: In-person labs where consuming teams experiment with the design system to make it feel engaging12:13 — Hannah's delivery approach: Stencil + web components, outputting to multiple NPM packages (tokens, styles, web components, React 18, React 19 + SSR)14:33 — Q4 theme: Framework agnosticism as a longevity strategy; design-side agnosticism and Penpot as a Figma alternative16:50 — Josh: Journey from web components wrapped in React to going all-in on React and why17:48 — Real challenges wrapping web components for React: Shadow DOM, team culture resistance, the "pure React" demand19:09 — Post-processing scripts on top of Stencil: Default values, required props, types files, and developer quality-of-life improvements22:50 — Guy: AI workflow from Figma to production code; using Figma Console MCP to convert prototypes into design-system-compliant files; circumventing design tools altogether27:11 — Kelly: Laid off with her entire product design org; job postings pitting design vs. engineering; the value of tight cross-discipline collaboration30:54 — Hannah: The full-stack cycle — companies oscillate between specialists and generalists at their own peril32:23 — Greg: Flipping the unicorn question — even if unicorns existed, would they want to do everything expected of them?36:05 — Amy: Designers vibe coding directly in repos; how design systems can support that workflow and reduce chaos37:31 — Joanna: Built two full implementations (React + Angular) after teams refused a framework-agnostic approach; the real costs39:30 — Sean: Extending across iOS + Android; shared tokens, consistent naming, cross-platform rituals; treating Figma as a fourth platform41:22 — Managing cross-platform parity: Manual processes, shared style layers, prioritization by demand44:09 — Hannah: Why she moved away from "just React" thinking; the unsolved mobile challenge for a three-person team46:36 — API flexibility vs. rigidity: Joanna's case for flexible APIs; Hannah and Mike on finding the balance without losing consistency51:01 — Closing remarks and community announcementsWhere to Find the HostsBen Callahan, Founder of Sparkbox and Redwoods Design System Community: https://bencallahan.comHannah Clarke, UI Engineer at Intapp: https://bit.ly/47kl2lnGet the Raw Data: https://bit.ly/3OOuU0BReview the FigJam Notes: https://bit.ly/4rxa9E8Join the Conversation: https://bit.ly/answerTheQuestion

Episode 070 Recap: Lasting Design System Infrastructure with Ben Callahan & Hannah ClarkeThis episode is made possible by Mintlify. If your design system documentation lives in five places and satisfies no one, Mintlify can provide one beautiful, AI-powered home for everything your team builds (and the why behind those decisions).Try it free → https://bit.ly/try-mintlify (use code MINT-THEQ for 50% off Pro for 6 months)IntroductionIn Episode 070 of The Question, host Ben Callahan sits down with co-host Hannah Clarke, UI Engineer at Intapp, to recap a conversation about building design system infrastructure that lasts. The episode drew from a survey sent to 1,061 design system practitioners, yielding 45 responses across four questions: which leadership model best describes your company (engineering, product, design, or balanced); which roles have at least one dedicated person on your design system team (DevOps, design ops, UI design, front-end dev); who owns responsibility for delivering coded components; and what actions create a system that endures. The conversation ranges from surprising survey results and the unicorn-hire debate to web component delivery strategies, framework agnosticism, and the human infrastructure that keeps systems alive.Show Notes00:00 — Welcome & sponsor mention (Mintlify)00:45 — Survey methodology recap: 1,061 sent, 45 responses, four questions reviewed01:20 — Q1 results: Company leadership — "led by product" dominated; why that surprised Ben but not Hannah02:35 — Low "led by design" responses: what does that say about design's seat at the table?04:47 — Q2 results: Dedicated roles — front-end dev outranked UI design, which shocked both hosts05:35 — Job posting trends: Why available design system roles skew toward design over engineering06:49 — The unicorn problem: Companies asking for one person to do it all07:20 — Greg's insight from the deep dive: "I want to use my code knowledge to do my design job better"08:01 — Hannah's perspective: Understanding design makes you a better front-end developer, but specialisms matter09:10 — Q4 highlight: "Connecting people that ask about the system — tools will keep changing, but people will keep interest alive"10:02 — Human infrastructure: Why community-building is as foundational as technical tooling11:36 — Data note: Over 60% of Q4 responses mentioned humans, people, community, champions, or trust12:22 — The cultural hurdle: Solving a technical problem doesn't mean people will adopt it13:13 — Framework agnostic vs. framework-specific: Three respondents advocated for agnosticism; Joanna's team built two separate libraries14:08 — Hannah's approach at Intapp: Why they chose Stencil + web components and the longevity thinking behind it15:43 — How they actually deliver components: NPM packages for tokens, styles, web components, React 18, and React 19/SSR18:49 — Post-processing scripts on top of Stencil: Default values, required props, types files, and developer quality-of-life improvements20:26 — Lowering the barrier to adoption: Making it painless for consuming teams to say yes21:38 — Working with teams already using Material UI: Not replacing everything, but filling the gaps24:07 — What does DevOps actually mean on a design system team day-to-day?26:14 — Hannah's surprising reality: Nearly 100% of her time is infrastructure, not component-building28:04 — Design-side agnosticism: Is Figma-lock sustainable? What Guy's team is doing differently29:30 — Treating Figma as a platform (alongside iOS, Android, web) — a mindset for longevity30:16 — Documentation-driven implementation: Defining the component as data first, then expressing it in any tool31:23 — Closing thought: Systems that last are defined above the tools, not inside themWhere to Find the HostsBen Callahan is Founder of Sparkbox and Redwoods Design System Community. Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comHannah Clarke is a UI Engineer at Intapp. Connect with her on LinkedIn: https://bit.ly/47kl2lnGet the Raw DataAccess the complete survey data from Episode 070 to conduct your own analysis: https://bit.ly/3OOuU0BReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4rxa9E8Join 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