The Question: Design System Collaborative Learning

Episode 079 Recap: The Evolution of Design System Documentation with Ben Callahan and Afyia SmithBen Callahan and Afyia Smith, a content designer and technical writer specializing in design systems, recap what the community said about who owns documentation and where docs are headed now that machines are reading them too.The survey went to more than 1,100 design system practitioners and drew 61 responses across five questions. The conversation covers the shift from prose to structured content, the case for a dedicated documentation owner, the design system knowledge architect role, the DSDS spec work with PJ Onori, and the fourteen respondents who said machines will be the only future readers of their docs.Show Notes00:00 — Welcome and introductions00:14 — Black-and-white prints and a giraffe collection01:00 — Almost 80 episodes, and the first one on docs01:24 — Survey setup: 1,100 practitioners, 61 responses02:34 — Afyia answers the open-ended question herself02:41 — Documentation as a knowledge layer, not just content03:20 — Focused ownership and just-in-time documentation04:08 — What docs looked like in the early design system days04:30 — Bare, scattered, outdated, ungoverned06:17 — The case for a point person07:53 — The design system knowledge architect role08:20 — Coming back a year later to the same mess11:03 — Question one results: who owns documentation11:57 — By design or by default?12:24 — Digging into the 30% who answered "other"13:36 — Question two: everyone figuring agentic workflows out alone14:24 — The correlation that wasn't in the data15:00 — Question three: reporting on agentic workflow success16:07 — Ownership reveals visibility more than success17:00 — Machine readable versus machine parsable17:20 — Surface-level changes versus foundational ones17:49 — Bad docs surfaced everywhere are still bad docs18:49 — Working upstream of AI19:38 — The component schema work with PJ Onori20:45 — DSDS, doc origin, and metadata as a trust layer23:32 — Question five: writing for humans, machines, or both24:48 — What we would lose without human-readable reference sites26:48 — Why documentation has always been the passionWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bencallahan.com/redwoods). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comAfyia Smith is a content designer and technical writer focused on design system documentation, governance, and knowledge architecture. Connect with her: https://bit.ly/4vVUhNPGet the Raw DataAccess the complete survey data from Episode 079 to conduct your own analysis: https://bit.ly/4yV4JrDReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4gismBZJoin the ConversationThe 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/answerTheQuestionMusic licensed through Soundstripe.Code: C1COHEMFO6L4XE0H

Episode 079 Deep Dive: The Evolution of Design System Documentation with Ben Callahan and Afyia SmithBen Callahan is joined by Afyia Smith, a content designer and technical writer who spent five years as a documentation specialist on the design system team at Epic Games, built AI readiness frameworks and governance models there, and now collaborates with PJ Onori on the DSDS documentation spec. Together with the community, they dig into who owns design system documentation and what changes when agents start reading it.The survey went to more than 1,100 design system practitioners and drew 61 responses across five questions. The conversation covers machine readable versus machine parsable formats, recipes and gotchas files, decision trees for agents, the split between reference and guidance documentation, just-in-time docs, and whether AI should be writing documentation at all.Show Notes 00:07 — Welcome to the Episode 079 deep dive 00:40 — Afyia's path into design system documentation 02:25 — Five years as a documentation specialist at Epic Games 03:50 — Emailing PJ Onori to contribute to DSDS 06:21 — This week's five questions, 1,100 sent, 61 responses 09:18 — Breaking down the responses that chose "other" 10:15 — Everyone figuring agentic workflows out on their own 11:04 — Looking for a correlation that isn't there 12:56 — Robin Di Capua on encoding compositional do's and don'ts 14:24 — Patterns, templates, and recipes in the DSDS spec 18:08 — Doug Neiner on recipes and gotchas files 19:16 — Kelby Gassman on docs turning into decision trees 23:52 — Kevin Coyle on machine readable versus machine parsable 26:09 — Surface-level delivery versus foundational content 27:04 — Stephen Greco on moving from Markdown to JSON and YAML 29:27 — Robin Di Capua on keeping prose alongside structured data 30:56 — Stephen Greco on reference documentation versus guidance 34:05 — Question five: humans, machines, or somewhere between 35:54 — Doug Neiner's Kindle and recipe book analogy 37:14 — Shaun Bent on two clients at opposite extremes 38:41 — Afyia on not picking a side 42:30 — Hattie Tadsen on meeting people where they are 44:02 — Just-in-time documentation as the goal 45:28 — Doug Neiner on AI-generated docs and false productivity 46:22 — Afyia: don't use AI to write the docs 47:19 — Hattie Tadsen on AI-assisted first draftsWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bencallahan.com/redwoods). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comAfyia Smith is a content designer and technical writer focused on design system documentation, governance, and knowledge architecture. Connect with her: https://bit.ly/4vVUhNPGet the Raw Data Access the complete survey data from Episode 079 to conduct your own analysis: https://bit.ly/4yV4JrDReview the FigJam Notes Dig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4gismBZJoin the ConversationThe 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/answerTheQuestionMusic licensed through Soundstripe.Code: C1COHEMFO6L4XE0H

Ben Callahan and Kacey Wood, Product Designer for Design Systems at Tabs, explore the psychology behind design system buy-in, the question Kacey brought after wondering what a design systems college curriculum would actually need to cover beyond tokens and components.The survey went out to over 1,100 design system practitioners and drew 50 responses across four questions. The conversation covers reactance theory, the endowment effect, curse of knowledge, social proof, the IKEA effect, foot-in-the-door, Aristotle's modes of persuasion, and where influence ends and manipulation begins.Show Notes00:00 — Welcome and introductions00:12 — Where the question came from: a design systems degree00:43 — The people layer matters as much as IC fundamentals01:32 — The four questions we asked this week02:44 — Craft, care, and reasoning as what actually convinces03:49 — The escape route as a pressure relief valve04:25 — Reactance theory, explained through a picky eater05:31 — Telling designers they don't have to use the system05:55 — Endowment effect and resistance to change06:48 — Does reactance skew young and endowment skew experienced?07:32 — Curse of knowledge: explaining tokens on day one08:10 — Writing for the people just behind you09:07 — Social proof and design system advocate groups09:39 — How social proof showed up in the open text answers10:40 — The IKEA effect, and a listener assembling IKEA furniture11:35 — Finding the small systems already scattered across an org12:35 — Flow, difficulty, and whether adoption can be too easy13:24 — Make it so easy they can't not use it14:07 — Foot in the door: a small yes leads to a bigger yes14:48 — Broadening what counts as adoption15:20 — Aristotle's ethos, pathos, and logos16:29 — Setting up the influence versus manipulation question17:20 — Is influence versus manipulation even the right question?18:34 — Hierarchy, company values, and team goals19:04 — Power dynamics and psychological safety19:44 — Skills you don't realize you're building20:40 — Building the curriculum for the people side of the workWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bencallahan.com/redwoods). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comKacey Wood is a Product Designer for Design Systems at Tabs, previously building systems at BetMGM and EY. Connect with her here: https://bit.ly/4aOYcV0Get the Raw DataAccess the complete survey data from Episode 078 to conduct your own analysis: https://bit.ly/4w3P47vReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4fhdlkzJoin the ConversationThe 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/answerTheQuestionMusic licensed through Soundstripe.Code: XXANWFJBSMJEM81F

On Episode 078, Ben Callahan is joined by Kacey Wood, Product Designer for Design Systems at Tabs and member of Redwoods design system community. She and Ben open the floor to the community on the psychological side of systems work.The survey went out to over 1,100 design system practitioners and drew 50 responses across four questions. The community digs into reactance theory, where influence becomes manipulation, power dynamics and reporting structure, the behavioral concepts behind buy-in, and what any of this means when the consumer is an AI agent.Show Notes00:04 — Welcome and episode framing00:36 — Kacey Wood's path from data analytics to design systems01:21 — Building 0 to 1 at BetMGM, then starting over at Tabs03:45 — The four questions we asked this week04:41 — 50 responses from over 1,100 practitioners09:12 — Janesa Chan on how org placement shapes perception10:43 — Nobody relies on just one buy-in tactic11:38 — Data isn't enough, the story is what convinces12:31 — Peter Allen on collaboration versus mandate13:27 — Guy Segal challenges the influence/manipulation framing15:08 — Kacey on whether you're willing to lose16:11 — Steven Deeds on manipulation as disingenuous influence18:37 — Reactance theory, explained through a picky eater20:03 — Daniel Florez on skin in the game21:01 — Janesa Chan on giving designers the choice22:53 — Amy Ogg on power dynamics and reporting lines25:19 — Guy Segal on why educating people doesn't work28:40 — Endowment effect, curse of knowledge, social proof29:36 — The IKEA effect and giving people a win31:00 — Aristotle's modes of persuasion33:58 — Rebecca Ostrich on not condescending to people38:19 — ToniAnn Drenckhahn: design systems makes me a better person39:17 — Kyle Hyams on soft skills over craft41:22 — AI has no reactance, so what changes?43:56 — Peter Allen's personal note to his AI agentsWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bencallahan.com/redwoods). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comKacey Wood is a Product Designer for Design Systems at Tabs, previously building systems at BetMGM and EY. Connect with her here: https://bit.ly/4aOYcV0Get the Raw DataAccess the complete survey data from Episode 078 to conduct your own analysis: https://bit.ly/4w3P47vReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4fhdlkzJoin the ConversationThe 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/answerTheQuestionMusic licensed through Soundstripe.Code: XXANWFJBSMJEM81F

Ben Callahan welcomes Lauren LoPrete, Head of Design Foundations at Mercury, back to the show to talk through design system culture versus compliance—the tension between earning adoption and enforcing it. Fresh off Lauren's Config talk on design systems anarchy, the two dig into what it means to relinquish control, and why letting go tends to improve adoption rather than threaten it.The survey went to 1,105 design system practitioners and drew 61 responses across four questions. The recap covers the belief-versus-reality gap in the data, a layered model of embedding, enabling, and enforcement, the venue-and-band metaphor for systems work, how AI is reshaping who builds and who reviews, and the scope of a design foundations role that owns both the system and the tooling.Show Notes00:00 — Welcoming Lauren LoPrete back to the show00:45 — Lauren recaps her Config talk on design systems anarchy01:19 — The community's shift away from control01:55 — The episode's mood: hard-won equanimity02:29 — Becoming the ocean: a Leonard Cohen reminder03:20 — "Be the water" and the responsive web parallel04:28 — Tying back to the systems-brain mindset05:17 — Leading a team through constant industry thrash06:35 — Owning both design systems and tooling07:40 — Framing the topic: culture versus compliance08:10 — The four questions, 1,105 sent, 61 responses09:27 — Is culture bottom-up and compliance top-down?10:27 — Culture as the overlap of shared beliefs11:45 — Walking through the layers-of-governance diagram13:55 — Enforcement, enabling, embedding as seasons15:53 — Letting agents carry the enforcement layer17:26 — Documentation as the objective standard18:48 — The venue-and-band metaphor for systems19:18 — Detaching components as part of designing20:37 — Judgment, safety, and the public-channel callout21:14 — When AI empowers PMs to prototype everything22:51 — Titles dissolving into subject-matter expertise24:37 — Connecting the system to prototyping tools25:47 — Design foundations as context for agentic work26:44 — Holding two speeds at once27:34 — The relief of not being aloneWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bencallahan.com/redwoods). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comLauren LoPrete is Head of Design Foundations at Mercury and has built and led design systems at Expedia, Dropbox, and Block. Connect with her on LinkedIn: https://bit.ly/LaurenLoPreteLinkedInGet the Raw DataAccess the complete survey data from Episode 077 to conduct your own analysis: https://bit.ly/4v3uKScReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/44UhlkKJoin the ConversationThe 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/answerTheQuestionMusic licensed through Soundstripe. Codes: RWX0YUSGWXLGICPW, SBJUDQ7C3ULIOBOM

Ben Callahan hosts the Episode 077, full community deep dive with Lauren LoPrete, Head of Design Foundations at Mercury, who has built and led design systems at Expedia, Dropbox, and Block. Lauren opens with her own arc, years spent grasping for control and pressuring leadership to mandate adoption, and how things improved once she let go. From there the room takes over, working through where culture ends and compliance begins.The survey reached over 1,100 design system practitioners and drew 61 responses across four questions. The conversation moves from the belief-versus-reality gap in the data through the timing of mandates, the accessibility "Trojan horse," internal versus external culture, a layered model of embedding, enabling, and enforcement, and a long thread on AI, prototyping, and whether teams will keep caring about output. Community voices include Erin Potter, Peter Allen, Greg Johnson, Michael Warren, Guy Segal, Rebecca Ostrich, Jeff Pelletier, Kele Webner, Alicia Payette, and more.Show Notes00:00 — Cold open: a system needs an opinion00:45 — Lauren on leading her fifth design system02:30 — Giving up the fight for a leadership mandate03:30 — "Design systems are culture work in disguise"05:00 — The four questions, restated06:30 — The mood: hard-won equanimity08:10 — 1,100+ surveyed, 61 responses09:40 — The belief-versus-reality gap in the data11:30 — Erin Potter on timing and system maturity14:00 — Peter Allen on Venmo's culture-plus-mandate moment15:40 — Greg Johnson on the accessibility backdoor16:30 — Lauren on the business-value Trojan horse19:00 — Michael Warren on internal versus external culture22:00 — Ben's embedding, enabling, enforcement layers23:30 — Lauren on seasons of enforcement and flexibility25:00 — Guy Segal on layers of company culture27:00 — Designing conditions where good choices emerge30:00 — Building prototyping tools for designers first32:00 — Rebecca Ostrich on intrinsic motivation34:00 — Question four themes: letting go paid off36:00 — Jeff Pelletier on the vibe-coding-to-agentic spectrum38:00 — Michael Warren on AI being oversold41:00 — Kele Webner on prototypes with no basis in reality43:00 — Lauren on choosing influence and authority44:30 — Alicia Payette on enterprise-trained AI and risk47:00 — Peter Allen on building context for your system49:30 — Lauren's last word: same old struggles, new userWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bencallahan.com/redwoods). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comLauren LoPrete is Head of Design Foundations at Mercury and has built and led design systems at Expedia, Dropbox, and Block. Connect with her on LinkedIn: https://bit.ly/LaurenLoPreteLinkedInGet the Raw DataAccess the complete survey data from Episode 077 to conduct your own analysis: https://bit.ly/4v3uKScReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/44UhlkKJoin the ConversationThe 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/answerTheQuestionMusic licensed through Soundstripe. Codes: RWX0YUSGWXLGICPW, SBJUDQ7C3ULIOBOM

Episode 076 Recap: Enabling Craft Through a Design System with Ben Callahan and ToniAnn DrenckhahnBen Callahan and ToniAnn Drenckhahn recorded this recap the morning after their community deep dive, reflecting on what stood out from the data and the conversation. The survey went out to 1,105 design system practitioners; 64 responded. Topics include the distinction between craft and quality, two frameworks for thinking about how systems enable craft, the role of leadership in setting a craft culture, and how AI is complicating the idea of what it means to make something well.Show Notes0:02 — Ben introduces ToniAnn and the episode topic0:30 — Overview of the four survey questions3:20 — Survey methodology: 1,105 practitioners, 64 responses3:48 — ToniAnn on her expectations for the results4:05 — Tension around whether teaching craft is the DS team's job5:26 — Org size and career stage as factors in that tension6:57 — Teaching craft requires becoming educators, not just practitioners7:38 — Natural leaders and the weight of carrying craft alone8:11 — Distinguishing craft from quality: craft as input, quality as output10:55 — ToniAnn: craft is care embedded throughout the process, not just polish12:01 — Donnie's framing: craft is subjective, quality is objective12:17 — Sean's point: craft means something different for each role13:59 — AI enters: can AI produce quality without craft?15:32 — ToniAnn: craft requires care — and AI doesn't care17:08 — ToniAnn on why she resists calling AI output "crafted"19:11 — Googling the definition: "made with high skill, care, or ingenuity"19:45 — Craft requires sentience; quality may not20:39 — The order of operations framework: define quality first, then offer21:33 — When teams skip the definition and offer assets first23:08 — Leadership's role in setting and calibrating the craft bar24:06 — The build-vs-buy question and what it reveals about craft25:18 — The floor-ceiling framework: DS raises the floor, product teams set the ceiling26:38 — ToniAnn: the system as quality floor, not limiting factor27:35 — AI as a tool to test the ceiling and inform what gets encoded28:33 — ToniAnn: "Full freedom. Please do it."29:39 — Competing values framework: system teams shifting from internal to external orientation30:51 — ToniAnn on the "hold the line" era and how posture has evolved33:29 — The vision for the system has to be bigger than components34:40 — ToniAnn's takeaway: lean into the floor-ceiling narrative next week35:49 — Closing reflections from Ben and ToniAnnWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bencallahan.com/redwoods). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comToniAnn Drenckhahn is a design systems leader currently at Etsy, previously at BetMGM. Connect with ToniAnn: https://bit.ly/ToniAnnLinkedinGet the Raw DataAccess the complete survey data from Episode 076 to conduct your own analysis: https://bit.ly/4vb9CuhReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4a5V6LPJoin the ConversationThe 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

Episode 076 Deep Dive: Enabling Craft Through a Design System with Ben Callahan and ToniAnn DrenckhahnBen Callahan is joined by ToniAnn Drenckhahn, a design systems leader currently at Etsy and formerly at BetMGM, where her work on primitive components and foundational design quality prompted this episode's question. The survey drew 64 responses from 1,105 practitioners and surfaced a striking finding: not a single respondent said their organization has no craft gap. Topics include a floor-ceiling framework for how systems teams and product teams share responsibility for craft, the difference between craft and quality, community perspectives on teaching versus encoding, the role of leadership and culture, and what AI means for the future of craft as a human skill.Show Notes0:09 — Ben introduces Episode 076 and co-host ToniAnn Drenckhahn0:46 — ToniAnn on what led her to this topic: BetMGM, Etsy, and AI pressure1:49 — The arc from policing to enabling — and the pendulum swinging back2:25 — Survey overview: four questions, 1,105 practitioners, 64 responses4:46 — Ben's read of the data: "accumulated realism"5:15 — Zero respondents said their org has no craft gap5:44 — Time and authority: the two blockers named most6:42 — 72% said teach and encode both; 67% rely on opinionated components8:11 — 70% cited no shared definition or speed pressure as the root cause8:39 — ToniAnn introduces the floor-ceiling framework9:36 — Ben: the floor is what we build in; the ceiling is how it gets used10:32 — Mike Riley on the wide quality gap between adopters using the same components12:21 — Janesa Chan on guiding consumers through the contribution process13:48 — Janesa Chan on educational techniques that ebb and flow14:48 — Ilya Grey on views, floor plans, and embracing the front-end stack16:24 — ToniAnn on co-designing screens and templates with consuming teams17:21 — Vision has to go beyond components17:49 — Shaun Bent on culture and department leadership overriding education18:48 — Lauren on hiring visual designers with a systems mindset19:45 — Lauren: before that, the feedback loop was too big20:39 — Lauren on closing the loop when teams deviate (data viz token example)22:09 — Jesse James: encoding is tactical and measurable; culture takes time22:38 — Jesse James: craft is like authenticity — it takes time to become the team's voice23:36 — Greg Johnson on system maturity, adoption, and finding patterns in the wild25:54 — The order of operations diagram: offer first vs. define first26:21 — Flipping the order: define quality, then offer27:18 — What happens when systems teams only offer the basics28:16 — Workshop approaches for building a shared definition of quality28:49 — ToniAnn on the BetMGM vision work and staying out of the way30:12 — Ilya Grey on customer expectations as a layer above the quality ceiling30:41 — Robin Di Capua on defining quality across departments32:07 — Caroline Horn: what customers actually said quality means to them34:17 — Donnie D'Amato: craft is subjective, quality is objective35:15 — Donnie on the button example: readable labels vs. border radius36:40 — Robin on how even "objective" quality resists consensus38:06 — Donnie on design attractors and the best button42:18 — Peter Allen: DS solves 80% of problems, but craft still matters in the 20%42:58 — Ben: does AI lower the need to learn design at all?44:21 — Automating craft vs. automating the basics45:20 — Derek Onay: does encoding lower the skill, or free up time for it?46:44 — Ilya Grey: high-taste environments improve taste over time47:34 — ToniAnn's closing thought: using AI to democratize education, not just speed48:49 — Ashley and Casey's series on education in design systems49:18 — Ben wraps up; Donnie previews the Undefined event in NYCWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bencallahan.com/redwoods). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comToniAnn Drenckhahn is a design systems leader currently at Etsy, previously at BetMGM. Connect with ToniAnn: https://bit.ly/ToniAnnLinkedinGet the Raw DataAccess the complete survey data from Episode 076 to conduct your own analysis: https://bit.ly/4vb9CuhReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4a5V6LPJoin the ConversationThe 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

Episode 075 Recap: The Design System Identity Crisis with Ben Callahan and Cassie GroosIn this recap of Episode 075, Ben Callahan and Cassie Groos unpack what they learned from the community on the subject of the design system identity crisis. Cassie is preparing a talk on this theme for Hatch Conference in Berlin and used The Question as her research engine.The survey was sent to 1,083 design system practitioners and received 60 responses across five questions: team posture toward AI, belief in the "design systems as AI's necessary foundation" narrative, how roles have changed in the past 12 months, how respondents would redefine a design system today, and the bets they're making that might be wrong by next year. Ben and Cassie dig into what's actually driving AI adoption when only 25% believe it protects their roles, how DS practitioners can use their outsized organizational influence to own the AI quality bar, how the definition of "design system" is quietly expanding to include AI as an audience, and whether writing context files for AI means double work or just different work.Show Notes00:03 — Welcome and intro00:18 — Recap of all five survey questions and methodology: 1,083 sent, 60 responses02:25 — Acknowledging ongoing layoffs and supporting the community03:34 — A standout open response: "from clear vision to navigating the moment"04:08 — Cassie's reframe: an opportunity to decide where we end up04:48 — DS practitioners as an unseen but outsized influence in organizations06:33 — What's actually happening in Cassie's world right now: architecting under shifting ground07:40 — The tweet that kicked this all off: "we don't need component libraries anymore"08:11 — Cassie's talk at Hatch Conference, Berlin, September 1809:05 — Q1 and Q2 combined: 3 in 4 actively adopting AI; only 1 in 4 believes it protects their role10:27 — Owning AI workflows as the stronger protection narrative11:12 — Who's most protected: those managing the AIs and staying in the loop11:48 — Cassie on going straight in on AI from day one — and why12:01 — Ben's kids as gen-Z AI skeptics; the ethics of how models are trained15:04 — Question 4: what even is a design system? Neither of them can answer it cleanly15:29 — How respondents split: ~half said unchanged, ~40% said definition is expanding, ~12% not ready to define it yet16:32 — Cassie: at the top level, it's still just a system for designing stuff17:17 — Skills and agents casually showing up in answers as design system resources17:23 — Ben on culture as the real substance of a design system program18:42 — The new work layer: context files, components as data, AI-readable rules19:58 — Living in the seams: juggling human-serving and AI-serving outputs simultaneously21:18 — Why visual components won't disappear: people still like to look at things with their eyes22:46 — Token efficiency and the rising cost of AI: CRDs, compounding context, and who actually pays23:26 — Cassie: maybe we don't care — and maybe that's fine24:29 — Cassie's takeaway: want to see more demos and hear what others are actually building25:24 — Don't let pressure to adopt AI make us abandon our principles on quality and accessibility27:34 — Does Claude show up in Cassie's morning routine? Yes — Figma work via Claude Code, Copilot at work29:28 — Closing thanksWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bencallahan.com/redwoods). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comCassie Groos is a freelance design systems specialist and senior product designer currently at Unily. Connect with her on LinkedIn: https://bit.ly/4tsihGUGet the Raw DataAccess the complete survey data from Episode 075 to conduct your own analysis: https://bit.ly/4tz9kLXReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/42LJtWkJoin the ConversationThe 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

Episode 075 Deep Dive: The Design System Identity Crisis with Ben Callahan and Cassie GroosIn this deep dive, Ben Callahan is joined by Cassie Groos — a freelance design systems specialist whose work spans consultancy, multi-brand systems, and the Hermes-to-Every rebrand — to explore what she calls the design system identity crisis. Cassie comes prepared: she's building out this topic as the focus of an upcoming talk at Hatch conference, and the community survey served as her research engine.The survey was sent to 1,083 design system practitioners and received 60 responses across five questions: team posture toward AI, belief in the "design systems as AI's necessary foundation" narrative, how roles have changed in the past 12 months, how respondents would redefine a design system today, and the bets they're making that might be wrong by next year. The conversation covers layoffs and job market anxiety in the DS community, whether the "moat narrative" holds up under scrutiny, the rising cost of AI tooling and what it means for democratized access to design, and the double work of living in the seam between old and new ways of working.Show Notes00:06 — Welcome and episode intro00:41 — Cassie's background: from NectarCard and Sketch symbols to multi-brand CMS-driven systems03:10 — Connecting with the community and how The Question was designed to serve talks and articles04:06 — Walking through all five survey questions05:33 — Survey methodology: 1,083 sent, 60 responses06:01 — Acknowledging ongoing layoffs and the design systems job market07:20 — A standout open response: "from clear vision to navigating the moment"07:46 — Cassie's reframe: this is our opportunity to decide where we end up08:15 — Q1 results: ~70% leaning in or experimenting carefully09:08 — Q2 results: 75% say the "DS as AI foundation" narrative won't hold for long09:37 — Cassie's reaction: DS practitioners are used to being ahead of the curve11:03 — Protection without job protection: AI still needs systems, but not as many people17:27 — Stephen Greco on going pedal-to-metal on AI because adopters already are18:31 — Owning the AI workflow as a competitive advantage: "we're in 30 products already"19:28 — Pedro Martins on system thinking as a demonstration of AI value20:26 — The cost of AI and what it means for design system teams21:22 — Kele on AI shifting from democratization to pay-to-play23:44 — Ismail Hamila on methodology versus superficial prompting26:07 — Cassie: DS practitioners can define and own the quality bar for AI component work27:03 — Peter Allen on cutting token consumption 87% through multi-agent MCP architecture28:18 — Michael Whitaker on leaning into AI personally after a recent layoff34:00 — The double-work problem: living in the seam between old and new workflows34:46 — Cassie: use AI to generate what AI needs; humans still must check the output35:40 — Hattie Tadsen on AI burnout and the cost of learning-while-reviewing37:04 — Mike Riley on context-specific prompt files for adopting dev teams37:33 — Joanna Kirtley on team burnout from constant AI tool churn38:02 — Kevin on leadership excitement creating downstream pressure on DS readiness39:14 — Cassie on AI burnout hitting high achievers hardest41:32 — Stephen Greco on betting that humans won't read docs directly within a year42:32 — "What do we actually do with all of this?" — new FigJam section for action items43:59 — Closing thanks and Redwoods demos as a next step44:27 — Announcements: Muir Woods hike, Sparkbox, Southleft, AI and Design Systems courseWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bencallahan.com/redwoods). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comCassie Groos is a freelance design systems specialist and senior product designer currently at Unily. Connect with her on LinkedIn: https://bit.ly/4tsihGUGet the Raw DataAccess the complete survey data from Episode 075 to conduct your own analysis: https://bit.ly/4tz9kLXReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/42LJtWkJoin the ConversationThe 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

In this recap of Episode 074, Ben Callahan is joined by Kaelig Deloumeau-Pregent to share what we learned on the subject of AI and design system visibility. The conversation traces a question Kaelig first answered nearly a decade ago at a Salesforce symposium: How do we actually know how our design system is being used? We wondered how that question lands today as AI accelerates content, design, and code production.The survey was sent to over 1,000 design system practitioners and received 78 responses across four questions: (1) current level of visibility into how design system assets are used across disciplines, including by AI; (2) biggest design system concerns as agents and automation produce more content at scale; (3) how the right balance between enforcement and enablement has shifted as AI enters the picture; and (4) the one thing they'd implement today to improve visibility without becoming the design police. Ben and Kaelig dig into a striking correlation between visibility maturity and enforcement-versus-enablement preferences, the "fog of war" metaphor for systems work, why accessibility may not belong inside design systems, and what shifting roles mean for designers in an agent-driven future.Show Notes00:00 — Welcome and reintroducing Kaelig00:28 — The 2016 Salesforce symposium and a decade-old magic wand question03:03 — A business opportunity: cross-discipline visibility tooling03:39 — Walking through the four survey questions and methodology (1,000+ sent, 78 responses)05:53 — Kaelig's in-progress article and crowdsourcing community thinking08:26 — Question 1: Self-reported visibility levels and what surprised us09:14 — Why design systems are for people, and the limits of robotized outreach10:38 — Visibility as stacked layers, not a single maturity rung11:00 — Question 2: When every concern is a top concern12:24 — Why feedback loops may be the most critical concern13:04 — Question 3: The balanced split on enforcement vs. enablement14:35 — Pace layers, time, and when to enforce vs. let people roam16:35 — Does accessibility actually belong inside the design system?18:53 — Design system teams becoming the org's AI product-builder definers19:30 — Educating the designers of tomorrow (including agents)20:30 — The legal-approval bottleneck slowing AI enablement20:55 — A standout open response: lightweight embedded signal collection at the point of consumption21:46 — Just-in-time guidance and bringing developer experience to designers22:31 — Pegah Amadi's Magnolia and weaving signals into workflow23:00 — The "Fog of War" metaphor: attention as a system team's scarcest resource24:48 — Sending scouts: proactive visibility across Slack, Drive, and roadmaps27:03 — De-risking and saying no when the landscape shifts28:30 — Cheap scouting with sentiment analysis and lightweight tooling29:26 — Mapping Question 1 against Question 4: a clear visibility-to-enablement gradient31:22 — Taming chaos vs. the plateau of sameness (Polaris, CalPete, Yesenia)33:20 — Curiosity over policing: the posture of successful system teams34:23 — What this means for designers facing a big role pivot35:10 — Redwoods Community Hike at Muir Woods in June37:11 — Closing thanksWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bencallahan.com/redwoods). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comKaelig Deloumeau-Pregent is a design systems leader with experience at Salesforce, Shopify, and beyond. Connect with him on LinkedIn: https://www.linkedin.com/in/kaelig/Get the Raw DataAccess the complete survey data from Episode 074 to conduct your own analysis: https://bit.ly/4t4rYv6Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/3OWYGk3Join the ConversationThe 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

Episode 074 Deep Dive: AI and Design System Visibility with Ben Callahan and Kaelig Deloumeau-PregentIn this deep dive, Ben Callahan is joined by Kaelig Deloumeau-Pregent—a veteran design system practitioner whose career has spanned the BBC, The Guardian, Financial Times, Salesforce, Shopify, Netlify, and most recently Intuit—to explore the intersection of AI and design system visibility. Kaelig shares how a question raised back in a 2016 design systems symposium ("If you had a magic wand, what would you change?") still resonates today: practitioners want more visibility into how their systems are actually being used.The survey was sent to 1,081 design system practitioners and received 78 responses across four questions: current level of visibility into design system asset usage, biggest concerns as AI agents produce content at scale, how the enforcement vs. enablement balance has shifted with AI, and what one thing they'd implement to improve visibility without becoming the "design police." The conversation explores the "fog of war" metaphor for incomplete knowledge in systems work, the tension between surveillance and creative freedom, librarians vs. police as governance models, and how AI changes who (or what) is deviating from the system.Show Notes00:39 — Kaelig's background: from a French web agency to BBC, Guardian, FT, Salesforce, Shopify, Netlify, and Intuit06:56 — Becoming a systems thinker before "design systems" was a career07:38 — The 2016 magic-wand question and why visibility is still the wish08:34 — Walking through the four survey questions09:22 — Survey methodology: 1,081 practitioners, 78 responses10:04 — Reviewing Q1: most teams have manual or partial visibility, very few have robust automated tracking12:01 — Visibility isn't just internal; the end customer dimension and zombie code12:27 — Q2 results: AI concerns are "all of the above," and Brandon's optimistic reframe13:26 — Q3 results: enforcement vs. enablement is balanced, with 14% choosing "other"14:35 — The "fog of war" metaphor and the risk of a design system surveillance state17:02 — Peter on cultural contracting and counterbalancing forces in an org18:58 — The "helpful Clippy" view: visibility as a signal for better docs and training21:24 — Doug's question: is resistance to tracking a designer-specific concern?22:13 — Greg on discipline, rigidity, and adapting design practices for AI workflows24:22 — Lightweight, embedded signal collection at the point of consumption25:31 — Magnolia and ESLint-style "disable with a reason" patterns for design27:10 — Jeff on measuring adoption and building relationships to capture wins for leadership29:48 — Alexander on percentile-matching to surface emerging patterns and snowflakes32:02 — Pedro on treating deviations as a "confession room," not policing33:53 — The correlation between visibility (Q1) and enablement (Q4) responses35:20 — The "plateau of sameness" and how the design system kicks back at scale36:16 — ToniAnn: less visibility breeds more assumptions; talk to people37:44 — Stephen on AI flipping enforcement toward enablement, and tracking why agents deviate39:41 — Robin on enforcement and enablement as intertwined, not opposing42:00 — Greg on building decision points into AI skills and rules44:57 — Danita: what level of accountability belongs to the human using AI?45:27 — Trust cultures, talent pools, and where the cursor sits on enforcement47:38 — Non-negotiables: accessibility and regulated environments49:01 — Closing announcements: Redwoods Compass alpha, Config hike, Sparkbox, SouthleftWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bit.ly/44lzHL5). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comKaelig Deloumeau-Pregent writes about design systems and AI at https://www.kaelig.frGet the Raw DataAccess the complete survey data from Episode 074 to conduct your own analysis: https://bit.ly/4t4rYv6Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/3OWYGk3Join the ConversationThe 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

Episode 073 Recap: Design System AI Automation with Ben Callahan and Davy FungHost Ben Callahan and co-host Davy Fung, a product designer on the Atlassian Design System and host of the Design System Office Hours podcast, sit down immediately following the Episode 073 deep dive to reflect on what they heard from the community. The survey was sent to 1,077 design system practitioners and received 101 responses across four questions: what percentage of your workflow could be automated with AI today; what percentage should be automated; in what areas should we avoid AI automation and why; and what does craft mean to you in a 2026 design systems context. The conversation covers the gap between "could" and "should," the fear of loss embedded in resistance to automation, how process maturity should gate automation decisions, Bill's insight that automating broken processes masks their flaws, and the community's rich catalog of ways AI is already being put to practical, targeted use in design system workflows.Show Notes00:00 - Introduction and episode overview00:14 - Topic recap: AI as automation in design systems, four questions asked01:51 - Davy's starting point: Zero Height report showing 63% not using design system automation02:48 - Top-down AI mandates vs. practical decisions about what to automate03:18 - What's missing from the conversation: automation's impact on human connection rituals03:40 - The "could vs. should" gap: respondents who decreased their answer between Q1 and Q204:00 - What the decreasers said: loss of organizational context, institutional memory, and learning05:01 - Davy's pushback: documented knowledge scales better than single points of contact05:58 - The language of "loss" as sensitivity to losing control, not losing value06:16 - Ben's process maturity model: automate after you've learned the lessons manually07:11 - The risk of skipping straight to AI before understanding the work07:45 - Davy: scalability vs. the trap of being the sole expert in your org08:10 - Bill's insight from the deep dive: automating a process exposes its flaws — AI won't17:24 - Ben recaps Bill's argument: AI is powerful enough to automate things you shouldn't18:40 - Davy on CI pipeline linting: signals over blockers, data over gatekeeping19:55 - Ben: injecting human review earlier in the process keeps the PR doing its job20:35 - FigJam roundup: how community members are already using AI for automation21:00 - Use cases shared: single-use plugins, token automation, GitHub workflows, dashboards, prototyping21:37 - Davy: Atlassian's push toward higher-fidelity prototyping with AI tools22:35 - Davy's underrated use case: Slack MCP to capture keywords and surface support patterns23:11 - Ben: thin slices of AI help throughout the process vs. wide-scope automation24:15 - Closing reflections on craft: Samantha's quote — "AI is the average; craft is rising above it"25:21 - Thanks and outroWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bencallahan.com/redwoods). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comDavy Fung is a Product Designer on the Atlassian Design System and host of the Design System Office Hours podcast (https://bit.ly/3AQYjjI). Connect with him on LinkedIn (https://bit.ly/3XrcF2W).Get the Raw DataAccess the complete survey data from Episode 073 to conduct your own analysis: https://bit.ly/4cIjAv8Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4tW5ZHAJoin the ConversationThe 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

Episode 073 Deep Dive: Design System AI Automation with Ben Callahan and Davy FungHost Ben Callahan is joined by co-host Davy Fung, a product designer on the Atlassian Design System (previously Meta) and host of the Design System Office Hours podcast, to explore AI as automation in design systems—what could be automated, what should be automated, where practitioners draw the line, and what "craft" still means in 2026.The survey was sent to 1,077 design system practitioners and received 101 responses across four questions: what percentage of your workflow could be automated with AI today; what percentage should be automated; in what areas should we avoid AI automation and why; and what does craft mean to you in a 2026 design systems context.The conversation covers the surprising gap between "could" and "should," the risk of using AI to automate broken processes without questioning them first, the tension between deterministic tasks and those requiring human judgment, and how community remains the best antidote to feeling overwhelmed by an ever-accelerating tooling landscape.Show Notes00:00 - Introduction and welcome00:29 - Guest background: Davy Fung on design systems at Atlassian and Meta01:27 - Design System Office Hours podcast approaching episode 10001:56 - Topic framing: AI as automation in design systems02:22 - Survey overview: the four questions asked03:14 - Survey stats: 1,077 sent, 101 responses03:44 - Framing quote from Greg: craft-driven practitioners as guardrail-keepers04:37 - Q1 & Q2 findings: could vs. should be automated04:59 - Davy's reaction: Zero Height report showed 60% not using token automation05:28 - Ben's take: design systems are ripe for automation by definition09:46 - Low-level manual work as craft: some practitioners prefer curation over automation10:17 - Community opens up: automation as habit vs. automation as know-how13:00 - The "could vs. should" gap: more caution than capability suggests17:00 - Davy's workflow: starting ~60–70% of work with AI or automation support23:34 - Bill's 0%/0% answer: automation exposes flawed processes AI won't question25:27 - Key insight: automating a hard process can mask that the process itself is wrong26:33 - Stephen's framework: black-and-white tasks vs. tasks needing intelligent reasoning28:01 - Practical example: using AI to write consumer-friendly token changelog messages29:57 - Connection to Episode 072: extreme support and openness to direct conversation30:12 - Lauren: AI used to train teams on new tools, preserving human knowledge transfer33:00 - Q3: areas to avoid AI automation — relationships, decision-making, creative direction36:15 - The "CEO said something" problem: top-down AI mandates without practical grounding36:43 - Skills vs. MCP: a lively side thread from the community38:00 - Craft in 2026: intentionality, systems thinking, and human judgment43:00 - The V0/AI coding tool support burden falling unexpectedly on design system teams45:02 - Community as the antidote to feeling overwhelmed by tooling change45:31 - Doug's question: how to expose design documentation to AI via MCP46:29 - Davy's answer: Atlassian's JSON-structured content powering their ADS MCP47:28 - Closing reflections; encouragement to dig into Q4 raw answers on craft47:55 - Community updates: Redwoods writing accountability group, Guy's "Cost of Yes" article48:51 - Upcoming events: Zeroheight Converge in Newcastle (October), UX London (June, code: JOIN_BC for 20% off)49:25 - OutroWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://bencallahan.com/redwoods). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comDavy Fung is a Product Designer on the Atlassian Design System and host of the Design System Office Hours podcast (https://bit.ly/3AQYjjI). Connect with him on LinkedIn (https://bit.ly/3XrcF2W).Get the Raw DataAccess the complete survey data from Episode 073 to conduct your own analysis: https://bit.ly/4cIjAv8Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4tW5ZHAJoin the ConversationThe 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

Episode 072 Recap: Extreme Design System Support with Ben Callahan and Doug NeinerHost Ben Callahan and co-host Doug Neiner, a design system practitioner at Planview, sit down immediately following the Episode 072 deep dive to reflect on what they heard from the community. The survey was sent to 1,081 design system practitioners and received 49 responses across four questions: what support do you currently offer; how would you change it without constraints; what prevents better support; and share a story of going above and beyond. The conversation covers the standout data points: the written vs. video documentation gap, the surprisingly high rate of dev environment access, embedding, private vs. public support channels, the balance between high-touch support and burnout, and the importance of being perceived as a helper rather than a blocker.Show Notes00:00 - Introduction and episode overview 01:46 - Q1 data highlights: written vs. video documentation gap 02:13 - Dev environment access: higher than expected at nearly 50% 02:48 - Lowering the bar for video production with modern tooling 03:15 - The perfectionist/design system practitioner Venn diagram 04:00 - Q3 data: unclear ownership is low; headcount and competing priorities dominate 04:30 - What "competing priorities" really means for system teams 05:46 - Doug's support approach at Planview: docs, Slack channels, onboarding, and local debugging 07:53 - Going beyond "access": running consumer products locally for deeper support 08:28 - The most extreme example: getting an org-issued PC to support a heavy product 09:42 - DMs vs. open channels: why private requests matter for trust 10:34 - Not everyone is comfortable asking publicly—meeting people where they are 11:20 - The problem with ticketing systems and over-streamlining support11:49 - How private support builds trust that eventually leads to public participation 13:25 - Prioritizing relationship over efficiency: creating tickets on behalf of consumers 14:10 - Scale vs. effort framework for thinking about support types 15:42 - Embedding: initially looks high-effort/low-scale, but the impact compounds 16:21 - Doug on embedding: modeling behavior, referencing docs together, building self-sufficiency 17:50 - The other side: high-touch support and the risk of design system team burnout 18:47 - How to gauge when a support request warrants deep mentorship vs. a quick fix 21:56 - Recap of embedding discussion: Sean's reverse embedding process from Spotify 23:28 - Doug's one experience with reverse embedding and its lasting impact 24:06 - Alexander's story: misaligned incentives can undermine embedding programs 25:08 - Rebecca's insight: being a helper vs. a blocker, and how hard trust is to rebuild 26:06 - What embedding teaches you about your own system's pain points 26:31 - Staying connected to product work keeps system teams grounded in consumer reality 27:31 - Mapping stakeholders: identifying high-influence non-advocates and converting them 28:35 - Doug: influence can come from the product, not just the person 29:57 - AI in design system support: useful for self-service, but reduce touch points with caution 31:01 - Closing reflections and thanks 31:39 - OutroWhere to Find the HostsBen Callahan is Founder of Sparkbox and Redwoods Design System Community. Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comDoug Neiner is a Principal Software Engineer at Planview. Connect with him on LinkedIn.Get the Raw DataAccess the complete survey data from Episode 072 to conduct your own analysis: **https://bit.ly/41H6Tf7**Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: **https://bit.ly/4mm3uLZ**Join the ConversationThe 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**

Episode 072 Deep Dive: Extreme Design System Support with Ben Callahan and Doug NeinerHost Ben Callahan is joined by co-host Doug Niner, a design system practitioner at Planview, to explore extreme design system support—what it looks like, what gets in the way, and what truly moves the needle with consuming teams. The survey was sent to 1,081 design system practitioners and received 49 responses across four questions: what support do you currently offer; how would you change your program if unconstrained; what prevents better support; and share a story of going above and beyond. The conversation covers the surprising prevalence of dev environment access, the rarity and outsized impact of embedding, the tension between high-touch support and burnout, and why building trust may matter more than any specific tactic.Show Notes00:00 - Introduction and welcome 00:37 - Guest background: Doug Niner on getting into design systems at Planview 01:38 - Topic framing: what is "extreme design system support"? 02:07 - Survey overview: the four questions asked 03:34 - Survey stats: 1,081 sent, 49 responses 03:59 - Q1 findings: what support are teams currently offering? 04:30 - Reactions: video vs. written docs, dev environment access 05:27 - Video documentation: perfectionism vs. "good enough" screen recordings 06:25 - Q3 findings: headcount, bandwidth, and competing priorities dominate 07:17 - Key insight: teams know what good looks like but lack people and time 09:10 - Embedding: high effort, but potentially exponential impact through advocacy 10:10 - Community discussion: what does "embedding" actually mean? 11:07 - Sean shares his team's embedding process: runbooks and buddy systems 15:36 - Alexander: forward embedding failures vs. reverse embedding wins 17:53 - Reverse embedding: consuming team members join the design system team 19:50 - Disruption and ROI: is onboarding a stream of embeds worth it? 21:16 - Turning embedded team members into lasting design system advocates 23:09 - Rapid bug turnaround as a trust-building extreme support tactic 24:57 - Embedded collaborators as a source of honest, continuous feedback 25:53 - "Runners": rotating on-call support roles and AI-assisted quick fixes 26:45 - Rebecca on trust: being a helper vs. a blocker 27:14 - Supporting private requests alongside public channels 28:35 - Over-systematizing support and why removing friction builds trust 29:31 - Q4 stories: going above and beyond for consuming teams 29:43 - Taylor's story: building buy-in for a generational system change at Fidelity 33:12 - Doug's story: burning trust with a team and winning them back over 18 months 34:37 - Mapping stakeholders from saboteur to advocate 35:30 - Jane's perspective: extreme support drives adoption but risks burnout 36:53 - Hand-holding vs. empowerment: when is high-touch support too much? 37:19 - Transitioning from high-touch support to self-service empowerment 43:51 - Live prototyping as a low-effort, high-value support approach 45:15 - Figma detachable components and slots discussion 45:50 - Christine's bi-weekly demo program at office hours 47:56 - Closing reflections; encouragement to read Q4 survey answers 48:25 - Community updates: Redwoods, Design System Triage, Converge in Newcastle 50:09 - OutroWhere to Find the HostsBen Callahan is Founder of Sparkbox and Redwoods Design System Community. Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comDoug Neiner is a Principal Software Engineer at Planview. Connect with him on LinkedIn.Get the Raw DataAccess the complete survey data from Episode 072 to conduct your own analysis: https://bit.ly/41H6Tf7Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4mm3uLZJoin the ConversationThe 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

Episode 071 Deep Dive: The Criticality of Design Systems with Ben Callahan & Vitaly FriedmanIn Episode 071, host Ben Callahan is joined by co-host Vitaly Friedman—UX Lead, author, and founder of Smashing Conference—for a deep dive into the criticality of design systems. Vitaly brings experience from complex enterprise environments, including a multi-year engagement consolidating 199 European Parliament websites into one across 25 languages.The survey was sent to over 1,000 design system practitioners, yielding 61 responses. Participants were asked four questions through the lens of their single most critical product: (1) what level of impact would a product failure have on end users—loss of comfort, discretionary money, essential money, or life; (2) the size of their engineering team; (3) how they ensure their design system supports that criticality; and (4) whether anyone in their org is doing workflow analysis with users.Show Notes00:04  Introduction and episode overview01:48  Vitaly's background: complex systems, B2B, insurance, European Parliament03:01  The pressure of high-stakes work and measuring before/after impact05:19  Ben's upcoming book, published by Smashing Magazine05:44  Survey overview: methodology and FigJam data access06:11  Q1 Results: 57% selected "loss of essential money"; write-in responses07:08  Q2 Results: even distribution across team sizes; Cockburn's scale model08:03  Vitaly on loss of trust and reputation as missing modern categories09:29  Expanding the criticality framework for today's digital landscape10:52  Defining workflow analysis vs. task analysis14:33  Financial app example: importing a portfolio (task) vs. market analysis (workflow)15:56  Key finding: workflow analysis correlates with team size, not criticality17:23  Peter: using AI agents as a team of one to conduct workflow analysis19:41  Community discussion: respondents who selected "loss of life"20:09  David (Mayo Clinic): design system tokens and cascading patient-room risk21:32  Taylor: higher criticality means more questions and stakeholders, not a different process23:52  Vitaly: poor data visualization choices can cascade into financial loss24:20  Reference: The Fifth Discipline by Peter Senge (1990)25:08  Hattie (John Deere): autonomous vehicle safety warnings and multi-team sign-off26:41  Jesse (NAVA): public benefits delivery—if this fails, someone doesn't eat28:10  Vitaly: legacy systems as an underappreciated source of fragility and criticality30:06  Taylor: legacy is an iceberg—you don't know what you've got until you knock31:58  Kele: integrating a design system and AI tooling into existing enterprise SaaS33:17  Level-setting AI expectations with leadership35:42  Greg: AI tooling as a potential accelerator for legacy accessibility migration39:38  Vitaly: migrating away from legacy means designing the change, not just the UI40:06  Ben: FOMO-driven AI adoption decisions41:32  Taylor: legacy systems are often politically protected44:15  Ben: systems thinkers evaluated on product KPIs—structural misalignment46:35  Kele: reframing "healthy tension" as creative friction with different mandates49:22  Closing and thank-yous49:48  Redwoods membership, UX London, previous episode with HannahWhere to find the hostsBen Callahan is Founder of Sparkbox and Redwoods Design System Community. Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comVitaly Friedman is a UX Lead and founder of Smashing Conference. Connect with him on LinkedIn: https://bit.ly/43Iig8BGet the Raw DataAccess the complete survey data from Episode 071: https://bit.ly/4rYcRTkReview the FigJam notesDig into the collaborative notes from the deep dive: https://bit.ly/4bKWSltJoin the conversationParticipate in future episodes and contribute to the next survey: https://bit.ly/answerTheQuestion

Episode 071 Recap: The Criticality of Design Systems with Ben Callahan & Vitaly FriedmanIntroductionHost Ben Callahan and co-host Vitaly Friedman reflect on the insights from the Episode 071 deep dive on the criticality of design systems. Vitaly is a UX lead, founder of Smashing Conference, and practitioner working in complex enterprise environments—most recently with the European Parliament.The survey was sent to 1,069 design system practitioners and received 61 responses. Respondents were asked four questions through the lens of their single most critical product: how failure would impact end users (loss of comfort, discretionary money, essential money, or life); the size of the engineering team; how their design system supports that criticality and scale; and whether anyone in their org is doing workflow analysis with product users.Show Notes00:00 - Welcome and introductions; Vitaly reflects on surprises from the deep dive00:27 - How The Question works: survey Monday, deep dive Thursday, recap to follow01:41 - The Coburn Scale and how it shaped the survey questions03:45 - Survey results: why "loss of essential money" topped the criticality scale04:23 - Vitaly's take: loss of reputation and trust as proxies for financial loss05:30 - Write-in responses: loss of transparency, essential data, and future compatibility07:28 - Hyper-personalization and ephemeral UI: validating experiences we can't fully see08:50 - Decisions as infrastructure: encoding decisions into markdown and design systems11:57 - Automation and AI across design, code, and UI—and what that means for human oversight13:52 - "Flying blind": the risks of building layers atop systems we don't fully understand16:30 - Defining workflow analysis vs. task analysis and why it matters19:37 - The hypothesis: does higher criticality correlate with more workflow analysis? The data didn't confirm it.22:01 - What the data did show: team size as a stronger predictor than criticality25:32 - Design systems sandwiched between product teams and top-down quality guidelines29:35 - Legacy software: an underappreciated risk factor and political minefield32:39 - Migrating legacy means migrating flows, habits, and ways of working—not just UI34:46 - What Vitaly is working on: events, video courses, design patterns, and upcoming books36:14 - How to stay connected; Redwoods community open for membership---Where to Find the HostsBen Callahan is Founder of Sparkbox and Redwoods Design System Community. Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comVitaly Friedman is a UX Lead and founder of Smashing Conference. Connect with him on LinkedIn https://bit.ly/43Iig8BGet the Raw DataAccess the complete survey data from Episode 071 to conduct your own analysis: https://bit.ly/4rYcRTkReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4bKWSltJoin the ConversationThe 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

IntroductionHost Ben Callahan is joined by co-host Hannah Clarke, UI Engineer at Intapp, for a live deep dive on building design system infrastructure that lasts. The survey went to 1,061 practitioners and received 45 responses across four questions: company leadership model, dedicated team roles, who owns coded component delivery, and what actions create a system that endures. The conversation spans surprising results, web component delivery strategies, the framework agnostic debate, the unicorn-hire problem, API flexibility, and the human community that makes any system worth building.This episode is made possible by Mintlify. If your design system documentation lives in five places and satisfies no one, Mintlify can provide one beautiful, AI-powered home for everything your team builds (and the why behind those decisions).Try it free → https://bit.ly/try-mintlify (use code MINT-THEQ for 50% off Pro for 6 months)Show Notes00:02 — Welcome, Hannah's intro, and sponsor message (Mintlify)01:07 — Hannah's background: UI Engineer at Intapp, full-stack roots, how she found the design systems space03:25 — Survey overview: Four questions, 1,061 sent, 45 responses04:39 — Q1: "Led by product" came in at ~40%, surprising Ben; Hannah less shocked given her experience06:31 — Q2: Front-end dev outranked UI design in dedicated roles; reference to Sean Bent's post on design system hiring trends08:22 — Community as infrastructure: Awareness and human connection matter as much as tooling; user showcase idea from Hannah's team retro11:14 — Joshua: In-person labs where consuming teams experiment with the design system to make it feel engaging12:13 — Hannah's delivery approach: Stencil + web components, outputting to multiple NPM packages (tokens, styles, web components, React 18, React 19 + SSR)14:33 — Q4 theme: Framework agnosticism as a longevity strategy; design-side agnosticism and Penpot as a Figma alternative16:50 — Josh: Journey from web components wrapped in React to going all-in on React and why17:48 — Real challenges wrapping web components for React: Shadow DOM, team culture resistance, the "pure React" demand19:09 — Post-processing scripts on top of Stencil: Default values, required props, types files, and developer quality-of-life improvements22:50 — Guy: AI workflow from Figma to production code; using Figma Console MCP to convert prototypes into design-system-compliant files; circumventing design tools altogether27:11 — Kelly: Laid off with her entire product design org; job postings pitting design vs. engineering; the value of tight cross-discipline collaboration30:54 — Hannah: The full-stack cycle — companies oscillate between specialists and generalists at their own peril32:23 — Greg: Flipping the unicorn question — even if unicorns existed, would they want to do everything expected of them?36:05 — Amy: Designers vibe coding directly in repos; how design systems can support that workflow and reduce chaos37:31 — Joanna: Built two full implementations (React + Angular) after teams refused a framework-agnostic approach; the real costs39:30 — Sean: Extending across iOS + Android; shared tokens, consistent naming, cross-platform rituals; treating Figma as a fourth platform41:22 — Managing cross-platform parity: Manual processes, shared style layers, prioritization by demand44:09 — Hannah: Why she moved away from "just React" thinking; the unsolved mobile challenge for a three-person team46:36 — API flexibility vs. rigidity: Joanna's case for flexible APIs; Hannah and Mike on finding the balance without losing consistency51:01 — Closing remarks and community announcementsWhere to Find the HostsBen Callahan, Founder of Sparkbox and Redwoods Design System Community: https://bencallahan.comHannah Clarke, UI Engineer at Intapp: https://bit.ly/47kl2lnGet the Raw Data: https://bit.ly/3OOuU0BReview the FigJam Notes: https://bit.ly/4rxa9E8Join the Conversation: https://bit.ly/answerTheQuestion

Episode 070 Recap: Lasting Design System Infrastructure with Ben Callahan & Hannah ClarkeThis episode is made possible by Mintlify. If your design system documentation lives in five places and satisfies no one, Mintlify can provide one beautiful, AI-powered home for everything your team builds (and the why behind those decisions).Try it free → https://bit.ly/try-mintlify (use code MINT-THEQ for 50% off Pro for 6 months)IntroductionIn Episode 070 of The Question, host Ben Callahan sits down with co-host Hannah Clarke, UI Engineer at Intapp, to recap a conversation about building design system infrastructure that lasts. The episode drew from a survey sent to 1,061 design system practitioners, yielding 45 responses across four questions: which leadership model best describes your company (engineering, product, design, or balanced); which roles have at least one dedicated person on your design system team (DevOps, design ops, UI design, front-end dev); who owns responsibility for delivering coded components; and what actions create a system that endures. The conversation ranges from surprising survey results and the unicorn-hire debate to web component delivery strategies, framework agnosticism, and the human infrastructure that keeps systems alive.Show Notes00:00 — Welcome & sponsor mention (Mintlify)00:45 — Survey methodology recap: 1,061 sent, 45 responses, four questions reviewed01:20 — Q1 results: Company leadership — "led by product" dominated; why that surprised Ben but not Hannah02:35 — Low "led by design" responses: what does that say about design's seat at the table?04:47 — Q2 results: Dedicated roles — front-end dev outranked UI design, which shocked both hosts05:35 — Job posting trends: Why available design system roles skew toward design over engineering06:49 — The unicorn problem: Companies asking for one person to do it all07:20 — Greg's insight from the deep dive: "I want to use my code knowledge to do my design job better"08:01 — Hannah's perspective: Understanding design makes you a better front-end developer, but specialisms matter09:10 — Q4 highlight: "Connecting people that ask about the system — tools will keep changing, but people will keep interest alive"10:02 — Human infrastructure: Why community-building is as foundational as technical tooling11:36 — Data note: Over 60% of Q4 responses mentioned humans, people, community, champions, or trust12:22 — The cultural hurdle: Solving a technical problem doesn't mean people will adopt it13:13 — Framework agnostic vs. framework-specific: Three respondents advocated for agnosticism; Joanna's team built two separate libraries14:08 — Hannah's approach at Intapp: Why they chose Stencil + web components and the longevity thinking behind it15:43 — How they actually deliver components: NPM packages for tokens, styles, web components, React 18, and React 19/SSR18:49 — Post-processing scripts on top of Stencil: Default values, required props, types files, and developer quality-of-life improvements20:26 — Lowering the barrier to adoption: Making it painless for consuming teams to say yes21:38 — Working with teams already using Material UI: Not replacing everything, but filling the gaps24:07 — What does DevOps actually mean on a design system team day-to-day?26:14 — Hannah's surprising reality: Nearly 100% of her time is infrastructure, not component-building28:04 — Design-side agnosticism: Is Figma-lock sustainable? What Guy's team is doing differently29:30 — Treating Figma as a platform (alongside iOS, Android, web) — a mindset for longevity30:16 — Documentation-driven implementation: Defining the component as data first, then expressing it in any tool31:23 — Closing thought: Systems that last are defined above the tools, not inside themWhere to Find the HostsBen Callahan is Founder of Sparkbox and Redwoods Design System Community. Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comHannah Clarke is a UI Engineer at Intapp. Connect with her on LinkedIn: https://bit.ly/47kl2lnGet the Raw DataAccess the complete survey data from Episode 070 to conduct your own analysis: https://bit.ly/3OOuU0BReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4rxa9E8Join the ConversationThe 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

Episode 069 Recap: Rebuilding a Design System Mid-Flight with Ben Callahan & Shimaa Hassan---IntroductionIn 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 Notes0:05 — Introductions: Ben welcomes Shimaa Hassan as co-host for episode 690:18 — Episode context: rebuilding a design system mid-flight and how Ben and Shimaa connected1:00 — Survey recap: the "how often do you think about starting over?" question and why Shimaa expected a higher number1:36 — Data results: the ~50/50 split and overview of the three open-text survey questions2:30 — The "fork and maintain" approach: letting teams use the old version while building the new one3:19 — Shimaa's iterative approach: design rebuilt from scratch, engineering making incremental changes in code4:53 — Step-by-step walkthrough: how Shimaa used the existing codebase and AI tools to inform the new architecture7:29 — Systematizing what already exists: abstracting and naming tokens vs. inventing new ones8:10 — Avoiding breaking changes: the strategy of supporting the live state while layering in improvements9:29 — Finding the middle ground: honoring existing design before driving further evolution10:30 — Multiple versions vs. iterative: Guy's semantic versioning approach vs. smaller teams who can't maintain parallel systems13:30 — Taylor's poll: how few teams have actually had a formal, mandated migration period15:00 — A model for splitting system team responsibilities: dedicated evolution vs. embedded implementation support16:12 — Shimaa's experience at Square: rotation embeds and borrowing engineers between teams17:15 — Empathy building through team exchange programs: pros, cons, and the ambassador model18: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 mandates21:16 — Working with product teams: how to collaborate on patterns that are ready to be standardized22:13 — Closing thoughts and wrap-up---Where to Find the HostsBen Callahan—Founder of Sparkbox and the Redwoods Design System Community. Individual and team coaching for design system programs. https://bencallahan.comShimaa Hassan—Senior Product Designer at Remote, specializing in design systems. https://www.linkedin.com/in/shimaahassan/---Get the Raw DataAccess the complete survey data from Episode 069 to conduct your own analysis: https://bit.ly/46s0G9w---Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4aNvT8j---Join the ConversationThe 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

Episode 069 Deep Dive: Rebuilding a Design System Mid-Flight with Ben Callahan & Shimaa HassanIntroductionIn 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 HostsBen Callahan—Founder of Sparkbox and the Redwoods Design System Community. Individual and team coaching for design system programs. https://bencallahan.comShimaa Hassan—Senior Product Designer at Remote, specializing in design systems. https://www.linkedin.com/in/shimaahassan/---Get the Raw DataAccess the complete survey data from Episode 069 to conduct your own analysis: https://bit.ly/46s0G9w---Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4aNvT8j---Join the ConversationThe 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

Episode 068 Part II Deep Dive: Design Systems as AI Context with TJ PitreAired live: February 20, 2026IntroductionIn 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 Notes00:00 — Welcome; Ben sets context for the Part II deep-dive format00:25 — TJ introduces Southleft and his team's focus on AI + design systems04: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 refinement15:42 — Community discussion: single source of truth vs. federated systems15:56 — Eric Steinborn: their source of truth spans JS docs, JSON tokens, Figma, a reference site, and Storybook — and the consolidation effort underway19:57 — TJ's agentic feedback loop: docs → MCP → code generation → screenshot → validation → iteration22: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 truth31:45 — Ismail's cautionary tale: burning $10 of tokens on a poorly-architected first agent run34:04 — FigJam spotlight: NY State team's pattern engine; Jennie Yip's design system as AI infrastructure diagram44:12 — Where does Storybook fit? TJ makes the case for Storybook MCP (via Chromatic) depending on your team45:35 — Jennie Yip: how packaging everything into an MCP server eliminated AI hallucination48: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 participation54:04 — Ben's closing: raw data, FigJam, and coaching resources at https://bencallahan.comWhere to Find the HostsBen 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 DataAccess the survey data for this episode here: https://bit.ly/4apfR5vReview the FigJam NotesCommunity notes from the deep dive: https://bit.ly/4c9cvFpJoin the ConversationSubscribe to The Question and join the Redwoods community at https://bencallahan.com/thequestion.

Episode 068 Recap: Design Systems as AI Context with Ben Callahan & TJ PitreIntroductionWelcome 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:How prepared design systems are to act as reliable AI contextWhether teams are experimenting with AI-generated UIHow practitioners feel about the output—or what’s holding them backWhat followed was a nuanced, honest conversation about infrastructure, documentation, design-to-dev parity, and the emotional tension many practitioners feel in this moment.Show Notes00:00 – Introduction & Topic FramingDesign systems as AI context and acknowledging the tension around AI.06:38 – Survey Overview & Readiness DataWhy most teams feel underprepared—and why that matters.11:51 – Experimentation vs. ConfidenceMany 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 TruthHow context cascades from design to development—and where it breaks.16:11 – The Figma Bridge ExperimentUsing APIs to extract component specs and generate code with AI.17:05 – Discovering the CracksDetached 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 FidelityMetadata, ARIA labels, intent, and behavior as critical AI context.24:44 – Documentation Drift & Context SprawlAI can’t distinguish outdated documentation without human governance.29:25 – Design-to-Dev Parity WorkflowsUsing tooling to compare canonical sources and surface deviations automatically.32:57 – AI as Passenger, Not DriverKey Themes1. Infrastructure > PromptingThe 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 Prompt2024 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 DebtDetached components, missing properties, undocumented variants—AI makes hidden system debt visible.4. Documentation Is a Living SystemOutdated Confluence pages and static decks become liabilities when surfaced through LLMs. Human oversight and governance remain essential.5. AI Should Be Embedded in WorkflowNot “set it and forget it.” Involve AI throughout design, parity checks, and documentation—not just at the end.Where to Find the HostsTJ 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.comhttps://sparkbox.comGet the Raw DataAccess the complete survey data from Episode 068 to conduct your own analysis: https://bit.ly/4apfR5vReview the FigJam notesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4c9cvFpJoin the ConversationThe 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

Episode 068 Recap: Design Systems as AI Context with Ben Callahan & TJ PitreIntroductionWelcome 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 Notes00:00 - Introduction & Welcome02:10 - Survey Overview & The Emotional Landscape of AI03:27 - The Three Survey Questions04:41 - Perception vs. Reality of AI Readiness06:34 - Detached Components and Hidden Cracks08:40 - AI Slop as a Signal for System Quality09:32 - Can AI Eventually Infer Intent Without Clean Context?11:09 - The Case for Human Involvement and Original Thought13:31 - Compounding Slop: When AI Builds on Its Own Mistakes14:28 - Context Engineering vs. Vibe Coding15:06 - Evals: Having Your AI Check Your AI17:48 - The Russian Doll Method: Building Systems Atomically20:04 - Human Oversight in the AI Workflow Loop20:44 - Infrastructure Wins Over Prompting22:37 - Tools: Serena MCP and Sequential Thinking23:56 - Closing Advice: Stay Curious, Start Small25:42 - Getting Started: Claude Chat + Figma MCP27:37 - The Most Impactful Change: Run Diagnostics on Your System29: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/sequentialthinkingWhere 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 DataAccess the complete survey data from Episode 068 to conduct your own analysis (https://bit.ly/4apfR5v)Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive (https://bit.ly/4c9cvFp)Join the ConversationThe 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 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 thereExpression 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 tasksExpression is about appropriateness to context and content16:33 - Matt (New York Times): Typography, Culture, and Letting GoNYT designers are very particular about typographyPrevious systems were strict: "text-small, text-medium, text-large"Stakeholder requests: "I want 15 [pixels]"Matt's evolution: Trying to let go of rigid rulesOpportunity: When you let go, the culture of the design org can come outTension: Also creates room for chaosQuestion: 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, CompositionYesenia's framework: Push as far as possible at compositional layer before changing token layerCan do something more powerful at composition than at token levelPromo 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 notchesMuch stronger visual representationDecision criteria: Pus...

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:27 - The Blank Canvas ApproachThe risk: Standardizing too much, too earlyYesenia's system worked well for building 2016's product, but not for 2020's needsStrategy: Encourage divergence first, then converge on new patternsCan't standardize things that don't exist yetTeams sometimes jump to defining palettes and typography before understanding the productCreative exploration should continue throughout the adoption process, not just at the beginning19:10 - Seasons of Innovation and StandardizationOrganizations pendulum between differentiation/innovation and standardizationBoth don't run full steam simultaneously—it's a seasonal shiftExternal factors impact business needs, which impact design approach, which impacts what gets standardizedExample timeline: Knew token layer wasn't ready, encouraged divergence to learn what needed standardizing, then created new token architecture and consolidatedThis required thinking 3+ years in advanceDesign systems practitioners must predict the future (another skill to add to the matrix!)20:42 - Trust, Responsibility, and Where to Draw the LineOne 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' workPro...

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 dependent on sharp folks doing cultural work- Standards should be about processes for creating systems, not systems themselvesEducation 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 agoThe 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 answersResources- 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 KalbagBen 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. TopicsImposter 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 specializationSystems 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 brainCommunity 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 standardsAcademic 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 theoryAI'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 impactedThe 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 understandingResources- 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