Davy and PJ discuss a potential trend of major design systems going from public to internal only, stressing that public documentation is the ultimate forcing function for quality and a huge win for the community.

Davy and PJ talk about the term "craft," emphasizing that high-quality design work requires designers to understand engineering constraints and that a good design system needs to provide education, not just components and prototypes.

Davy talks to PJ about his trip to see Figma's slots conference, formerly known as Schema. We talk about the releases and rejoice on a focus on the main editor again.

Davy talks to friend of the program, Ben Callahan from Sparkbox about his series The Question, which brings together design system designers bi-weekly to share and learn collaboratively in a 60-min workshop.

Davy and PJ talk about how amongst many good engineering traits, the rigor, and ways they work should be more adopted by product designers and specially us, maintainers. If we can track, version, and test our work as rigorously as engineers, we would be in a higher quality bar.

Davy talks special co-host, Guy Segal, about his first month at his new design systems job at Atlassian, and the fun of being a newbie after the first 30 days, when the going really starts getting tough.

Davy and PJ talk about the role of our designers on the ground, we call them our ambassadors. These good eggs not only inform our day-to-day product improvements, but help keep up informed across the org.

Davy with friend of the program, Chela Giraldo talk about their recent experiences looking for a new design systems, and the struggles with developing the "design system portfolio" that can tell our unique stories.

Chela has a recent post about it, which you should check out on Design System Collective.

Davy and PJ discuss the challenges and strategies for design system training, especially when it comes to Figma. We explore the line between providing direct tool training and focusing on how the design system integrates with those tools.

Davy talks about what he's seen with the popularity around (local) product systems and how you can may want to adoption via providing just some design system team support. PJ ends the convo with the lighter weight approach of supporting templates in code and design.

Another takeaway from our cross-functional discussions, how do design system team members handle disagreements with consumers, or even our own teammates?