
Sign up to save your podcasts
Or


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)
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
03:14 - The Expression Lens: A Different Approach to Systems
04:40 - Survey Results Overview
09:24 - Decision Paralysis and Designer Safety
12:13 - Stephen: AI and Design Systems Parallel
14:09 - Kaelig's Comment: "Everything Looking the Same Is Good"
16:33 - Matt (New York Times): Typography, Culture, and Letting Go
17:44 - Layers: Tokens, Components, Composition
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
02:27 - Defining Sameness, Differentiation, and Expression
04:42 - Did Design Systems Create Sameness?
06:50 - Drift vs. Differentiation: Critical Distinctions
08:10 - Brand Differentiation Through Primitive Components
10:37 - Balancing Usability and Expression
12:22 - How to Decide Where to Standardize vs. Innovate
14:35 - Enablement, Safety, and Experimentation
17:27 - The Blank Canvas Approach
19:10 - Seasons of Innovation and Standardization
20:42 - Trust, Responsibility, and Where to Draw the Line
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)
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
From the publisher's feed