Advertise on podcast: Design Systems WTF

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: [email protected] — and send your design system's motion docs, we want to see them!

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

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

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

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

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

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?

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

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? 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

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

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

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

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

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