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

The Question: Design System Collaborative Learning

The Question: Design System Collaborative Learning

著者： Ben Callahan
無料で聴く

概要

 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 069 Recap: Rebuilding a Design System Mid-Flight with Ben Callahan & Shimma Hassan

    Episode 069 Recap: Rebuilding a Design System Mid-Flight with Ben Callahan & Shimma Hassan
    2026/03/02

    Episode 069 Recap: Rebuilding a Design System Mid-Flight with Ben Callahan & Shimaa Hassan

    ---

    Introduction

    In Episode 069 of The Question, host Ben Callahan (founder of Sparkbox and Redwoods Design System Community) sits down with co-host Shimaa Hassan.

    The conversation centers on one of the most persistent challenges in design systems work: how do you rebuild the foundation while the plane is still flying? Ben and Shimaa share survey results from 1,061 design system practitioners (53 responses) and open the floor to a rich community discussion on versioning strategies, token architecture, breaking changes, and the ongoing tension between innovation and standardization.

    Survey questions asked: (1) How many times a month do you think about throwing your design system away and starting over? (Range: 0–5) | (2) If you chose to start over, what's the one decision you'd make differently on day one? | (3) How do you keep product teams confident in a system that's actively being rebuilt underneath them? | (4) Tell us a story about rebuilding a system mid-flight.

    ---

    Show Notes
    0:05 — Introductions: Ben welcomes Shimaa Hassan as co-host for episode 69
    0:18 — Episode context: rebuilding a design system mid-flight and how Ben and Shimaa connected
    1:00 — Survey recap: the "how often do you think about starting over?" question and why Shimaa expected a higher number
    1:36 — Data results: the ~50/50 split and overview of the three open-text survey questions
    2:30 — The "fork and maintain" approach: letting teams use the old version while building the new one
    3:19 — Shimaa's iterative approach: design rebuilt from scratch, engineering making incremental changes in code
    4:53 — Step-by-step walkthrough: how Shimaa used the existing codebase and AI tools to inform the new architecture
    7:29 — Systematizing what already exists: abstracting and naming tokens vs. inventing new ones
    8:10 — Avoiding breaking changes: the strategy of supporting the live state while layering in improvements
    9:29 — Finding the middle ground: honoring existing design before driving further evolution
    10:30 — Multiple versions vs. iterative: Guy's semantic versioning approach vs. smaller teams who can't maintain parallel systems
    13:30 — Taylor's poll: how few teams have actually had a formal, mandated migration period
    15:00 — A model for splitting system team responsibilities: dedicated evolution vs. embedded implementation support
    16:12 — Shimaa's experience at Square: rotation embeds and borrowing engineers between teams
    17:15 — Empathy building through team exchange programs: pros, cons, and the ambassador model
    18:22 — Standardization vs. innovation: is the design system the right place for innovation?
    19:34 — Reframing the idea: "the system enables product teams to innovate" and the danger of generic innovation mandates
    21:16 — Working with product teams: how to collaborate on patterns that are ready to be standardized
    22:13 — Closing thoughts and wrap-up

    ---

    Where to Find the Hosts
    Ben Callahan—Founder of Sparkbox and the Redwoods Design System Community. Individual and team coaching for design system programs. https://bencallahan.com

    Shimaa Hassan—Senior Product Designer at Remote, specializing in design systems. https://www.linkedin.com/in/shimaahassan/

    ---

    Get the Raw Data
    Access the complete survey data from Episode 069 to conduct your own analysis: https://bit.ly/46s0G9w

    ---

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

    ---

    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
    続きを読む 一部表示
    23 分
  • Episode 069 Deep Dive: Rebuilding a Design System Mid-Flight with Ben Callahan & Shimaa Hassan

    Episode 069 Deep Dive: Rebuilding a Design System Mid-Flight with Ben Callahan & Shimaa Hassan
    2026/03/02

    Episode 069 Deep Dive: Rebuilding a Design System Mid-Flight with Ben Callahan & Shimaa Hassan

    Introduction
    In episode 069 of *The Question*, host Ben Callahan (founder of Sparkbox and the Redwoods Design System Community) sits down with co-host Shimaa Hassan to tackle one of the most universal challenges in the space: rebuilding a design system while the products it supports are still in production.

    Ben surveyed 1,061 design system practitioners and received 53 responses across four questions: a 0–5 range question asking how often respondents think about throwing their system away and starting over, plus three open-text questions — (1) what's the one decision you'd make differently on day one, (2) how do you keep product teams confident in a system being rebuilt underneath them, and (3) share a story about rebuilding mid-flight. Key themes include token architecture, composability, governance, and the honest reality of how rarely formal migration mandates get enforced.

    ---

    Show Notes

    - **00:02** — Welcome and intro
    - **00:27** — Shimaa's background: from Alexandria, Egypt to design systems at Square and Remote
    - **02:28** — Shimaa's current challenge: rebuilding at Remote while the product ships continuously
    - **04:46** — Survey methodology and overview of the four questions
    - **05:43** — Question 1 results: roughly 50/50 split; Ben's sentiment analysis of the extremes
    - **08:48** — Question 2 highlights: token architecture, simplicity, composability, governance, leading with documentation
    - **10:09** — Erin on a cross-platform parity audit (iOS, Android, web) and handling breaking changes
    - **11:36** — Shimaa on balancing live product state with new system decisions
    - **12:37** — Guy on semantic versioning: one major release per year, advance communication, and a CLI tool that automated 70% of breaking change migrations
    - **14:34** — Taylor on SLAs, defining "breaking change" for your system vs. the org, mono repo vs. component-level versioning
    - **17:45** — Maintaining parallel systems: running old and new simultaneously
    - **18:53** — Peter references Kim Williams' Clarity talk on managing system transitions
    - **22:36** — How do you get teams to actually switch? Selling the value of migration
    - **26:26** — Shimaa's pro tip: run the codebase locally; use AI to audit token usage and map point-A-to-point-B
    - **29:16** — Guy on mandates that exist on paper but aren't enforced; lower org maturity can work in your favor
    - **31:41** — Taylor on the system as a place of stability; introducing an "additive threshold" for governance
    - **36:50** — Shimaa on triage logs tagged "approved / will not do / future"
    - **38:19** — Peter on adaptable (not rigid) infrastructure; wanting early involvement with consuming teams
    - **42:07** — Taylor's feature status Airtable for centralizing and communicating request progress
    - **45:46** — Shimaa introduces Norma Labs: a space for ideas not yet mature enough for the core system
    - **47:06** — Aaron on component-level versioning with 20 components needing updates simultaneously
    - **48:30** — Tallulah and Liz on capacity constraints; offering support windows to encourage faster migration
    - **50:45** — Liz on her IBM experience building testing infrastructure to keep React and Angular in parity
    - **52:31** — Peter's closing mantra: "Don't show me different, show me better"
    - **53:01** — Shimaa's closing reflection; Ben's announcements

    ---

    Resources Mentioned
    - **Kim Williams' Clarity Conference talk** on transitioning between design systems (https://designsystems.media/video/kim-williams-start-with-your-brand-purpose/)

    ---

    Where to Find the Hosts
    **Ben Callahan** — Founder of Sparkbox and Redwoods Design System Community; individual and team coaching for design system programs.
    https://bencallahan.com

    **Shimaa Hassan** — Senior Design System Designer at Remote
    https://bit.ly/46fGWGa

    ---

    Get the Raw Data
    Access the complete survey data from Episode 069 to conduct your own analysis:
    https://bit.ly/46s0G9w

    ---

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

    ---

    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
    続きを読む 一部表示
    55 分
  • Episode 068 Part II Deep Dive: Design Systems as AI Context with Ben Callahan and TJ Pitre

    Episode 068 Part II Deep Dive: Design Systems as AI Context with Ben Callahan and TJ Pitre
    2026/02/22

    Episode 068 Part II Deep Dive: Design Systems as AI Context with TJ Pitre
    Aired live: February 20, 2026

    Introduction
    In Part II of Episode 068, host Ben Callahan is joined again by co-host TJ Pitre—founder of Southleft, a front-end design development agency specializing in the intersection of AI and design systems—for a live community deep dive. This episode builds on Episode 068 Part I's exploration of the challenges that emerge when stochastic models try to keep the deterministic promises of a design system.

    This week the question turned practical: what work needs to happen behind the scenes so your design system can serve as powerful, reliable AI context? Ben and TJ sent the question to 1,031 design system practitioners and received 184 responses. The community came ready to share—from MCP servers as structured sources of truth, to agentic feedback loops that validate component output against documentation, to honest debate about where Storybook fits in an AI-native workflow.

    Show Notes
    00:00 — Welcome; Ben sets context for the Part II deep-dive format
    00:25 — TJ introduces Southleft and his team's focus on AI + design systems
    04:00 — Opening the question: where does your design system live as AI context?
    09:07 — Design System Assistant MCP vs. Claude Code-to-Figma: which is better for whom?
    10:02 — "Vibe coding" and the emerging pattern of going from code → Figma for UI refinement
    15:42 — Community discussion: single source of truth vs. federated systems
    15:56 — Eric Steinborn: their source of truth spans JS docs, JSON tokens, Figma, a reference site, and Storybook — and the consolidation effort underway
    19:57 — TJ's agentic feedback loop: docs → MCP → code generation → screenshot → validation → iteration
    22:56 — Ismail Hamila's AI audit agent: agnostic formats, skills, and checking correct variable intent (not just correct variable usage)
    31:18 — Orchestration layers, RAG, and vector databases as an alternative to forcing a single source of truth
    31:45 — Ismail's cautionary tale: burning $10 of tokens on a poorly-architected first agent run
    34:04 — FigJam spotlight: NY State team's pattern engine; Jennie Yip's design system as AI infrastructure diagram
    44:12 — Where does Storybook fit? TJ makes the case for Storybook MCP (via Chromatic) depending on your team
    45:35 — Jennie Yip: how packaging everything into an MCP server eliminated AI hallucination
    48:04 — Kevin Muldoon in chat: "The blueprint is not derived from the building. Authority flows from origin, not from output."
    50:46 — Wrap-up and gratitude for FigJam participation
    54:04 — Ben's closing: raw data, FigJam, and coaching resources at https://bencallahan.com

    Where to Find the Hosts
    Ben Callahan is the founder of Sparkbox (https://sparkbox.com) and the Redwoods Design System Community (bencallahan.com/redwoods), and host of The Question (https://bencallahan.com/the-question). Find him on LinkedIn (https://bit.ly/3T6rd5S).

    TJ Pitre is the founder of Southleft (https://southleft.com/). Find TJ on LinkedIn (https://bit.ly/4rsXOBf).

    Get the Raw Data
    Access the survey data for this episode here: https://bit.ly/4apfR5v

    Review the FigJam Notes
    Community notes from the deep dive: https://bit.ly/4c9cvFp

    Join the Conversation
    Subscribe to The Question and join the Redwoods community at https://bencallahan.com/thequestion.
    続きを読む 一部表示
    55 分
まだレビューはありません