Evan Lovely (Head of Product & Engineering), Chris Bloom (Principal Front-End Engineer), Jake Love (Senior Solutions Engineer), and Brittany Smart (Solutions Engineer) join Chris to discuss the state of design systems today. Listen to hot takes on everything from the lesser known elements of successful design systems to the role vulnerability should play in your system.
Stephen Gates and Chris discuss the realities of design system leadership, unconventional sources of inspiration, and the impact of design on society.
Vojtech Miksu (Software Engineer at Uber) and Evan Lovely (Chief Architect at Knapsack) join Chris to discuss the gap between a frontend developer’s code base and what actually gets shipped, the next-gen tool (Ladle) Vojtech created to address this, and ultimately helping developers get closer to what end users experience.
Meghan Rosatelli and Saejin Choi join Chris to discuss transitioning multiple design systems into one, shifting system consumers’ mindset from working with a local system to working with a global system, and using play to drive excitement and adoption of a design system.
Nick, Ellis, and Chris discuss how News UK’s design system, NewsKit, united multiple disparate brands in a central source of truth, and how infrastructure management has helped scale design and engineering practices.
Curious about the fun parts of design systems? Check out this episode of the Design Systems Podcast featuring Davy Fung, co-host of design systems podcast Design System Office Hours, who joined Chris to talk about working creatively within design system constraints, common structures for design systems, and building a Jedi Council of Design System Advocates.
Una, Chris Bloom, and Chris Strahl talk about production-level code, the accessibility of Web3, and the new sliced bread of the web. Prepare for Una to blow your mind with how dynamic CSS can be.
Corey and Chris discuss how design systems represent an organization’s lifeblood, the sisyphean parts of design system maintenance, and what stands out about design system culture at Compass.
Matt, Veda, and Chris discuss how Matt and Veda have incorporated accessibility and inclusion into one of the world’s most well-known design systems, Spectrum. Matt shares his experience getting accessibility principles into Spectrum on the ground floor, and Veda discusses how inclusion fits into design systems.
Wayfair, the ubiquitous online retailer, is more than just wayfair.com: the company owns Perigold, Joss & Main, and Birch Lane. Neva, Rogin, and Chris discuss how Wayfair united three disparate design systems into one; the gradual process of building a holistic design system team; achieving cross-functional design system adoption, and the merits of overthinking.
Mike and Chris discuss design systems at the enterprise level, the history of systems, and UX design at the beginning of the internet.
Stephen Gates joined Chris Strahl on the podcast for a long talk about team culture, design systems, and more.
Microsoft’s Josh Cusick and Chris discuss how to convey intent when working with a design system, the importance of buy-in for a successful design system culture, and whether or not your design system will ever be finished.
Leonardo De La Rocha and Chris discuss the “federated” design system model, how to connect design systems to business needs, designing friction-free cross-platform experiences, and C-suite awareness of design needs.
Maya Hampton, product manager of REI's design system, joined Knapsack CEO Chris Strahl to discuss why design systems need to be flexible, the role of a product manager in a design system, and viewing design systems as products.
Audrey and Chris discuss the vision guiding Xero’s design system team, how co-ownership helps design system teams thrive, the processes she uses for managing a global team, and how the Xero design system team approaches modernization.
Jess Clark and Chris discuss the meaning of design systems and the potential of design systems as a service. What can design systems offer us beyond infrastructure? How can approaching design systems as products, rather than repositories, increase their capabilities?