In our second recent episode about reviewing work, Davy and PJ talk about how we review output from product designers on our teams and the need to stay plugged in so we can help designers earlier in the process.

While the podcast is one form of communication, on our teams we heavily utilize async written communication methods to best spread the good work of design systems. We talk about the different methods we communicate to stakeholders and consumers of our design system artifacts, specifically, documentation.

Davy and PJ dive into the various ways we've utilized crits on our teams to both do design ops related work, but also reviewing code, in addition to design.

Topical for the time of year, Davy gets PJ to spill some beans on how to best set up designers to best prove the value of their day-to-day work in design systems.

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.