『The Question: Design System Collaborative Learning』のカバーアート

The Question: Design System Collaborative Learning

The Question: Design System Collaborative Learning

著者： Ben Callahan
無料で聴く

今ならプレミアムプランが3カ月 月額99円

2026年5月12日まで。4か月目以降は月額1,500円で自動更新します。

概要

 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 ❤️© Copyright 2026, Learning Mode, LLC
エピソード
  • Episode 071 Deep Dive: The Criticality of Design Systems with Ben Callahan & Vitaly Friedman

    Episode 071 Deep Dive: The Criticality of Design Systems with Ben Callahan & Vitaly Friedman
    2026/03/29

    Episode 071 Deep Dive: The Criticality of Design Systems with Ben Callahan & Vitaly Friedman

    In 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 Notes
    00:04 Introduction and episode overview
    01:48 Vitaly's background: complex systems, B2B, insurance, European Parliament
    03:01 The pressure of high-stakes work and measuring before/after impact
    05:19 Ben's upcoming book, published by Smashing Magazine
    05:44 Survey overview: methodology and FigJam data access
    06:11 Q1 Results: 57% selected "loss of essential money"; write-in responses
    07:08 Q2 Results: even distribution across team sizes; Cockburn's scale model
    08:03 Vitaly on loss of trust and reputation as missing modern categories
    09:29 Expanding the criticality framework for today's digital landscape
    10:52 Defining workflow analysis vs. task analysis
    14:33 Financial app example: importing a portfolio (task) vs. market analysis (workflow)
    15:56 Key finding: workflow analysis correlates with team size, not criticality
    17:23 Peter: using AI agents as a team of one to conduct workflow analysis
    19:41 Community discussion: respondents who selected "loss of life"
    20:09 David (Mayo Clinic): design system tokens and cascading patient-room risk
    21:32 Taylor: higher criticality means more questions and stakeholders, not a different process
    23:52 Vitaly: poor data visualization choices can cascade into financial loss
    24:20 Reference: The Fifth Discipline by Peter Senge (1990)
    25:08 Hattie (John Deere): autonomous vehicle safety warnings and multi-team sign-off
    26:41 Jesse (NAVA): public benefits delivery—if this fails, someone doesn't eat
    28:10 Vitaly: legacy systems as an underappreciated source of fragility and criticality
    30:06 Taylor: legacy is an iceberg—you don't know what you've got until you knock
    31:58 Kele: integrating a design system and AI tooling into existing enterprise SaaS
    33:17 Level-setting AI expectations with leadership
    35:42 Greg: AI tooling as a potential accelerator for legacy accessibility migration
    39:38 Vitaly: migrating away from legacy means designing the change, not just the UI
    40:06 Ben: FOMO-driven AI adoption decisions
    41:32 Taylor: legacy systems are often politically protected
    44:15 Ben: systems thinkers evaluated on product KPIs—structural misalignment
    46:35 Kele: reframing "healthy tension" as creative friction with different mandates
    49:22 Closing and thank-yous
    49:48 Redwoods membership, UX London, previous episode with Hannah

    Where to find the hosts
    Ben 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.com

    Vitaly Friedman is a UX Lead and founder of Smashing Conference. Connect with him on LinkedIn: https://bit.ly/43Iig8B

    Get the Raw Data
    Access the complete survey data from Episode 071: https://bit.ly/4rYcRTk

    Review the FigJam notes
    Dig into the collaborative notes from the deep dive: https://bit.ly/4bKWSlt

    Join the conversation
    Participate in future episodes and contribute to the next survey: https://bit.ly/answerTheQuestion
    続きを読む 一部表示
    52 分
  • Episode 071 Recap: The Criticality of Design Systems with Ben Callahan & Vitaly Friedman

    Episode 071 Recap: The Criticality of Design Systems with Ben Callahan & Vitaly Friedman
    2026/03/29

    Episode 071 Recap: The Criticality of Design Systems with Ben Callahan & Vitaly Friedman

    Introduction
    Host 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 Notes
    00:00 - Welcome and introductions; Vitaly reflects on surprises from the deep dive
    00:27 - How The Question works: survey Monday, deep dive Thursday, recap to follow
    01:41 - The Coburn Scale and how it shaped the survey questions
    03:45 - Survey results: why "loss of essential money" topped the criticality scale
    04:23 - Vitaly's take: loss of reputation and trust as proxies for financial loss
    05:30 - Write-in responses: loss of transparency, essential data, and future compatibility
    07:28 - Hyper-personalization and ephemeral UI: validating experiences we can't fully see
    08:50 - Decisions as infrastructure: encoding decisions into markdown and design systems
    11:57 - Automation and AI across design, code, and UI—and what that means for human oversight
    13:52 - "Flying blind": the risks of building layers atop systems we don't fully understand
    16:30 - Defining workflow analysis vs. task analysis and why it matters
    19: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 criticality
    25:32 - Design systems sandwiched between product teams and top-down quality guidelines
    29:35 - Legacy software: an underappreciated risk factor and political minefield
    32:39 - Migrating legacy means migrating flows, habits, and ways of working—not just UI
    34:46 - What Vitaly is working on: events, video courses, design patterns, and upcoming books
    36:14 - How to stay connected; Redwoods community open for membership

    ---

    Where to Find the Hosts
    Ben 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.com

    Vitaly Friedman is a UX Lead and founder of Smashing Conference. Connect with him on LinkedIn https://bit.ly/43Iig8B

    Get the Raw Data
    Access the complete survey data from Episode 071 to conduct your own analysis: https://bit.ly/4rYcRTk

    Review the FigJam Notes
    Dig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4bKWSlt

    Join the Conversation
    The 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
    続きを読む 一部表示
    38 分
  • Episode 070 Deep Dive: Lasting Design System Infrastructure with Ben Callahan & Hannah Clarke

    Episode 070 Deep Dive: Lasting Design System Infrastructure with Ben Callahan & Hannah Clarke
    2026/03/16
    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
    続きを読む 一部表示
    53 分
まだレビューはありません