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?

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?

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!

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.

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.

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!

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.

Luke and Michelle come to you direct from Converge to talk about AI (again). Is there a place for AI in our design systems? 

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.

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!

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.

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? 

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? 

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. 

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!

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.

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.

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?

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. 

We tackle a question that often gets overlooked in the world of design systems: Is there room for fun and delight? Sure, components are the workhorses of design systems, known for their functionality and consistency, but does that mean they have to be dull? We'll explore the possibilities of infusing a bit of charm and personality into your design system. Listen in as we discuss examples of some of the more fun design systems in action, the challenges of maintaining usability while injecting creativity, and how to strike the right balance.

We dive into the ambitious idea proposed by Brad Frost: creating a global design system for everyone to use. Imagine a world where companies don't reinvent the wheel with every component they create, but instead, contribute to and utilize a shared set of resources. We tackle the big questions: Where do we start in building such a universal system? How do we address hesitations and resistance in the community? What are the potential risks and unseen challenges? 

This special episode is our love letter to the unsung heroes of the design system world. Join us as we shine a spotlight on some incredible individuals in the field who might not be on your radar yet, but definitely should be. We'll share our personal favorites, diving into the work they're doing and where you can find their contributions. Get ready to fall in love with these design system Valentines.

In this episode, we tackle the common concern—are you being too prescriptive with your design system? We'll discuss the fine line between guidance and rigidity, exploring how much prescription is too much. We'll share the pitfalls of being overly prescriptive and the chaos that can ensue from excessive flexibility.

Navigating design system contributions – how do you tell someone their component is terrible?We address many design system creators' challenges: Navigating design system contributions and giving constructive feedback. How do you effectively communicate that a contributed component may not meet the standards or expectations (i.e., they're just plain terrible)? We discuss ways to encourage improvement without demoralizing contributors. Join us as we explore best practices, real-life stories, and strategies for fostering collaboration and quality within your design system.

In this episode, we tackle the question that many ponder: Can you create a successful design system through contracted work? We explore the dynamics of working with external design teams, freelancers, or agencies to build a cohesive design system. Is it a recipe for success, or does it present unique challenges that could impact the system's effectiveness? We uncover the pros and cons of this approach and share insights on navigating the path to a thriving design system.

We have a special edition of Design Systems WTF, this time Luke will be joined by the amazing Amy Hupe! They'll be chatting about design systems and answering your questions. Get ready for a unique and interactive experience in this special “DSWTF Help Desk” episode. We're opening the floor to you, our listeners! Have a burning question about design systems or anything related? Ask us, and we'll tackle your toughest inquiries with our highly opinionated thoughts. Whether you seek career advice, design tips, or want to settle a design systems debate, we're here to help. Tune in for a one-of-a-kind Q&A session with Luke and Amy!

Today's question: Is my career doomed if I focus on design systems?We dive deep into the world of design system careers. Is focusing on design systems a career move that can make or break your professional journey? Join us as we explore the power and potential of design systems and discuss how they can shape your career in design. Is it a stepping stone to success or a potential roadblock? Tune in to discover how design systems can be your secret weapon or a career-defining challenge.

Today's question: How accessible can a design system really make a product?We explore the potential of design systems to enhance accessibility and discuss the challenges involved in achieving this goal. Are design systems the golden ticket to a more inclusive digital world?

Today's question: Should I use tokens today?DESIGN TOKENS. The saviour of our design systems, or so it seems from the amount that people hold them up as the shining light. But what's the deal with design tokens — when do they make sense for your company? What is going to happen to them in the future? And who do you listen to when it comes to doing them correctly?

Today's question: Will AI change design systems?We genuinely can't believe it's taken us three episodes to mention AI… It's obviously a hot topic at the moment, as folks are figuring out how they can use things like GPT or Dall-e to automate or generate things within their design systems, or heck, if they even should use AI in the first place because of the ethical, legal and moral risks!

Today's question: How do you reward someone for the contributions they make?From the big questions straight into the weeds! This has been a favourite question in the last few years of figuring out how to rightly reward folks for contributing, but also how to motivate them to contribute in the first place. Are shout-outs enough? Do we need to tie rewards to the wider company rewards? Should motivation to contribute be intrinsic or extrinsic? Should we be encouraging contributions at all?Resources: Amy Hupe - You design system contribution model is doomed to failEthan Marcotte - You deserve a tech unionMike Monteiro - Ruined by design

Today's question: How do you make the rest of your org care about your design system?With the current climate, budgets are being slashed left, right and center. Because of this design systems are often at the top of the list for what to put on the chopping block. So how do we make the rest of the organization care about design systems? How do we show how important it is, and how do we talk about it in the language that non-design systems folks care about? Do we need to change that when we're talking to senior leadership? How can we get the CEO to care about our design system?