Design System Office Hours

As we approach 2 years, and 50 episodes, we recap this year and dive back into how AI changed some of our thinking this year, as well as what we would like to see out of the design systems practice in 2024.

One theme that has been our mind working in large mega design teams, is how our product design teams handle outside, external POV, vs historical cannon. Davy and PJ discuss this, weaved in with how we like to evaluate potential solutions for our systems.

With convos of relying on external services such as design system docs sites, Figma plugins, or analytics, we talk about our experience working in large teams with funding to build our own, vs utilizing third party services that can simply get you up and running immediately.

Davy and PJ talk a little more in depth about support and the dangers of being a purely reactive design system team. How do you handle requests, and how to operate the program during times of duress.

Listener question: DS team of one, and how to keep afloat and keep the program going. We touch on what you might want to focus on, and getting help as soon as you can so you can scale.

We are back in your lives with a normal 1:1 with Davy and PJ about design system complexities, and how you might want to consider a system with less tokens, variants, and what it's like for Davy to manage 149 components on web alone.

Happy 40th episode birthday. We talk about moving fast vs designing and building with intentionality, and naturally the convo led morphed into a half episode about ways of partnering with product designers, and how we work on our systems at Meta and Pinterest.

With DS being table stakes on lots of product design teams, and even job postings, we talk about whether you need one, or whether your efforts should be scaled elsewhere. What are you really getting yourself into when you start this journey..

Davy comes back from Config 2023, pondering life in and outside of the file, and some rapid fire QA with Davy and PJ. (01:25) Config 2023 IRL recap. (22:10) IntoDS, Future of Design Systems talk QA.

One of Davy's favorite parts of being an IC is being able to still build components, and chase Figma's quest for excellence. Davy and PJ talk about the approach their teams take for building and maintaining design components, alignment with code source of truth, and staying away from uber components.

We’ve been following Masato’s project, designsystem.careers for a while now, and given the nature of the design job economy, wanted to pick his brain on how we can better interview design system designers and engineers.

As design system maintainers, we have the unique role of being deeply entrenched in our own product roadmaps. How can we find opportunity areas and advocate for what we think is best for our consumers? Can we even achieve this within a given time frame. Davy PM and PJ talk about how this has worked at Meta and Pinterest.

Governance doesn't have to be a bad work, but can define how you convey intent through your system. We love governing so much, there's some bits and pieces that we covered in Ep 15: Support.

What happens when we get lost on our own sauce, our presentations, decks, vision work, and forget about the tactical and operational work we need to do so we can keep the design systems train moving along.

We made it to episode 30! It's about time we talked about Design Delivery and why design system maintainers are so passionate about it. Can we as a design and product team agree to deliver artifacts, in one single format? I bet the design systems team can help with a framework for that.

With all this chat (pun included) about ChatGPT, how else can we utilize some programmable help with AI and automation. Plus, the differences between a sweet potato and a yam. 

Davy and PJ answer listener questions that came in from some friends of the program. We touch on fun component library design only components, governance, office hours issue tracking, documentation, interviewing, and much more.

With the rise of design system teams in orgs, Davy and PJ talk about how their roles have progressed through product design, and design ops. How have things changed while we have come in and out of IC <> management? Today in our roles, what does IC leadership in Design Systems look like for us?

Welcome to the show 2023, even tho this was recorded in 2022. This is the last of our trilogy series, about how to get started in Design Systems. What happens after you get to year 2 and so on? Is your job done because everyone is bought in and good actors and advocates supporting the system?

2nd in our series of the first years of design systems, Davy and PJ talk about how to grow the team, and where we have decided on our teams to focus on; which of the design system knobs, library, education, documentation, we decided to turn.

Originally episode 21, if not for our last special episode on layoffs, we talk about how to get a design system up and running, and things we looked to achieve in years 0-1. This ep is the first in a series of 3 episodes about getting started in design systems.

During this rough week at Meta and Twitter, Davy and PJ discuss how to continuously prove ROI for yourself and your team in the light of operating on leaner teams. 

Happy Halloween and 20th episode to us! Davy and PJ talk about how their teams support educating designers and the continuous task of training product designers, whether they are new to the org, or just new to the design system.

Davy and PJ talk about different design system team make ups at Disney Streaming, Meta, and Pinterest. How federated vs centralized have worked for them; and how big does your team need to be?

Davy and PJ talk about how they're thinking about contribution models on their teams and mechanisms to get better XFN collaboration between design and engineering.

Davy and PJ react to the earth-shattering news that Adobe is “teaming up" with Figma, and what that may or may not mean to us.

Davy and PJ discuss issues with copy cat design patterns and frameworks. What might work for your company may not work for the next. Design systems is not one size fits all, but fits most.

Davy talks with PJ about various ways of automating design system and design ops tasks to help our day-to-day lives as worker-bees easier.

Davy and PJ talk about their methods of design systems support, ranging from Davy's fave, Office Hours, to async support on Slack. A good episode candidate to do design systems bingo/drinking game. 

PJ grills Davy about his super organized and sometimes outrageous file hygiene mandates he lead while working at Disney Streaming. How can you use organization and naming to drive better alignment across design and engineering partners?

Davy and PJ talk about how we've incorporated design and engineering user feedback on our design system work. Leaning into surveys, PJ has had great success half-over-half by employing a new product framework.. listening. 

Davy talks about speaking at his first design conference last month, UXDX. We talk about how to find your voice and how to get started for those whom want to engage more with the product design community.

We took a long Memorial Day vacay and back to talk about adoption methods and get how to get designers excited to use your design system. Chatter about how different strategies apply for differing scale of teams. 

Happy 10th episode birthday! We wanted to take a look at and see, knowing what we've known about working on design systems at our companies, what we wish we would have known had we started today.

We're almost at episode 10, and we're here to talk about ROI, driving impact. It has to do with learning what leadership's LOVE LANGUAGE is.

We talk about a fun topic of scale, how to support multiple brands under 1 design system. Davy talks a bit about considerations when designing across Disney+ and Star+ and the usage of theming to design for one system in whole.

We've polled our listeners and heard that JIRA was their favorite design tool, over Figma. So we decided to talk about how we've utilized JIRA as Design System product owners and how it's impacted the way we plan our work.

Mandates, governance, we discuss how our orgs approach the mandates for usage of the Design Systems.

Is your work in Figma a Design System? We chat about how design artifacts and tools are just one portion of what a system represents.