The Question: Design System Collaborative Learning

Ben Callahan

The Question is a collaborative learning podcast about Design Systems. Smart people like you sign up, answer a few niche questions about design systems for each episode, and then we all get together to unpack the data we've gathered. Each week, I'll invite a new co-host to help facilitate the conversation. After the deep dive, the co-host and I record a recap of what we learned. That means, for each episode, you can listen to the recap and the full deep dive! If you're a design system practitioner, subscribe today (https://bencallahan.com/the-question) to receive an invitation to each episode. This only works if the community joins in! Stay in learning mode ❤️

  1. 19h ago ·  Bonus

    Episode 082 Recap: Design Systems for Sentient Design with Ben Callahan, Josh Clark, and Veronika Kindred

    Episode 082 Recap: Design Systems for Sentient Design with Ben Callahan, Josh Clark, and Veronika Kindred Ben 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 Veronika Where 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.com Josh Clark is principal of Big Medium and co-author of Sentient Design. Connect on LinkedIn: https://bit.ly/4wtZduO Veronika Kindred is a designer and researcher at Big Medium and co-author of Sentient Design. Connect on LinkedIn: https://bit.ly/4tmjIXv Get the Raw DataAccess the complete survey data from Episode 082 to conduct your own analysis: https://bit.ly/4ybEWcW Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4y6VPpe 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 082 Recap: Design Systems for Sentient Design with Ben Callahan, Josh Clark, and Veronika Kindred
  2. 19h ago

    Episode 082 Deep Dive: Design Systems for Sentient Design with Ben Callahan, Josh Clark, and Veronika Kindred

    Episode 082 Deep Dive: Design Systems for Sentient Design with Ben Callahan, Josh Clark, and Veronika Kindred Ben 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-up Where 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.com Josh Clark is principal of Big Medium and co-author of Sentient Design. Connect on LinkedIn: https://bit.ly/4wtZduO Veronika Kindred is a designer and researcher at Big Medium and co-author of Sentient Design. Connect on LinkedIn: https://bit.ly/4tmjIXv Get the Raw DataAccess the complete survey data from Episode 082 to conduct your own analysis: https://bit.ly/4ybEWcW Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4y6VPpe 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 082 Deep Dive: Design Systems for Sentient Design with Ben Callahan, Josh Clark, and Veronika Kindred
  3. Oct 27 ·  Bonus

    Episode 081 Recap: The Culture We Build with Ben Callahan and Shaun Bent

    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 thoughts Where 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.com Shaun Bent has led design systems at the BBC and Spotify and now runs Studio 53 Degrees. Connect with him: https://bit.ly/4jeC3lc Get the Raw DataAccess the complete survey data from Episode 081 to conduct your own analysis: https://bit.ly/4AmUT2k Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4xH36fc 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 Music licensed through Soundstripe.Code: PC5Z0DRTDVMQITVR

    Episode 081 Recap: The Culture We Build with Ben Callahan and Shaun Bent
  4. Oct 26

    Episode 081 Deep Dive: The Culture We Build with Ben Callahan and Shaun Bent

    Episode 081 Deep Dive: The Culture We Build with Ben Callahan and Shaun Bent Ben 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 one Where 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.com Shaun Bent has led design systems at the BBC and Spotify and now runs Studio 53 Degrees. Connect with him: https://bit.ly/4jeC3lc Get the Raw Data Access the complete survey data from Episode 081 to conduct your own analysis: https://bit.ly/4AmUT2k Review the FigJam Notes Dig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4xH36fc Join 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/answerTheQuestion Music licensed through Soundstripe.Code: PC5Z0DRTDVMQITVR

    Episode 081 Deep Dive: The Culture We Build with Ben Callahan and Shaun Bent
  5. Sep 23 ·  Bonus

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

    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 — Closing Where 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.com Robin Di Capua is a designer on the design system team at GetYourGuide in Zurich. Connect with him on LinkedIn: https://bit.ly/3VYboQI Taylor Cashdan is a design systems practitioner who has worked across enterprise, startup, and consulting teams. Connect with him on LinkedIn: https://bit.ly/4cZhbKq Get the Raw DataAccess the complete survey data from Episode 080 to conduct your own analysis: https://bit.ly/4c18Fx5 Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4wZmHH7 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 Music licensed through Soundstripe.Code: PC5Z0DRTDVMQITVR

    Episode 080 Recap: Visualizing Design System Health with Ben Callahan, Robin Di Capua, and Taylor Cashdan
  6. Sep 23

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

    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-up Where 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.com Robin Di Capua is a designer on the design system team at GetYourGuide in Zurich. Connect with him on LinkedIn: https://bit.ly/3VYboQI Taylor Cashdan is a design systems practitioner who has worked across enterprise, startup, and consulting teams. Connect with him on LinkedIn: https://bit.ly/4cZhbKq Get the Raw Data Access the complete survey data from Episode 080 to conduct your own analysis: https://bit.ly/4c18Fx5 Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4wZmHH7 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 Music licensed through Soundstripe.Code: PC5Z0DRTDVMQITVR

    Episode 080 Deep Dive: Visualizing Design System Health with Ben Callahan, Robin Di Capua, and Taylor Cashdan
  7. Aug 10 ·  Bonus

    Episode 079 Recap: The Evolution of Design System Documentation with Ben Callahan and Afyia Smith

    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 passion Where 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.com Afyia Smith is a content designer and technical writer focused on design system documentation, governance, and knowledge architecture. Connect with her: https://bit.ly/4vVUhNP Get the Raw DataAccess the complete survey data from Episode 079 to conduct your own analysis: https://bit.ly/4yV4JrD Review the FigJam NotesDig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4gismBZ 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 Music licensed through Soundstripe.Code: C1COHEMFO6L4XE0H

    Episode 079 Recap: The Evolution of Design System Documentation with Ben Callahan and Afyia Smith
  8. Aug 10

    Episode 079 Deep Dive: The Evolution of Design System Documentation with Ben Callahan and Afyia Smith

    Episode 079 Deep Dive: The Evolution of Design System Documentation with Ben Callahan and Afyia Smith Ben 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 drafts Where 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.com Afyia Smith is a content designer and technical writer focused on design system documentation, governance, and knowledge architecture. Connect with her: https://bit.ly/4vVUhNP Get the Raw Data Access the complete survey data from Episode 079 to conduct your own analysis: https://bit.ly/4yV4JrD Review the FigJam Notes Dig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4gismBZ 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 Music licensed through Soundstripe.Code: C1COHEMFO6L4XE0H

    Episode 079 Deep Dive: The Evolution of Design System Documentation with Ben Callahan and Afyia Smith

About

The Question is a collaborative learning podcast about Design Systems. Smart people like you sign up, answer a few niche questions about design systems for each episode, and then we all get together to unpack the data we've gathered. Each week, I'll invite a new co-host to help facilitate the conversation. After the deep dive, the co-host and I record a recap of what we learned. That means, for each episode, you can listen to the recap and the full deep dive! If you're a design system practitioner, subscribe today (https://bencallahan.com/the-question) to receive an invitation to each episode. This only works if the community joins in! Stay in learning mode ❤️

You Might Also Like