Design Systems WTF

Dive into the complexities of versioning in design systems. Discover strategies for syncing design, code, and documentation effectively. Explore the unique challenges designers face compared to developers, especially with tools like Figma. Learn about the balance between detailed version tracking and user accessibility. Simplification of versioning and release notes is emphasized for better clarity. Engage in discussions around effective communication and the importance of community feedback to enhance design patterns.

Pablo Stanley, co-founder of AI design tools Musho and Lumi, dives into the fascinating world of AI-driven design in this engaging conversation. He discusses how AI tools are making design more accessible, prompting the question: has AI made everyone a designer? The chat humorously addresses challenges faced by designers in adapting AI-generated images. Pablo also highlights the balance between innovation and human creativity, illustrating how AI can enhance design processes while emphasizing the importance of retaining essential design skills.

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!

Exploring the challenges of proving the value of design systems, discussing metrics like bug ticket reduction and positive feedback. Importance of storytelling data, navigating soft skills and politics, and effective communication strategies for maintaining stakeholder buy-in.

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.

Dave, a Developer Advocate, and Michelle, a Designer, discuss challenges in transitioning between design systems and feature teams. They explore hurdles in adopting design system documentation, merging design system files, and creating systems for companies unfamiliar with complexity. The podcast also touches on challenges in transitioning to larger companies, semantic naming in typography, and navigating naming conventions in design systems.

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?

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.

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?

We examine that critical phase in the life of a design system: moving beyond the Minimum Viable Product (MVP). Launching an MVP is just the beginning, but what comes next? Michelle and Luke discuss strategies for advocating for more resources, ensuring your work is recognized and adequately resourced, and not just seen as a “free” addition from your team. Drawing from our own experiences and those of other teams, we share practical advice on selling your design system’s ongoing value to stakeholders.