Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Summary
Having a design system is a de facto necessity when building cohesive enterprise software. The challenge is how does it all come together with a single location, a source of truth, a website? How does a cross-functional team marshal the resources with political and technical willpower to achieve this goal? It’s no easy feat as Jennie Yip, Atlassian design systems lead, explains in this Medium essay. This fireside chat will dig deeper into the problems addressed and lessons learned, with Jennie and also Charles Lee, the engineering lead. Hearing their stories will inspire and inform all of us in our design system journeys. We hope you will join us!
Key Insights
-
•
Multiple sources of truth in design systems cause inconsistencies and confusion, as seen with the button component font weight differences across specs, design files, and code.
-
•
Design systems should treat code as the source of truth while making design tools like Figma an integrated extension of that truth.
-
•
The Constellation project aims to create a single, consistent destination for design and development documentation, consolidating 50+ guidelines and 27 out of 60 components.
-
•
Collaboration between designers and engineers early in the process is critical to align priorities, avoid scope creep, and build trust.
-
•
Governance in design systems works best as shared execution through community trust and enabling teams, rather than policing or harsh compliance enforcement.
-
•
Workshops and detailed documentation are essential for onboarding new team members quickly and preserving knowledge amid team changes.
-
•
Live code examples embedded in documentation reduce maintenance burdens and ensure consumers always see current component behavior.
-
•
Versioning pace needs balancing—too frequent releases burden product teams trying to keep up and can hinder adoption.
-
•
Research methods like card sorting and usability testing directly influence information architecture and navigation improvements in the new documentation.
-
•
Buy-in from leadership and stakeholders grew through repeated demos and a unified team vision, highlighting the value and reducing skepticism over time.
Notable Quotes
"We kept feeling the same consistent pain around some truths for our design system."
"Kate said she considers live code to be the source of truth because she can't trust the design site due to inconsistencies."
"Code is definitely considered the source of truth; we're working hard to make Figma an extension of that."
"Governance is not policing; we're here to help you create the best experience and save time."
"Workshops often reveal gaps in documentation, which is a spicy take but true."
"It's really about finding a way to link all the different aspects to bring everything together to tell the story."
"Continuous adaptation is key; you're adapting to the system as much as adopting it."
"If you can't get buy-in for collaboration between engineers and designers, start from the bottom and talk more early and often."
"Updating and adopting design system components is company time, so a slower release schedule helps teams keep up."
"We absolutely need feedback loops so engineers and designers can influence the design system and keep it relevant."
Or choose a question:
More Videos
"Sponsor sessions are not sales pitches, they’re people like you, really knowledgeable, sharing great things."
Louis RosenfeldWelcome / Housekeeping
June 6, 2023
"You have to be responsible for your viewpoint—you can't claim objectivity and ignore the impact."
Paul Pangaro, PhDSystems Disciplines: Table Stakes for 21st Century Organizations
June 6, 2023
"Often we’re seen just as people who create personas or blueprints, but that’s not even what’s needed."
Dharani PereraThe mandala of service design: unlocking alignment and action through service design
November 20, 2025
"Done is better than perfect. You can always refine afterwards."
Tiffany ChengDesigning in a Pandemic: Integrating Speed and Rigor
June 9, 2022
"Conjoint analysis reveals how consumers make choices by examining trade-offs they are willing to make."
Ricardo MartinsUnlocking the power of advanced quantitative methods
March 12, 2025
"Executives first want to know what metric you will impact next quarter before approving big initiatives."
William Newton Jenny ChangHow to Lead With Data, and Without Data
June 7, 2023
"If you walk in someone else’s shoes, then you’ve taken their shoes."
Sahibzada MayedThe Politics of Radical Research: A Manifesto
March 27, 2023
"The best teams I know are a quarter ahead of the product roadmap, seeking out impactful strategic research projects themselves."
Prayag NarulaHow to Empower Your Designers to Do Good Research – And Why You Want To
June 10, 2022
"You can’t just break apart these components and type; instead, you change their properties to adjust labels, colors, or icons."
Jack BeharHow to Build Prototypes that Behave like an End-Product
December 6, 2022
