Episode 082 Recap: Design Systems for Sentient Design with Ben Callahan, Josh Clark, and Veronika KindredBen Callahan sits down with Josh Clark and Veronika Kindred, authors of Sentient Design, right after the Episode 082 deep dive. They cover the crowded vocabulary around generative UI, the sentient triangle and its four postures, the gap between what products ship and what design systems support, a new behavioral layer for design systems, and whether the graphical interface fades as agents take on more of the work.Show Notes00:00 — Welcome and introducing Sentient Design00:53 — Calling in from Brooklyn and Asheville01:08 — A whirlwind deep dive with a lot to process02:23 — The many names for generative UI03:26 — Why the book offers a shared vocabulary04:16 — Naming things as design systems work07:05 — What “sentient” means in this context08:07 — The sentient triangle and the four postures11:41 — Having language to classify everyday software11:58 — The layers where AI reaches systems teams14:13 — Service-minded teams taking on too much17:10 — The gap between products and systems18:14 — Small teams working together, and whether it scales19:46 — Design systems as glue against AI’s centrifugal force20:29 — Building blocks for chat and agent experiences22:15 — Veronika on “yes, and”23:09 — Shape-shifting interaction models23:47 — Alchemists and the accessibility opportunity24:48 — Objects and actions agents can operate on25:15 — Skills as an engineering-only format25:43 — Does the graphical interface fade away?26:40 — From user experience to manager experience28:24 — Where design innovation goes next29:07 — Getting the book and the community discount29:41 — Connecting with Josh and VeronikaWhere 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.comJosh Clark is principal of Big Medium and co-author of Sentient Design. Connect on LinkedIn: https://bit.ly/4wtZduOVeronika Kindred is a designer and researcher at Big Medium and co-author of Sentient Design. Connect on LinkedIn: https://bit.ly/4tmjIXvGet the Raw DataAccess the complete survey data from Episode 082 to conduct your own analysis: https://bit.ly/4ybEWcWReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4y6VPpeJoin 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 082 Deep Dive: Design Systems for Sentient Design with Ben Callahan, Josh Clark, and Veronika KindredBen Callahan is joined by Josh Clark and Veronika Kindred of Big Medium, co-authors of Sentient Design. Josh has spent about 30 years as a product designer and strategist and has run Big Medium for 25 of them. Veronika is a designer and researcher who has helped build enterprise design systems for some of the world’s biggest companies.The survey went to 1,115 design system practitioners and drew 54 responses across five questions. The conversation covers what “sentient” means, why behavior belongs in a design system, the gap between the postures products ship and what systems enable, the “armies of one” that AI makes possible, and what artifacts might hold behavior in a design system.Show Notes00:02 — Welcome and sponsors02:42 — Veronika on her path into design04:35 — Josh on 30 years and Big Medium07:51 — This week’s questions and responses09:29 — “I still feel very behind”09:58 — Even AI design leaders are still figuring it out11:55 — Christoph on teams expecting systems to have the answers13:17 — What sentient design means14:43 — Awareness, intent, and agency16:31 — The sentient triangle and four postures17:01 — Nobody said no18:17 — Veronika: which layer is the design system?19:44 — Building blocks beyond components21:38 — The gap between products and systems23:35 — Armies of one and AI’s centrifugal force25:04 — Christoph on Zapier’s system partnering with AI teams26:59 — Veronika on renewed respect for systems thinking29:14 — Chris on teams of one and teaching collaboration31:07 — AI and empathy for other roles33:25 — Working together in the code repo34:51 — Haven’t we said this before?38:12 — Tools, chat, agents, and copilots42:42 — MVC and designing the controller44:33 — Designing the physics of the universe45:31 — Intelligent canvas and the NPC pattern46:52 — Skills, Fin’s procedures, and prompt templates49:45 — Christoph on defining rules instead of components51:30 — Casual intelligence and smarter defaults53:23 — Announcements and wrap-upWhere 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.comJosh Clark is principal of Big Medium and co-author of Sentient Design. Connect on LinkedIn: https://bit.ly/4wtZduOVeronika Kindred is a designer and researcher at Big Medium and co-author of Sentient Design. Connect on LinkedIn: https://bit.ly/4tmjIXvGet the Raw DataAccess the complete survey data from Episode 082 to conduct your own analysis: https://bit.ly/4ybEWcWReview the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4y6VPpeJoin 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
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