Design Systems WTF

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?

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.

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?

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

The challenges of integrating unique design elements, known as 'snowflakes,' are explored in depth. The discussion emphasizes balancing customization with standardization to meet diverse team needs. Governance and effective communication are vital for managing these unique components and ensuring design integrity. The speakers share personal experiences and suggest that snowflakes can reveal priorities for development. Flexibility and regular evaluations are key to maintaining a functional design system.

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!

The podcast dives into the debate on the ideal placement of design systems within organizations. It explores the potential benefits of dedicated teams versus integration within existing departments. Challenges in collaboration and the necessity of leadership support are also discussed. The conversation touches on the significance of design operations for breaking down silos and boosting productivity. Finally, a humorous vision of a secretive group shaping the future of design systems adds a fun twist to the serious discourse.

Infinite scroll was intended to enhance user experience, but it often leads to addictive habits that can impact mental health. The discussion delves into ethical responsibilities in design, exploring the balance between user engagement and well-being. It highlights the importance of mindful design choices and transparency. The potential pitfalls of gamification in apps are examined, emphasizing the need for healthier user experiences. Overall, the conversation pushes for a rethinking of engagement strategies to promote more responsible digital interactions.

Design systems are touted as productivity boosters, but do they really enhance team efficiency? The discussion reveals a dual nature: while components can foster reusability, they can also complicate workflows. The challenges of overcomplexity highlight the importance of simplicity in design. Additionally, understanding the optimal team structure is crucial for successful implementation. Real-world examples showcase the need for agility and collaboration in large organizations to truly benefit from design systems.