Skip to content

About the show

A podcast from zeroheight. Let’s be honest, design systems are full of choice wtf moments. Michelle and Luke, two of our resident design advocates, are attempting to combat this with a new regular series, where they answer a single question around design system troubles every two weeks. 

Newest episodes

Do designers need to code NOW?

47 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. The eternal question is back... do designers, especially designers on design systems, need to know how to code? Or at least know enough to be dangerous and understand what they're looking at? Luke and Michelle dive into everyone's favorite topic, which has probably changed quite a bit in the age of AI. So, do you need to open VS Code right now? Show notes Information Architecture Conference is in Philadelphia in April, and Poster Night (hosted by Michelle) has its call for posters open for a couple more weeksDesign System Report — the annual state of design systems survey, open until DecemberDS ARC — the AI readiness checker for your design system docsPiccalilli — front-end courses, and the people who make them get paidJosh W. Comeau — tutorials and courses on good front-end practiceCSS-Tricks — back in community handsFrontend Mentor — recommended in the chatW3Schools — the classic referenceA Global Design System — Brad Frost's proposal for standardised componentsLuke on BlueskyMichelle on BlueskyEmail: community@zeroheight.com

Is structured content important for design systems in the age of AI?

1 hr 0 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Luke's already rabbited on about structured content in previous episodes, but now the landscape has changed, is structured content still important? Or have LLMs changed the game and made it a moot point? In this episode, we dive into structured content, where the limits are, and what you should do to make sure your content is as readable as possible. Show notes Design systems as knowledge graphs Roam Research and Obsidian — the structured-content note tools referencedDesign System Documentation Spec W3C Design System Documentation Community Group Design Tokens Community Group — the precedent Guillaume referencedDS ARC zeroheight MCP Luke on BlueskyMichelle on BlueskyEmail: community@zeroheight.com

What should you automate in design systems?

55 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Everyone talks about how you should automate as much as possible in design systems... but what can you actually automate? Luke and Michelle go through all the things that they've had success automating and things that are better with a human touch. From script-based automation, to tool-based automation, to AI-based automation. Show notes Automating your documentation webinar and accompanying github repoDesign System Documentation Spec — what the AI audited its own output againstDesign Tokens and a Source of Truth — your first zeroheight article (March 2021), the "docs in the middle" future that still hasn't arrivedGet in touch Luke on BlueskyMichelle on BlueskyEmail: community@zeroheight.com

Similar podcasts

All episodes

Do designers need to code NOW?

47 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. The eternal question is back... do designers, especially designers on design systems, need to know how to code? Or at least know enough to be dangerous and understand what they're looking at? Luke and Michelle dive into everyone's favorite topic, which has probably changed quite a bit in the age of AI. So, do you need to open VS Code right now? Show notes Information Architecture Conference is in Philadelphia in April, and Poster Night (hosted by Michelle) has its call for posters open for a couple more weeksDesign System Report — the annual state of design systems survey, open until DecemberDS ARC — the AI readiness checker for your design system docsPiccalilli — front-end courses, and the people who make them get paidJosh W. Comeau — tutorials and courses on good front-end practiceCSS-Tricks — back in community handsFrontend Mentor — recommended in the chatW3Schools — the classic referenceA Global Design System — Brad Frost's proposal for standardised componentsLuke on BlueskyMichelle on BlueskyEmail: community@zeroheight.com

Is structured content important for design systems in the age of AI?

1 hr 0 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Luke's already rabbited on about structured content in previous episodes, but now the landscape has changed, is structured content still important? Or have LLMs changed the game and made it a moot point? In this episode, we dive into structured content, where the limits are, and what you should do to make sure your content is as readable as possible. Show notes Design systems as knowledge graphs Roam Research and Obsidian — the structured-content note tools referencedDesign System Documentation Spec W3C Design System Documentation Community Group Design Tokens Community Group — the precedent Guillaume referencedDS ARC zeroheight MCP Luke on BlueskyMichelle on BlueskyEmail: community@zeroheight.com

What should you automate in design systems?

55 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Everyone talks about how you should automate as much as possible in design systems... but what can you actually automate? Luke and Michelle go through all the things that they've had success automating and things that are better with a human touch. From script-based automation, to tool-based automation, to AI-based automation. Show notes Automating your documentation webinar and accompanying github repoDesign System Documentation Spec — what the AI audited its own output againstDesign Tokens and a Source of Truth — your first zeroheight article (March 2021), the "docs in the middle" future that still hasn't arrivedGet in touch Luke on BlueskyMichelle on BlueskyEmail: community@zeroheight.com

Are we doing motion right in design systems?

49 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. With the release of Figma Motion, we finally have a tool that talks to our design systems that do motion. So now it's time to ask the question - are we covering motion within our design systems in the right way? Show notes Introducing Figma Motion — the Config 2026 launch (24 June) that kicked this topic off: timeline on the canvas, animated components, and motion variables with modesAtlassian Design System — Motion — the foundations page Luke screen-shares, with the four principles and the semantic token bundles like motion.popup.enter; the Applying motion page covers composing custom motion, and the motion primitive component is the componentised bitUber Base — Motion — Michelle's pick, with the accessibility-first guidelines, timing and easing, transitions, the atomic animation patterns, and the motion office hoursCarbon — Motion and Material — Motion — the other tokenised examplesThe Animator's Survival Kit — book by Richard Williams Designing Interface Animation — book by Val HeadVal Head at Converge US 2023 — "Animation, Your Design System, and You!" GSAP (now owned by Webflow) and Lottie — the dev-side enablersCassie Evans' live-coded GSAP game talk — (SmashingConf Freiburg 2025, and State of the Browser 2026 has a recording with transcript)Bonnie Kate Wolf — the illustration systems workBlush — Pablo Stanley's composable illustration toolKano model — the "emotional connection has been proved" referenceLuke on BlueskyMichelle on BlueskyEmail: community@zeroheight.com — and send your design system's motion docs, we want to see them!

Is generative UI ever going to happen?

51 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. A few years ago everyone started talking about how AI-powered interfaces are going to start generating UI on the fly. But how close is that from being a reality? Have there been any advances towards it being a mainstream thing? And what do we need to know from a design systems perspective to cater towards it? Show notes Rachel-Lee Nabors — "Death of the Browser" — the talk that sparked the topicChatGPT Apps SDK — the plugin-style generative UI route, with Booking.com among the launch partnersInteractive apps in Claude (MCP Apps) — the Anthropic equivalent A2UI — Google's declarative spec letting agents send UI as component descriptions rather than executing codeThe Complete Guide to Generative UI Frameworks in 2026 — a rundown of the generative UI framework landscape, covering A2UI, CopilotKit/AG-UI, MCP Apps and moreNN/g's 10 Usability Heuristics — the "codified best practice" comparisonGeri Reid — the Converge US talk — Geri’s talk about flexibility and NewsKitGet in touch Luke on BlueskyMichelle on Bluesky

What should we call design systems?

41 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. We really screwed the pooch when it came to naming design systems. Why is the name so bad? And should we call it something else? Or should we bin the whole concept of design systems and start over in a completely decommodified way? Show notes NASA Graphics Standards Manual — the classic design handbook Luke referencesA Pattern Language — Christopher Alexander's town planning/architecture bookApple Human Interface GuidelinesAtomic Design — Brad Frost's original article, which credits the earlier pattern library workAnna Debenham and Laura Kalbag — referenced in that article as part of the originsCo-op Experience Library — Co-op's renamed design system; their follow-up post explains they changed the name because "design system" implies it's only for designers, which backs up the whole episode thesis Co-op Digital BlogValve's Handbook for New Employees — the famously flat, no-job-titles structure Luke half-remembers (it was Valve, not Epic)Luke on BlueskyMichelle on Bluesky

What is the future of agentic design systems?

44 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Agentic is the buzz word of the moment - but what does it actually mean for design systems? Luke and Michelle have a real conversation about what's hype, what's possible, and where they see it all going. Show notes Luke's webinar on automating documentation — the session covering the facts / distilled / authored bucketsTJ Pitre / Southleft — doing agentic design system work (also behind FigmaLint with Brad and Ian Frost)Sil Bormüller — founder of Into Design SystemsRomina Kavčič — The Design System Guide — the knowledge-graph-to-pattern work Luke describesDesign System Documentation Spec (DSDS) — what you're auditing zeroheight docs againstObsidian and Roam Research — knowledge-graph tools mentioned by MichelleThe Information Architecture Conference — Michelle's conference, which usually runs a knowledge graphs workshopn8n — Luke's stacked-agents automation instanceClaude Code — used in Luke's Figma-MCP-to-code component flowzeroheight MCP — for the docs-as-context part of that flowPaper — mentioned by Mark in chat for better HTML outputPencil — design-as-code tool with .pen filesPenpot — the open-source, web-dev-structured design toolGet in touch Luke on BlueskyMichelle on Bluesky

How do you get research findings back to the design system team?

52 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. We're all in agreement that UX Research and design systems should work hand in hand. But how do you actually get this to work in practice? How can UX Researchers and design systems folks work best together? What cadence should you be doing things? And should you be included research findings as part of your design system documentation? Show notes Design System Documentation Spec (DSDS)zeroheight MCPzeroheight MCP overview (help docs)Design Systems WTF #39 — Should designers know how to code?zeroheight Design Systems ReportLuke on BlueskyMichelle on Bluesky

Is Governance Just Theater?

47 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Governance seems to be one of those fancy words that gets thrown around a lot by design system people - but what level of governance is actually worthwhile, and how much of it is theater? Michelle and Luke will dive into governance, what level is good enough, and what bits they think you should scrap. Show notes Brad Frost's governance flowchart — the component approval flow Michelle borrowed and adapted: A Design System Governance Process. Also available as a Figma community file, and his lighter-touch follow-up: Master design system governance with this one weird trickNathan Curtis on governance and contribution — his writing on contribution models referenced in the episode: Contributions to Design Systems and Team Models for Scaling a Design SystemManaging Chaos: Digital Governance by Design by Lisa Welchman — Michelle's book recommendation for adding process in a way that isn't "gross", with a historical look at how web governance emerged: Rosenfeld MediaOrg Design for Design Orgs by Peter Merholz & Kristin Skinner — Luke's companion-piece recommendation on ritual and process for design teams, transferable to design systems: petermerholz.com / O'ReillyBig Vape: The Rise and Fall of Juul — the Netflix documentary on Juul and "how not to do a startup": Netflix

What do the Config 2026 announcements mean for design systems?

55 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Config 2026 happened in San Francisco last week, so we got together straight after the announcements to discuss what the announcements mean for design systems folks - from code on the canvas, to agents, skills, and connectors, to Figma Motion. What will these announcements mean for the work we do day to day? Show notes Blog post - What do the Config 2026 announcements mean for design systems?

⁠⁠Is driving adoption just a polite way of begging

40 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Adoption has been the perennial curse of design systems. Always a problem, never quite fixed, and loads of opinions about how to do it. But are we approaching it in the right way? Michelle and Luke talk about the problem with how adoption has been positioned, whether it's a tactical or cultural thing, and whether the goal should sit with design systems teams or the wider org. Show notes Design Systems are Dead. Long Live Design Systems

If AI can generate your design system docs, what does that say about how valuable those docs were in the first place?

43 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. The State of AI in Design Systems report came out recently, and it shows that everyone is using AI to create documentation. Is this a good thing? Luke and Seb dive into the question of what good documentation is, whether it's even relevant anymore and what parts we should let AI own, and the parts we need to protect.

Is Figma holding design systems back?

46 min

Is Figma holding design systems back? Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. It's the month before Config! So we're diving into a spicy topic - is Figma helping or hindering design systems? Is the future of design systems a world where Figma doesn't exist? Or are design tools like Figma essential for the work we do in design systems day to day? Show notes Figma Weave (acquisition / launch)Figma Make Kits announcementThe State of AI in Design Systems (zeroheight)Design Systems Report 2025 (zeroheight)UX Tools Design Tools SurveyConverge (zeroheight)Luke Murphy on BlueskyMichelle Chin on Bluesky

How do you make developers to care about your design system?

37 min

Episode 54 - How do you make developers to care about your design system? Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Getting developers interested in the design system still seems to be a challenge for a lot of design system teams in 2026. So how do you get them interested in what you're doing? Do you need to bribe them with snacks? Luke and Michelle discuss ways to get engineers on board, why it's essential, and common pitfalls with design systems sans developers. Show notes None this week

Is a design system mandate worth fighting for?

40 min

Episode #53 - Is a design system mandate worth fighting for? Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. The Design System Report this year suggested that the number one thing design system teams with low adoption rates were missing was a company mandate. However, is that really the thing you should be fighting for? Or is your time better spent focusing on something else? Luke and Michelle will dive into what actually drives good adoption, and whether a mandate is just a wolf in sheep's clothing. Show notes Design System Report 2026Design System Report webinar on AdoptionDesign System Report webinar on ResourcingThe QuestionRedwoods CommunityZeroheight Case Studies

Does your design system need a PM?

40 min

Episode 52 - Does your design system need a PM? Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Time for the hot takes - do design systems need product management? Or is it something that just gets in the way and stops work happening? Show notes Design System Report 2026Amy Hupe

What do you actually test?

34 min

Episode 51 - What do you actually test? Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Once you've done a first pass on anything in your design system, how do you validate it? Do you create complicated automated tests to ensure absolute consistency? Or do you even put it in front of real people to make sure it works? Show notes Rocket Surgery Made Easy by Steve KrugAXE MCP serverTetralogical - a great accessibility agency

Do MCPs care more about patterns or components?

47 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Now we're in the business of creating context for AI (ew), what is actually important when we're creating documentation that will be used by machines AND humans? Are detailed component guidelines important? Are the foundations essential to get right? Or can we rely on top-level patterns and vague guidance? Show notes How LLMs use MCPs to read your design system and how to write prompts that work with thatProduct Deep Dive Webinar: MCP, vibe coding, and your design systemPDF of A Pattern Language by Christopher Alexander et al.Google Prompting Essentials course on CourseraMarketing Against the Grain podcastAI and Design Systems course with Brad Frost, Ian Frost and TJ PitreTJ Pitre on LinkedInDom Nguyen on LinkedInSil Bormüller on LinkedIn

Are we delighting enough in our design systems?

41 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Design systems kill creativity, right? We've heard that said so many times. But are we actually taking the time to inject joy into the system itself? Not only considering it as a part of the process for what we include in the system, but also in how we do documentation, release notes, and general communication around the design system? Or controversially... is it even important? Show notes Luke’s article on delighting in design systemsSociete Generale release notes articleAaron Walter’s Heirarchy of User NeedsThe socks component in Gitlab’s Pyjamas design system

Do our design systems give new joiners anxiety?

32 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Set the scene - you've joined a new company as a product designer or engineer, and you're confronted with a massive system, with custom naming and opaque decisions. Queue anxiety. So how do we make our design systems easy to understand, and make them a strength for onboarding new joiners? Show notes Amy’s talk about jargonzh’s AI features

What will happen in design systems in 2026?

39 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. It's time to peer into the crystal ball and predict what's coming up for design systems this year and further out. Will AI take all our jobs? Are design systems becoming a thing of the past? Will we finally kill all creativity? Or are we still plodding along to general adoption? Show notes No show notes this episode!

What's with the emotional baggage with design systems?

37 min

Design system folks seem to be prone to burnout, arguments, and generally feeling underappreciated within their organizations. What makes design systems folks so prone to being loaded with additional weight? We discuss why this happens, as well as some strategies to overcome it. Show Notes Amy Hupe – "Burn baby burnout" (based on her Converge Manchester 2023 talk): https://amyhupe.co.uk/articles/burn-baby-burnout/Lauren LoPrete – "Design Systems Burnout" talk at Clarity 2021: https://www.clarityconf.com/session/design-systems-burnoutRobin Rendle – "Design Systems Burnout" newsletter: https://robinrendle.com/the-cascade/012-design-systems-burnout/Brad Frost - “Master design systems governance with this one weird trick: bradfrost.com/blog/post/master-design-system-governance-with-this-one-weird-trick/

Are we reducing complexity with design systems??

32 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. Time to get spicy... One of the big promises of the hype of design systems was that it would reduce organizational and product complexity by providing efficient, replicable ways of doing things. Now that we've bedded in, its time to ask - how much do design systems actually reduce complexity? Do they just reorganize and make complexity more palatable? Show notes Product Deep Dive on Systematizing your DocumentationMichelle’s article on structuring your design systems

Episode 44 - Should we care about consistency?

46 min

Live recording of the fortnightly podcast Design Systems WTF (back for season two!), where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with a Q&A from the live audience. A bit of a deep topic this week – how important is consistency as a concept to be aiming for with design systems? Obviously, it's one of our design systems' selling points, but in a world where we're moving more and more towards browserless, how important is component consistency, or can we see a place where foundational consistency is all we need? Show notes A List Apart - Design Dialects: Breaking the rules, not the systemVinted - Greenhouse

Are we finally at the point of contextual documentation?

39 min

Season 2 Episode 1 Design Systems WTF is the fortnightly podcast where Luke Murphy and Michelle Chin attempt to combat all the amazing wtf in design systems. In each episode, they answer a single question around design system troubles with Q&A from the live audience. We took a few months off and y'all went and changed everything... We dive into the wonderful world of contextual design systems. Do MCPs finally offer what we need to make our design systems serve information up contextually? Are there major things we need to refactor? Or is it all smoke and mirrors? Show notes:  Knowledge graphs article from ChaseLuke’s talk on Contextual DocumentationConverge videosDS Live with TJ PitreTJ Pitre on LinkedIn

Can you actually measure the ROI of a component?

24 min

Selling the value of your design system to folks who don't necessarily understand it is a difficult and thankless task. But are we trying to sell in the right things? Is it possible to put the value of our design system against the bottom line, and how far down the stack can we go? Can we actually put a dollar sign against a single component?

Should designers know how to code?

29 min

The age old question – should designers know how to code? Or more specifically, how much should designer know when it comes to code? Considering it's the medium that we're designing for, it's still surprising how much this topic splits opinion. Luke and special guest Rob Whitfield will dive into the pros and cons, and give some practical advice if you did want to delve into the witchcraft that engineers do.

Are accessibility guidelines enough to be inclusive?

25 min

Making your design system as inclusive as possible is something that I think we all agree on. However, for most systems teams, this means creating some accessibility guidelines and then ticking it off the list. Is this enough? Is there more we can be doing?

Are design systems a dead end?

31 min

Inspired by Luke's article on the death of design systems, Michelle and Luke dive into whether design systems have a future... are we at a natural point of evolution or are design systems going to go the way of the dinosaurs?

How big is too big for a design system?

27 min

How big is too big? Is there a point where your design system just becomes unwieldy? Luke and Michelle dive into this question from a previous episode, and try and figure out how you keep your design system to a manageable size. Or is that just a nice problem to have, and we should embracing our systems to grow to the size they need to be?

When is OK to snowflake?

25 min

Detach instance is a concept that has stuck fear into the hearts of design systems folks since the beginning. However, there are definitely instances where it’s totally ok to snowflake components! How should you deal with snowflakes in your system? How does this play into your overall view on flexibility, and can you actually use snowflakes as a way to determine what you should be working on?

How much is too much documentation?

27 min

Sometimes we may feel the urge to include everything in our documentation, to the point where it rivals Lord of the Rings for length and density. However, we may be doing ourselves a disservice! How much is too much documentation? How much is not enough documentation? Do we even need documentation at all? join us for the last Design Systems WTF of the year!

Where should design systems sit in your org?

29 min

Design systems should sit in the design team. Design systems should sit in the designops team. Design systems should sit in their own team. There are so many different options that are presented as the ‘truth’ when it comes to design systems and org design. Michelle and Luke are going to wade through the options, weigh up their merits and probably tear the entire thing down to the ground by the end of the half hour.

Should we get rid of infinite scroll?

27 min

Infinite scroll was designed to enhance the UX for browsing search results, but now it's often used to keep users endlessly engaged on social media. As concerns grow about its impact on mental health, especially among young people, it's time to reconsider its place in design systems. What responsibilities do we have as creators when our components contribute to these issues? In this episode, we’ll examine the ethical considerations of infinite scroll and other components, exploring how we can design more responsibly and promote healthier user experiences.

Do design systems make teams go faster?

29 min

Design systems are often hailed as the ultimate productivity boosters for devs and designers alike, but do they really deliver on that promise? We’ll explore whether design systems genuinely make teams more efficient or if they just add another layer of complexity. Tune in for a reality check on the true impact of design systems on team performance!

Why isn’t contribution the answer?

28 min

Contribution often seems like the perfect solution for scaling design systems, but is it really? We'll weigh the tough realities of managing contributions and why a federated system might not suit everyone. We'll explore the hurdles of contribution and how to decide if it's the right path for your team.

Why aren’t people contributing to the design system?

30 min

If you're struggling to get contributions to your design system, you might think it’s a governance issue. But it might not be the real issue. In this episode, we'll consider why people aren't contributing and examine factors beyond governance that might be preventing contributions. We’ll discuss the motivations and barriers that impact participation and how to foster a thriving contributor community.

Where can AI actually help with design systems?

27 min

We're cutting through the AI hype and getting to the good stuff—practical ways AI can supercharge your design system. From streamlining workflows to generating documentation, we'll explore real-world applications of AI that can make your life easier. Plus, we’ll guide you through creating a custom GPT to assist with your design system needs. Are you leveraging AI to its full potential, or are you stuck in the buzzword bubble? Join us for insights and strategies to make AI work for you!

Live from Hatch: Do we need to stop making components?

41 min

In this episode, we’re challenging the status quo of design systems by questioning the necessity of components. Are we too focused on building and maintaining a library of components when we should be thinking bigger? What if our obsession with components is actually holding back innovation? Join us as we explore whether it’s time to shift our attention away from components and consider new ways to build flexibility, scalability, and creativity into our design systems.

Why do we need to care more about patterns?

26 min

In this episode, we’re focusing on patterns, the often-overlooked pillar of your design system. Why should we focus on patterns more than components? Are your components really as reusable as you think, or are they just static building blocks without a solid pattern to guide them? 

How should we version design systems?

26 min

In this episode, we explore the enigma that is design system versioning. How do we make sense of versioning? How do you sync versions between code, design, and documentation? Maybe it’s easier to ignore versioning, but at what cost? 

Has AI made everyone a designer? A spicy conversation with Pablo Stanley

29 min

AI tools are transforming the landscape, making it easier than ever to create and design. Is this making everyone a designer? Will design system makers have to herd even more cats? We’ll be joined by special guest Pablo Stanley, the brilliant co-founder of two AI-based design tools, Musho and Lummi. We’ll unpack the potential of AI-based design tools and some risks. 

WTF happened at Config?

29 min

In this episode, we’re diving into the buzzworthy announcements and new feature releases that have the design community talking. We’ll share our opinions and insights on how these changes will impact design systems and workflows. Whether you missed the event or want a fresh perspective, tune in to catch up on all the highlights and WTF moments from Config!

How do you prove the value of design systems?

28 min

We tackle the fundamental question: “How do you prove the value of design systems?” What kind of metrics work? Why does the math seem so fuzzy? Are there any valid measurements? Based on our experiences and what we’ve seen with other teams, we share our thoughts and hot takes when it comes to advocating and validating your design system efforts.

They downsized the design system team; how do we survive?

25 min

We navigate the challenges and uncertainties that arise when a design system team undergoes downsizing or restructuring. How do the design system team and teams who use the design system cope in this situation? We explore strategies for resilience, collaboration, and innovation in the face of adversity and discover how to thrive amidst organizational changes.

What’s keeping design systems people up at night?

33 min

In this episode, we answer some interesting design system questions from the Internet. With Luke away, Dave, our Developer Advocate, will joins Michelle. Sharing insights from a developer and designer perspective, respectively. Will Dave and Michelle see eye to eye or will we agree to disagree?

Should Figma be the source of truth?

27 min

Figma is currently dominating the design landscape and with good reason. They’ve taken what we’ve done with product and UX design and allowed us to do so much more than we used to be able to. With the release and continued improvement of Dev Mode, they’re hoovering up more use cases and raising the question: are we happy with a design tool being the source of truth for all product teams?

Is using a pre-built frontend library realistic?

26 min

Today we ask, “Is using a pre-built frontend library realistic?” We look into the pros and cons of leveraging frontend libraries such as MUI, Tailwind, or Ant Design for your design system. Are these libraries a shortcut to success, or do they come with hidden complexities and limitations? Tune in as we dissect the practicality, scalability, and long-term implications of adopting these pre-built solutions for your product.

Future-proofing your design system

25 min

Design systems should reflect what’s currently in your product, but it’s tempting to future-proof them. After all, getting the system up and running was a lot of work, so what’s the harm in adding a few new things? Future us will thank our past selves, right?

See all 64 episodes

–

0 ratings from members

5
4
3
2
1

Rate this podcast

Log in to rate and review the shows you listen to.

No reviews yet — be the first member to rate "Design Systems WTF".

This podcast, its content and its artwork are not owned by, affiliated with, or endorsed by Castquire.

Keep listening

Discover more podcasts like this.

Up next

  1. Nothing queued. Use + Queue on any episode to line it up.

0:00 0:00