The Question: Design System Collaborative Learning

The Question: Design System Collaborative Learning

By Ben CallahanTechnology
Download on the App Store

The Question: Design System Collaborative Learning episodes

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

    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)

    31 min
  • Full: Episode 067 of The Question with Ben Callahan & Yesenia Perez-Cruz on Design Systems that Differentiate

    Episode 067 Deep Dive: Design Systems That Differentiate

    Introduction

    Welcome 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 Notes

    00:00 - Welcome & Yesenia's Background

    • Ben welcomes participants and introduces Yesenia Perez-Cruz as co-host
    • Yesenia's journey: Started with graphic design education (primarily print, some early Dreamweaver)
    • First job at Happy Cog agency doing responsive websites
    • Early 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 work
    • Jose Garces restaurants project: Six distinct restaurant brands requiring systematic brand expression
    • Vox Media: Led design system for eight distinct editorial brands moving to centralized team
    • Shopify/Polaris: Led system that had good adoption but noticed sameness creeping in 
      • Point of sale team adopted admin system—felt too similar
      • Mobile team had same issue
      • Focus: How to get diverse expression within huge platform
    • Six years at Shopify, now doing independent design work and consulting

    03:14 - The Expression Lens: A Different Approach to Systems

    • Most practitioners enter systems looking for consistency
    • Yesenia's unique lens: Systems can empower/enable expression
    • Consistency is good to an extent, but that extent is often exaggerated
    • Clear 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 flattened
    • Many challenges stem from pushing too hard toward consistency

    04:40 - Survey Results Overview

    • Question 1: Where do you notice sameness emerging? 
      • Overall layout and page structure
      • Visual hierarchy and emphasis
      • Interaction patterns and behaviors
      • Brand 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 sameness
    • Follow-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 efficiency
      • Others: Brand cohesion
      • Smaller group: Product differentiation
      • Observation: Most teams want both efficiency AND cohesion
      • Forcing choice to primary goal revealed interesting tensions
    • Question 3: Open-ended responses about bottlenecks 
      • Component flexibility
      • Token structures
      • Documentation (big theme)
      • Decision paralysis (surprising theme)

    09:24 - Decision Paralysis and Designer Safety

    • Key insight: Best design work happens when designers are relaxed, having fun, in flow state
    • When 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 approved
    • Lack of clarity about permissions takes away the safety of design
    • Not about sacrificing brand expression for consistency—need to solve this tension
    • Knowing the bounds enables creative problem-solving with the design language

    12:13 - Stephen: AI and Design Systems Parallel

    • Working with AI recently reveals similar challenges
    • AI "does whatever it can to not follow the rules"
    • Explores areas where documentation doesn't quite forbid something
    • Same 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 liberating
    • Humans have judgment to assess "is this working well?" that AI currently lacks
    • Need to meet both ends of the spectrum

    14:09 - Kaelig's Comment: "Everything Looking the Same Is Good"

    • Chat comment challenges fundamental assumption
    • Yesenia's response: There are phases to design systems 
      • Typically start wanting convergence—reducing too much variation
      • This is absolutely valid
      • The problem: How to get convergence without getting stuck in place
    • Five years ago problem: If you created a system 5 years ago, you're converging on how the product existed then
    • Need ability to move from there
    • Expression clarification: Doesn't necessarily mean brand personality 
      • Core question: Does the thing you're using look like the action you're taking?
      • Mac example: Control Center (big affordances for quick actions) vs. System Settings (tiny controls, explanatory text)
      • Spectrum of UI tailored for specific tasks
    • Expression is about appropriateness to context and content

    16:33 - Matt (New York Times): Typography, Culture, and Letting Go

    • NYT designers are very particular about typography
    • Previous systems were strict: "text-small, text-medium, text-large"
    • Stakeholder requests: "I want 15 [pixels]"
    • Matt's evolution: Trying to let go of rigid rules
    • Opportunity: When you let go, the culture of the design org can come out
    • Tension: Also creates room for chaos
    • Question: How do you give up design system control and give control to customers?
    • How do teams manage based on org culture?

    17:44 - Layers: Tokens, Components, Composition

    • Yesenia's framework: Push as far as possible at compositional layer before changing token layer
    • Can do something more powerful at composition than at token level
    • Promo card example: 
      • Team wants new color token for "promo"
      • Yesenia pushes back: What's more powerful to indicate promotion?
      • Uber Eats reference: Promo card looks like actual coupon—different z-index, inset notches
      • Much stronger visual representation
    • Decision criteria: Pus...
    51 min
  • Recap: Episode 067 of The Question with Ben Callahan & Yesenia Perez-Cruz on Design Systems that Differentiate

    Episode 067 Recap: Design Systems That Differentiate with Ben Callahan and Yesenia Perez-Cruz


    Introduction


    Welcome 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 Notes


    00:00 - Introduction & Survey Overview

    • Ben welcomes Yesenia Perez-Cruz as co-host for the Episode 067 recap
    • Context: Just finished deep dive with participants reviewing raw data
    • Survey details: 1,027 practitioners contacted, 55 responses received
    • Three questions explored: where sameness emerges, primary system goals, and bottlenecks to expression
    • First question results were evenly split across categories (30-50% for each option)


    02:27 - Defining Sameness, Differentiation, and Expression

    • Participants 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 footers
    • The key distinction: Good expression means content emerges rather than being hidden by component structure
    • Expression is really just good visual communication and design


    04:42 - Did Design Systems Create Sameness?

    • Historical context: Brett Victor's "Magic Ink" article from 2005 identified this problem before design systems existed
    • Victor argued product designers aligned with industrial design (mechanical tools) vs. graphic design (information shaping)
    • He cited "ancestors of design systems" as contributors to sameness
    • Conclusion: 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 them


    06:50 - Drift vs. Differentiation: Critical Distinctions

    • Drift: 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 action
    • Differentiation: When things that are different look appropriately different
      • Things should look like what they are, not all the same
    • Sameness: The opposite of drift—when things that are different look the same
    • Differentiation serves both interface clarity AND market positioning


    08:10 - Brand Differentiation Through Primitive Components

    • Two meanings of differentiation: interface clarity and market positioning
    • MyMind example: Bookmarking tool with atmospheric, circular branding
      • Reimagined drop zone with circular shapes and soothing animations
      • Standard components (drop zone, color picker) styled to brand essence
    • Many teams start by referencing other design systems or galleries
    • Key insight: For core parts of your experience, create distinct patterns that feel specific to your product


    10:37 - Balancing Usability and Expression

    • The usability concern: Familiarity breeds instinctual understanding
    • Jacob's Law: Users prefer patterns they're familiar with from other sites
    • The nuance: There's space for differentiation in domain-specific components
    • When components are specific to your domain (not just functional), users are more willing to learn something different
    • The line between standardization and innovation isn't the same for every organization


    12:22 - How to Decide Where to Standardize vs. Innovate

    • First: Understand the role the system plays in your organization
      • Are you in efficiency mode or innovation mode?
      • This can ebb and flow within the same company
    • Second: Understand who needs to create expression and where
      • Example: 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 approaches
    • The person making the choice matters as much as what the choice is


    14:35 - Enablement, Safety, and Experimentation

    • Design systems shape the culture of how designers work
    • The trust paradox: Sometimes teams trust the system too much
    • Yesenia's experience: Encouraging teams to "start with a blank canvas"
    • Goal was to encourage feedback loops of new patterns into the system
    • Creating psychological safety for designers to explore outside constraints
    • How the system team responds to requests shapes whether people feel safe to experiment


    17:27 - The Blank Canvas Approach

    • The risk: Standardizing too much, too early
    • Yesenia's system worked well for building 2016's product, but not for 2020's needs
    • Strategy: Encourage divergence first, then converge on new patterns
    • Can't standardize things that don't exist yet
    • Teams sometimes jump to defining palettes and typography before understanding the product
    • Creative exploration should continue throughout the adoption process, not just at the beginning


    19:10 - Seasons of Innovation and Standardization

    • Organizations pendulum between differentiation/innovation and standardization
    • Both don't run full steam simultaneously—it's a seasonal shift
    • External factors impact business needs, which impact design approach, which impacts what gets standardized
    • Example timeline: Knew token layer wasn't ready, encouraged divergence to learn what needed standardizing, then created new token architecture and consolidated
    • This required thinking 3+ years in advance
    • Design systems practitioners must predict the future (another skill to add to the matrix!)


    20:42 - Trust, Responsibility, and Where to Draw the Line

    • One participant's perspective: "I don't tell designers what to do, I trust they know their craft"
    • The challenge: What does trust mean for design debt and tech debt?
    • It's difficult for system practitioners to block product designers' work
    • Pro...
    27 min
  • Full: Episode 066 of The Question with Ben Callahan & Laura Kalbag on The Design System Learning Curve

    The Question Episode 066: The Design System Learning Curve with Ben Callahan & Laura Kalbag

    Ben 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 newcomers

    Mentorship 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 structures

    Understanding 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 users

    Embedding 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 users

    Identifying 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 learning

    The 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 anyway

    The 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 dependent on sharp folks doing cultural work
    - Standards should be about processes for creating systems, not systems themselves

    Education and Management in Design Systems (32:21)
    - Austin: Reaching out on LinkedIn begging for mentorship conversations
    - Learning about program/product manager role for design systems
    - Convincing organizations to commit to necessary roles
    - Taylor's meta observation: We're at a maturation point in the field
    - Early ICs now moving into director/manager/lead roles
    - Phase two of design systems establishment
    - Built-in layers of experience we didn't have years ago

    The Evolution of Design Systems (36:07)
    - Taylor: Roles and understanding have changed in the ecosystem
    - Learning paths for different roles (designer to system designer, etc.)
    - Need for curated resources with markers in time
    - Annotating when content becomes outdated
    - Community-led approaches vs. top-down certification
    - Standards question discussion: W3C-style standards or community curation?
    - Stephen: Focus on articulating shared problems and values across organizations
    - Greg: Extending HTML patterns and elevating emerging needs
    - Component galleries focused on user problems and solutions
    - Open source templates for education (tokens, variables, theming)
    - Meeting teams where they are vs. pushing standards
    - Gratitude for community participation and thoughtful answers

    Resources
    - Recap of Episode 055 with Lauren LoPrete on Managing your Systems Brain (https://bit.ly/3HTh89a)
    - To Be a Leader of Systems by Hazel Weakly (https://hazelweakly.me/blog/to-be-a-leader-of-systems/)
    - Ben on LinkedIn (https://bit.ly/3T6rd5S)
    - Laura on LinkedIn (https://bit.ly/4hI9g8v)
    - Get The Question in your Inbox (https://bit.ly/3U1hdf3)
    - Redwoods Design System Community (https://bit.ly/44lzHL5)

    55 min
  • Recap: Episode 066 of The Question with Ben Callahan & Laura Kalbag on The Design System Learning Curve

    Episode 66 Recap: The Design System Learning Curve with Ben Callahan and Laura Kalbag

    Ben and Laura unpack the episode 066 deep dive conversation on how people learn design systems, exploring why imposter syndrome is so prevalent in this space, the challenges of being self-taught in a field with no formal education path, and how the community might create better learning resources and pathways for newcomers.

    Topics
    Imposter syndrome and qualification (00:00-06:12)
    - Do people feel qualified as design system specialists?
    - Connection between self-taught learning and lack of confidence
    - Systems thinkers: "The people who see systems are the ones who make them"

    Learning paths and skills development (06:12-09:00)
    - How practitioners learned: scrappy, experimental, self-taught
    - Value of working in other roles first (product design, development, product management)
    - Design systems as increasingly broad field requiring specialization

    Systems thinking benefits and challenges (07:23-09:00)
    - Risk of burnout from always seeing systems
    - Danger of over-codifying and creating restrictive structures
    - Managing your systems brain

    Community learning and resources (16:39-20:52)
    - Challenge of finding good information amid AI-generated content
    - Value of human connection and community curation
    - Potential for gathering trusted resources rather than top-down standards

    Academic vs. practical preparation (16:39-18:28)
    - Gap between art school confidence and professional readiness
    - Sparkbox's apprenticeship program: paid 6-month positions to bridge the gap
    - Creating materials for professional practice, not just theory

    AI's impact on learning and entry positions (18:28-19:54)
    - Difficulty finding trustworthy information
    - Machines talking to machines with no human wisdom
    - Entry-level positions being impacted

    The unique moment we're in (21:46-22:34)
    - Early design system practitioners now in leadership roles
    - Potential for more fertile soil with leaders who understand the work
    - Question: how do we build the pipeline?

    Standardization and community resources (21:04-21:46)
    - Building on existing HTML patterns
    - Brad Frost's global design system concept
    - Component galleries and shared understanding

    Resources
    - Recap of Episode 055 with Lauren LoPrete on Managing your Systems Brain
    - To Be a Leader of Systems by Hazel Weakly
    - Ben on LinkedIn
    - Laura on LinkedIn
    - Get The Question in your Inbox
    - Redwoods Design System Community

    24 min

About The Question: Design System Collaborative Learning

From the publisher's feed

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!