エピソード

  • 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 分
  • Episode 68 Deep Dive: Design Systems as AI Context with Ben Callahan & TJ Pitre

    Episode 68 Deep Dive: Design Systems as AI Context with Ben Callahan & TJ Pitre
    2026/02/16

    Episode 068 Recap: Design Systems as AI Context with Ben Callahan & TJ Pitre


    Introduction

    Welcome to The Question Episode 068 Recap. In this episode, Ben Callahan and co-host TJ Pitre facilitate a deep dive into one of the most pressing topics in the design system space today: Are our design systems ready to serve as reliable AI context?

    Ben sent a three-question survey to 1,031 design system practitioners and received 148 responses. The questions explored:

    1. How prepared design systems are to act as reliable AI context
    2. Whether teams are experimenting with AI-generated UI
    3. How practitioners feel about the output—or what’s holding them back

    What followed was a nuanced, honest conversation about infrastructure, documentation, design-to-dev parity, and the emotional tension many practitioners feel in this moment.


    Show Notes

    00:00 – Introduction & Topic Framing
    Design systems as AI context and acknowledging the tension around AI.

    06:38 – Survey Overview & Readiness Data
    Why most teams feel underprepared—and why that matters.

    11:51 – Experimentation vs. Confidence
    Many are testing AI even if they don’t feel ready.

    13:17 – What Does “AI Readiness” Actually Mean?
    The gap between perceived readiness and actual infrastructure maturity.

    14:14 – Figma as Canonical Source of Truth
    How context cascades from design to development—and where it breaks.

    16:11 – The Figma Bridge Experiment
    Using APIs to extract component specs and generate code with AI.

    17:05 – Discovering the Cracks
    Detached components, hard-coded values, missing properties, and hidden inconsistencies.

    20:18 – “Infrastructure Wins Over Prompting”
    Why better prompting isn’t the answer—better system architecture is.

    22:30 – Beyond Visual Fidelity
    Metadata, ARIA labels, intent, and behavior as critical AI context.

    24:44 – Documentation Drift & Context Sprawl
    AI can’t distinguish outdated documentation without human governance.

    29:25 – Design-to-Dev Parity Workflows
    Using tooling to compare canonical sources and surface deviations automatically.

    32:57 – AI as Passenger, Not Driver

    Key Themes

    1. Infrastructure > Prompting

    The quality of AI output is directly tied to the integrity of your system. If your components are inconsistent, disconnected, or poorly documented, AI will expose those cracks—not fix them.

    2. Context is the New Prompt

    2024 was about prompts. 2025 is about context. Systems that encode intent, behavior, accessibility, and relationships between components will outperform purely visual libraries.

    3. AI Reveals Design Debt

    Detached components, missing properties, undocumented variants—AI makes hidden system debt visible.

    4. Documentation Is a Living System

    Outdated Confluence pages and static decks become liabilities when surfaced through LLMs. Human oversight and governance remain essential.

    5. AI Should Be Embedded in Workflow

    Not “set it and forget it.” Involve AI throughout design, parity checks, and documentation—not just at the end.


    Where to Find the Hosts

    TJ Pitre: Founder of Southleft and working at the intersection of design systems and AI.
    https://southleft.com/

    Ben Callahan: Host of The Question, Founder of Redwoods Design System Community and Founder of Sparkbox.
    https://bencallahan.com
    https://sparkbox.com

    Get the Raw Data

    Access the complete survey data from Episode 068 to conduct your own analysis: https://bit.ly/4apfR5v

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


    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 68 Recap: Design Systems as AI Context with Ben Callahan & TJ Pitre

    Episode 68 Recap: Design Systems as AI Context with Ben Callahan & TJ Pitre
    2026/02/16

    Episode 068 Recap: Design Systems as AI Context with Ben Callahan & TJ Pitre

    Introduction
    Welcome to The Question Episode 068 Recap. In this episode, Ben Callahan sits down with TJ Pitre—founder of South Left studio—to unpack the results from this week's survey on design systems as AI context.

    Ben sent the three-question survey to 1,031 design system practitioners and received a record 148 responses. The questions explored how prepared design systems are to act as reliable AI context today, whether practitioners have experimented with AI-generated UI from their design systems, and how they feel about the output (or what's keeping them from trying). The conversation that follows is a recap of the deep dive into the emerging relationship between design systems and AI, revealing why infrastructure and context quality matter more than clever prompts when it comes to AI-assisted workflows.

    ---

    Show Notes

    00:00 - Introduction & Welcome
    02:10 - Survey Overview & The Emotional Landscape of AI
    03:27 - The Three Survey Questions
    04:41 - Perception vs. Reality of AI Readiness
    06:34 - Detached Components and Hidden Cracks
    08:40 - AI Slop as a Signal for System Quality
    09:32 - Can AI Eventually Infer Intent Without Clean Context?
    11:09 - The Case for Human Involvement and Original Thought
    13:31 - Compounding Slop: When AI Builds on Its Own Mistakes
    14:28 - Context Engineering vs. Vibe Coding
    15:06 - Evals: Having Your AI Check Your AI
    17:48 - The Russian Doll Method: Building Systems Atomically
    20:04 - Human Oversight in the AI Workflow Loop
    20:44 - Infrastructure Wins Over Prompting
    22:37 - Tools: Serena MCP and Sequential Thinking
    23:56 - Closing Advice: Stay Curious, Start Small
    25:42 - Getting Started: Claude Chat + Figma MCP
    27:37 - The Most Impactful Change: Run Diagnostics on Your System
    29:29 - Closing Reflections & What's Next

    ---

    Resources Mentioned
    - TJ's AI and Design Systems course: (https://https://aianddesign.systems//)
    - Serena MCP: https://github.com/oraios/serena
    - Sequential Thinking MCP: https://github.com/modelcontextprotocol/servers/tree/main/src/sequentialthinking

    Where to Find the Hosts
    **TJ Pitre**: Founder of South Left, creator of Figma Console MCP, and educator on AI and design systems. Known for bridging the gap between design systems infrastructure and AI-powered workflows. (https://southleft.com/)
    **Ben Callahan**: Host of The Question, Founder of Redwoods Design System Community and Founder of Sparkbox. (https://bencallahan.com, https://sparkbox.com)

    Get the Raw Data
    Access the complete survey data from Episode 068 to conduct your own analysis (https://bit.ly/4apfR5v)

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

    Join the Conversation
    The Question explores design systems topics through community research and deep-dive discussions. Visit the show website to participate in future episodes and join the conversation. (https://bit.ly/answerTheQuestion)
    続きを読む 一部表示
    30 分
  • Full: Episode 067 of The Question with Ben Callahan & Yesenia Perez-Cruz on Design Systems that Differentiate

    Full: Episode 067 of The Question with Ben Callahan & Yesenia Perez-Cruz on Design Systems that Differentiate
    2026/02/01
    Episode 067 Deep Dive: Design Systems That DifferentiateIntroductionWelcome to The Question Episode 067 Deep Dive. Host Ben Callahan is joined by Yesenia Perez-Cruz—author of Expressive Design Systems and former design systems leader at Vox Media and Shopify—for an interactive conversation about design systems that differentiate. This session brings together dozens of design systems practitioners to discuss the tension between sameness and differentiation in our consuming products.Ben surveyed 1,027 design system practitioners and received 55 responses exploring three key questions: Where does sameness emerge in products? What's your system's primary goal (efficiency, cohesion, or differentiation)? And what bottleneck most restricts product expression? The conversation reveals the cultural, architectural, and philosophical challenges of building systems that both accelerate and differentiate—featuring perspectives from teams across the world.Show Notes00:00 - Welcome & Yesenia's BackgroundBen welcomes participants and introduces Yesenia Perez-Cruz as co-hostYesenia's journey: Started with graphic design education (primarily print, some early Dreamweaver)First job at Happy Cog agency doing responsive websitesEarly realization: Need to make decisions systematically (not 10 different header styles)2011: First article on design systems (describing systematic decision-making process)Agency work delivering "style guides" to clients, early theming workJose Garces restaurants project: Six distinct restaurant brands requiring systematic brand expressionVox Media: Led design system for eight distinct editorial brands moving to centralized teamShopify/Polaris: Led system that had good adoption but noticed sameness creeping in Point of sale team adopted admin system—felt too similarMobile team had same issueFocus: How to get diverse expression within huge platformSix years at Shopify, now doing independent design work and consulting03:14 - The Expression Lens: A Different Approach to SystemsMost practitioners enter systems looking for consistencyYesenia's unique lens: Systems can empower/enable expressionConsistency is good to an extent, but that extent is often exaggeratedClear inconsistencies can break trust (example: phishing email from your bank)But consistency can delve into a space where "it's not good anymore"The problem: Design solutions aren't actually communicating information when content is flattenedMany challenges stem from pushing too hard toward consistency04:40 - Survey Results OverviewQuestion 1: Where do you notice sameness emerging? Overall layout and page structureVisual hierarchy and emphasisInteraction patterns and behaviorsBrand expression and personality"I don't notice meaningful sameness"Results: Fairly even distribution (30-50% each)Very few people (5-6) said they don't notice samenessFollow-up question posted: For those who don't notice sameness, what's unique about your architecture or processes?Question 2: Primary goal of your system? About half: Operational efficiencyOthers: Brand cohesionSmaller group: Product differentiationObservation: Most teams want both efficiency AND cohesionForcing choice to primary goal revealed interesting tensionsQuestion 3: Open-ended responses about bottlenecks Component flexibilityToken structuresDocumentation (big theme)Decision paralysis (surprising theme)09:24 - Decision Paralysis and Designer SafetyKey insight: Best design work happens when designers are relaxed, having fun, in flow stateWhen you don't know the bounds you can work within, you tense up"Can I put this line here? Can I use this color background? Will I get in trouble?"Result: Retreat to what feels safe—copying what's already approvedLack of clarity about permissions takes away the safety of designNot about sacrificing brand expression for consistency—need to solve this tensionKnowing the bounds enables creative problem-solving with the design language12:13 - Stephen: AI and Design Systems ParallelWorking with AI recently reveals similar challengesAI "does whatever it can to not follow the rules"Explores areas where documentation doesn't quite forbid somethingSame question: Where are proper constraints vs. room for creative exploration?How do companies prioritize tasks for AI (needing explicit boundaries) vs. humans?Yesenia's response: Design language as a tool for creative freedom can be liberatingHumans have judgment to assess "is this working well?" that AI currently lacksNeed to meet both ends of the spectrum14:09 - Kaelig's Comment: "Everything Looking the Same Is Good"Chat comment challenges fundamental assumptionYesenia's response: There are phases to design systems Typically start wanting convergence—reducing too much variationThis is absolutely validThe problem: How to get convergence without getting stuck in placeFive years ago problem: If you created a system 5 years ago, you're converging on how the product existed thenNeed ability to move from ...
    続きを読む 一部表示
    50 分
  • Recap: Episode 067 of The Question with Ben Callahan & Yesenia Perez-Cruz on Design Systems that Differentiate

    Recap: Episode 067 of The Question with Ben Callahan & Yesenia Perez-Cruz on Design Systems that Differentiate
    2026/02/01
    Episode 067 Recap: Design Systems That Differentiate with Ben Callahan and Yesenia Perez-CruzIntroductionWelcome to The Question Episode 067 Recap. In this episode, Ben Callahan sits down with Yesenia Perez-Cruz—author of Expressive Design Systems and design system consultant, to unpack the results from this week's survey on design systems that differentiate.Ben sent the three-question survey to 1,027 design system practitioners and received 55 responses. The questions explored where sameness emerges in products, what design system teams prioritize as their primary system goal (operational efficiency vs. brand cohesion vs. product differentiation), and what aspect of their design system acts as the biggest bottleneck to product expression. The conversation that follows is a recap of the deep dive into the tension between standardization and innovation, revealing frameworks and strategies for creating design systems that both accelerate and differentiate.---Show Notes00:00 - Introduction & Survey OverviewBen welcomes Yesenia Perez-Cruz as co-host for the Episode 067 recapContext: Just finished deep dive with participants reviewing raw dataSurvey details: 1,027 practitioners contacted, 55 responses receivedThree questions explored: where sameness emerges, primary system goals, and bottlenecks to expressionFirst question results were evenly split across categories (30-50% for each option)02:27 - Defining Sameness, Differentiation, and ExpressionParticipants immediately questioned: "Don't we want sameness?Expression defined: Does the interface look like the thing users are doing? Do visual cues communicate content meaning (shipping profiles, order lists, etc.)?Sameness defined: When the shape of components overrides the content—everything looks like generic headers, lists, and footersThe key distinction: Good expression means content emerges rather than being hidden by component structureExpression is really just good visual communication and design04:42 - Did Design Systems Create Sameness?Historical context: Brett Victor's "Magic Ink" article from 2005 identified this problem before design systems existedVictor argued product designers aligned with industrial design (mechanical tools) vs. graphic design (information shaping)He cited "ancestors of design systems" as contributors to samenessConclusion: Design systems aren't the only cause, but are "the cost of economies of efficiency"The problem predates design systems but has been accelerated by them06:50 - Drift vs. Differentiation: Critical DistinctionsDrift: When things that are the same look different (unintentional inconsistency)Example: Delete actions using different icons (X vs. trash can)Users shouldn't have to relearn patterns for the same actionDifferentiation: When things that are different look appropriately differentThings should look like what they are, not all the sameSameness: The opposite of drift—when things that are different look the sameDifferentiation serves both interface clarity AND market positioning08:10 - Brand Differentiation Through Primitive ComponentsTwo meanings of differentiation: interface clarity and market positioningMyMind example: Bookmarking tool with atmospheric, circular brandingReimagined drop zone with circular shapes and soothing animationsStandard components (drop zone, color picker) styled to brand essenceMany teams start by referencing other design systems or galleriesKey insight: For core parts of your experience, create distinct patterns that feel specific to your product10:37 - Balancing Usability and ExpressionThe usability concern: Familiarity breeds instinctual understandingJacob's Law: Users prefer patterns they're familiar with from other sitesThe nuance: There's space for differentiation in domain-specific componentsWhen components are specific to your domain (not just functional), users are more willing to learn something differentThe line between standardization and innovation isn't the same for every organization12:22 - How to Decide Where to Standardize vs. InnovateFirst: Understand the role the system plays in your organizationAre you in efficiency mode or innovation mode?This can ebb and flow within the same companySecond: Understand who needs to create expression and whereExample: Polaris serves both third-party developers (who want decisions made) and internal designers (creating new products)Different audiences within the same organization may need different approachesThe person making the choice matters as much as what the choice is14:35 - Enablement, Safety, and ExperimentationDesign systems shape the culture of how designers workThe trust paradox: Sometimes teams trust the system too muchYesenia's experience: Encouraging teams to "start with a blank canvas"Goal was to encourage feedback loops of new patterns into the systemCreating psychological safety for designers to explore outside constraintsHow the system team responds to requests shapes whether people feel safe to experiment17...
    続きを読む 一部表示
    26 分
  • Full: Episode 066 of The Question with Ben Callahan & Laura Kalbag on The Design System Learning Curve

    Full: Episode 066 of The Question with Ben Callahan & Laura Kalbag on The Design System Learning Curve
    2026/01/18
    The Question Episode 066: The Design System Learning Curve with Ben Callahan & Laura KalbagBen and Laura lead the community through a conversation about how people learn design systems, revealing that 75% feel qualified despite most being self-taught. The discussion explores whether the field needs W3C-style industry standards, with answers nearly evenly split between yes, no, and other. Community members share insights on multidisciplinary backgrounds, the value of peers and mentorship, the challenge of articulating shared problems and values across organizations, and the tension between standardization and meeting teams where they are.Introduction to Design Systems (00:00)- Welcome and overview of the episode topic- Ben introduces Laura Kalbag as co-host- Laura's background as designer-developer with accessibility expertise- Early adoption of design systems (writing about them since 2012)- Current work with Penpot on educational materials- Book: Accessibility for Everyone (going free online with audiobook)Exploring the Design System Learning Curve (00:00)- How The Question works: survey format and community participation- 77 responses from 1,025 practitioners- Four key questions about learning and industry standards- First question results: Do you feel qualified? (75% yes, 17% no, 8% other)- Themes: constant references to peers, mentorship, and multidisciplinary backgrounds- Standards question showing nearly even split (yes/no/other)Engaging with the Community: Collaborative Learning (05:16)- Laura's opening question: Where would you tell a new designer to start?- Christine: Point to thought leaders (Brad Frost, Dan Mall, Jina Anne, Nathan Curtis)- Recommendation to work in product/UX roles first before systems- Importance of systems thinking - looking at things holistically- Ismael: Value of product management skills and understanding users- Learning HTML/CSS fundamentals, semantic structure, and inheritance- Laura: HTML as accessible starting point for newcomersMentorship and Guidance in Design Systems (08:57)- Greg: "The people who see systems are the ones who make them"- Systems thinking as natural progression for some practitioners- Learning from industry leaders but adapting to your specific context- Disclaimer needed: what works for IBM or Spotify may not work for you- Guy: Ask "why" someone wants to get into design systems first- Understanding the process, not just copying outputs- Risk of burnout from always seeing systems and implications- Danger of over-codifying and creating restrictive structuresUnderstanding Your Motivation for Design Systems (17:52)- Different aspects: code, coordination, fame, specific challenges- Tailoring guidance based on individual motivations and goals- Jeremy Keith quote: Design system doc sites are like social media (only show the good)The Unique Nature of Your Design System (18:21)- Austin: Working at Bass Pro Shops vs. big tech companies- Challenge of resources not fitting organizational context- Greg: "Be happy you don't have their problems"- Looking at intricate systems born from problems you don't have- Blessing of not needing those complex solutions- Focus on the problems that are unique to your usersEmbedding Values in Design Systems (20:12)- Laura: We embed our values in the design systems we create- Risk of copying big tech values that don't align with your mission- Small Technology Foundation example: creating alternatives to big tech- Question: Are you taking on values that don't represent your product?Imposter Syndrome in Design Systems (21:08)- Greg: First time experiencing true imposter syndrome in nearly two decades- Reading industry masters and feeling inadequate- Redwoods community response: appreciate not having their problems- Shift in perspective about own work in the space- Focus on what you can do that's more interesting for your usersIdentifying Gaps in Design System Learning (24:44)- Christine: Communication between teams as huge blind spot- Building systems with one product in mind defeats the purpose- Style guides vs. true systems serving multiple products- Need for people at all skill levels to share their learning- Missing links in the learning chain- Everyone has responsibility to share what they're learningThe Importance of Change Management (26:34)- Yesenia: Change management as biggest success or failure factor- Getting people to change what they're doing- Adapting communication to organizational context- Relationship-driven vs. storytelling-driven organizations- Mismatch in communication styles leads to failure- Book recommendation: Switch by Chip and Dan Heath- Not trained in change management but must do it anywayThe People Side of Design Systems (29:32)- Little focus on people side in survey responses- Austin's revelation: "This is about people" shifted everything- Meet people where they're at instead of holding meetings no one attends- Attend their standups and see how design system can help- Laura: Tooling companies ...
    続きを読む 一部表示
    55 分