Episode 080 Deep Dive: Visualizing Design System Health with Ben Callahan, Robin Di Capua, and Taylor Cashdan

Ben Callahan and Shaun Bent look back on the Episode 081 deep dive about how design systems shape, and are shaped by, the cultures of the organizations they serve. They walk through the four survey questions (1,124 practitioners invited, 45 responses) and talk about who decides when product priorities conflict with cohesion, how incentives shift over time, what “deciding together” looks like in practice, and a story about three teams building three tab bars.Show Notes 00:00 — Welcome and Shaun on why this topic fascinates him 00:30 — Redwoods UK meetups in London and Manchester, ahead of Converge 01:26 — Overview of the four survey questions 03:12 — Response count and where to find the raw data 03:34 — Shaun on “we decide together” topping Question 1 04:18 — How collaboration has grown as systems have matured 05:16 — Do designers care about cohesion more than engineers? 06:53 — Ben on why this is individual, not disciplinary 07:52 — The long history of systematic thinking in design and engineering 09:18 — Why is working systematically still hard? Incentives 11:22 — Autonomy as an expectation vs. what systems ask of teams 12:31 — Shaun: understand your organization’s shape or the system gets stuck 13:34 — Speed and innovation vs. quality and cohesion 14:21 — Shaun on system teams as enabling teams 15:00 — How incentives cascade from CEO vision to individual promotions 16:00 — Shaun on shifting priorities during nine years at Spotify 19:03 — Showing a system’s value when priorities keep changing 20:21 — Unpacking what “deciding together” looks like 21:24 — Choosing one or two teams to go deep with, per Christoph and Maya 22:31 — “White glove service” as a carrot for other teams 23:55 — Ben on the risk of over-supporting consuming teams 25:55 — Three moments for disagreement: before, during, and after production 26:53 — Shaun on why he didn’t check “before” in Question 2 27:29 — Shaun’s story: three teams building three tab bars 29:14 — Why one team opted out: incentives 31:09 — Closing thoughtsWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://joinredwoods.com). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comShaun Bent has led design systems at the BBC and Spotify and now runs Studio 53 Degrees. Connect with him: https://bit.ly/4jeC3lcGet the Raw DataAccess the complete survey data from Episode 081 to conduct your own analysis: https://bit.ly/4AmUT2kReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4xH36fcJoin 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: PC5Z0DRTDVMQITVR

Episode 081 Deep Dive: The Culture We Build with Ben Callahan and Shaun BentBen Callahan and Shaun Bent open the floor to the community to talk about how design system work shapes organizational culture, and how much room systems teams have to change it. Shaun has spent 15 years in design systems, including time at the BBC and nearly nine years leading design systems at Spotify. He now runs his own studio, Studio 53 Degrees, in Manchester.The conversation draws on a survey of 1,124 design system practitioners, with 45 responses to four questions. Threads include who decides when product priorities conflict with cohesion, whether system teams are a counterpower, incentives and promotion ladders, what “deciding together” actually looks like, high-touch partnerships with selected teams, and leadership sponsorship.Show Notes 00:06 — Welcome and sponsor thanks 01:15 — Shaun Bent on his background and Studio 53 Degrees 02:47 — Walking through the four survey questions and response count 05:10 — Most say product and system teams decide together 06:07 — Product team decides outnumbers system team decides five to one 06:37 — Peter on whether “decide together” is a politically astute answer 07:07 — Doug on decision-making shifting as trust and maturity grow 08:01 — Christoph asks whether design systems are always a counterpower 10:55 — Robin on aligning with leadership’s real priorities 12:21 — Product teams thinking beyond their slice scored lowest 13:19 — Horizontal vs. vertical: the tension is where the value lives 14:55 — Guy on platform thinking as a luxury and the incentive gap 16:38 — Rebecca on global thinking being the system team’s job 18:34 — Maya on system teams as “victims of our own success” 19:56 — Pedro on asking how we improve users’ lives in the rush to ship 22:49 — Brady on a split culture between UX and engineering 24:09 — Doug on developers as allies pushing designers toward the system 27:10 — Christoph on adding system adoption to promotion ladders 28:39 — Decision-making frameworks as a lever for culture change 30:32 — Shaun on assuming positive intent and jumping on a call 31:55 — Christoph on choosing two or three teams to work with closely at Zapier 35:40 — Jeremy on compromise, trade-offs, and disagree and commit 41:18 — Question 3 themes: loosen control, get closer, adapt, hold the line 43:13 — Steven on partnering with high-visibility projects and leadership demos 45:56 — Kaelig on security, risk, and compliance parallels 47:59 — Shaun on design systems as a people problem dressed up as a technical oneWhere to Find the Hosts Ben Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://joinredwoods.com). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comShaun Bent has led design systems at the BBC and Spotify and now runs Studio 53 Degrees. Connect with him: https://bit.ly/4jeC3lcGet the Raw Data Access the complete survey data from Episode 081 to conduct your own analysis: https://bit.ly/4AmUT2kReview the FigJam Notes Dig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4xH36fcJoin the Conversation The Question explores design systems topics through community research and deep-dive discussions. Participate in future episodes and contribute to the next survey: https://bit.ly/answerTheQuestionMusic licensed through Soundstripe.Code: PC5Z0DRTDVMQITVR

To celebrate 80 episodes, Ben Callahan is joined by Robin Di Capua and Taylor Cashdan, who built the Redwoods Compass, a self-reflective tool for looking at design system health without grading it.The survey went to 1,118 design system practitioners and received 52 responses to two questions, along with a first-ever homework assignment: a blank spider chart to fill in by instinct. The conversation covers what "health" even means, how the Compass's six categories emerged from Redwoods workshops, why five of those six aren't about the assets themselves, a respondent who realized mid-answer that none of their metrics measured health, and how the Compass keeps all data local.Show Notes 00:02 — Welcome to episode 080 00:15 — Introducing Robin and Taylor 01:58 — The two survey questions and spider chart homework 03:56 — What is design system health? 04:58 — Human health as an analogy 05:25 — No single indicator of health 06:49 — Redwoods action groups and the Compass's origins 07:54 — What the Compass is, and isn't 08:47 — Six categories and the spider chart 10:58 — Collecting charts to find patterns 11:34 — Workshopping the categories with Redwoods 13:08 — Five of six categories aren't about assets 13:56 — Shipping a button five hundred times 15:14 — Nobody wrote "design tokens" on a sticky note 15:45 — Pivoting from readiness to health 16:47 — Tracking change over time 17:14 — A respondent's mid-answer realization 18:43 — Validating the Compass's framing 19:47 — Why intangibles need conversation, not scores 20:50 — One tool among many 21:41 — How the Compass works locally 23:00 — zeroheight's maturity model and next week's panel 24:18 — How to share feedback 25:11 — ClosingWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://joinredwoods.com). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comRobin Di Capua is a designer on the design system team at GetYourGuide in Zurich. Connect with him on LinkedIn: https://bit.ly/3VYboQITaylor Cashdan is a design systems practitioner who has worked across enterprise, startup, and consulting teams. Connect with him on LinkedIn: https://bit.ly/4cZhbKqGet the Raw DataAccess the complete survey data from Episode 080 to conduct your own analysis: https://bit.ly/4c18Fx5Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4wZmHH7Join 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: PC5Z0DRTDVMQITVR

Ben Callahan is joined by Robin Di Capua and Taylor Cashdan, members of the Redwoods Design System Community who spent nearly a year building the Redwoods Compass. Robin has worked as a designer since 2009, has focused on systems since 2016, and recently joined the design system team at GetYourGuide in Zurich. Taylor has spent six years as a systems practitioner across enterprise, startup, and consulting teams.The survey went to more than 1,100 practitioners and received 52 responses to two questions, plus a spider chart homework assignment. During the session, participants took the Compass live and compared their gut-check charts with its results. The conversation covers voluntary adoption versus mandates, surprising gaps between charts, legacy systems in the public sector, taking the Compass as a team, and where community fits in the framework.Show Notes 00:04 — Welcome and sponsors 01:09 — zeroheight's maturity model and the Redwoods Compass 02:47 — The survey questions and spider chart homework 05:05 — "None tell me whether the programme is healthy" 05:58 — Origin story: from readiness to health 07:25 — The six Compass categories 09:44 — Setting up the FigJam exercise 12:32 — Taking the Compass: Authority 14:55 — Alignment 17:44 — Resource Lifecycle 19:06 — People 21:02 — Investment 21:33 — Infrastructure 23:54 — Defining design system health 24:31 — Voluntary use and fit as health signals 25:28 — Jesse Gardner on resisting a mandate at New York State 27:14 — Comparing spider charts 30:06 — Leo Vogel on ChatGPT's estimate vs. the Compass 30:58 — Mike Polowick on a drastic gap in People 33:34 — Jesse Gardner on legacy sites and public sector funding 34:54 — Taking the Compass as a team 37:43 — System health vs. effectiveness for your product 39:09 — Using divergence to surface expectations 40:35 — "Too busy" as unrecorded health work 41:59 — Jeremy on quick vs. considered answers 44:59 — A memorable survey answer and four acquisitions 45:49 — Mike Polowick on where community fits 48:19 — zeroheight panel and wrap-upWhere to Find the HostsBen Callahan is Founder of Sparkbox (https://sparkbox.com) and Redwoods Design System Community (https://joinredwoods.com). Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.comRobin Di Capua is a designer on the design system team at GetYourGuide in Zurich. Connect with him on LinkedIn: https://bit.ly/3VYboQITaylor Cashdan is a design systems practitioner who has worked across enterprise, startup, and consulting teams. Connect with him on LinkedIn: https://bit.ly/4cZhbKqGet the Raw Data Access the complete survey data from Episode 080 to conduct your own analysis: https://bit.ly/4c18Fx5Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4wZmHH7Join 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: PC5Z0DRTDVMQITVR

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