Design System Office Hours

While we touched on teams of one, which is quite common in our community, how do we function in medium size teams of 3+ designers, and how can we effectively, and intentionally scale.

In our second episode dedicated to accessibility in design systems, Davy and PJ talk about the surface level explorations of color contrast, then learning more about how to better design for screen readers, for a better web experience.

We start our series with learning about how design systems interact and help our other team members from different disciplines. We start with Matt Petitt, Engineering Manager at Dayforce.

Davy and PJ talk in depth about the perils of chasing efficiency, and how we approach measuring effort and time-saved. And does this tie into velocity at all?

In the tough market of design team contractions, Davy and PJ talk about how to maintain focus and stability as a horizontal design practice.

On this episode, PJ talks about his time using Figma's REST API and how with so much data collected, we just need it to do a little more for us.

These have become some of our favorites, and tend to cover more ground than a typical ep. Nico, community manager for Zeplin joins as a co-host for this special ep.

Happy episode 60! Davy and PJ talk about a popular design system topic when we start out, Contributions and Federated Help. While this all sounds good, what are some of the pitfalls of relying too heavily on contributions and help from external design resources.

Is system adoption the only measure of success? Davy and PJ talk about adoption metrics we tend to tie ourselves to, and how it may not always paint the most complete picture.

Or aptly named, Color Complexity in Design by our GPT pal, Davy and PJ discuss the use or rather overuse of color in product design. When thinking about color in design systems, once again, less is most appropriate.