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
"We give out stickers for research participation, and people get really eager to collect them all and promote research to their teams."
Molly FargotsteinMultipurpose Communication & UX Research Marketing
September 12, 2019
"The linchpin of a good design space is a high top table for ad hoc gatherings without interruptions or formal scheduling."
Dave MaloufClosing Keynote: Amplify. Not Optimize.
October 24, 2019
"I think of AI models as amanuenses, like super secretaries aiding scholars in the early modern period."
Jorge ArangoAI as Thought Partner: How to Use LLMs to Transform Your Notes (3rd of 3 seminars)
May 3, 2024
"AI-generated UX is not about replacing designers, but removing grunt work to focus on higher-order design."
Daniel J. RosenbergDesigning with and for Artificial Intelligence
August 11, 2022
"Accessibility is a key component of user experience that has been neglected and requires specialists to close the gap."
Alexis LucioScaling Accessibility Through Design Systems
June 9, 2022
"The design project tracker used 1900 Excel functions mostly for capacity planning in quarterly design cycles."
Peter BoersmaHow to Define and Maintain a DesignOps Roadmap
October 3, 2023
"Storytelling helps surface machine quirks and failures that aren't documented—AI as assistant ethnographer has great potential."
Ben Reason Aline Horta Majid Iqbal Fabiano LeoniMaking the system visible: The fastest path to better decisions
November 20, 2025
"If you don’t jump in and learn, you’ll spend your time reading stuff on it and not really understand the tech."
Peter Van Dijck Louis RosenfeldCoffee with Lou #4: Taking a Peek Under the Rosenbot's Hood
June 14, 2024
"We often adapt within imperfect systems rather than fight them outright, aiming for longer-term change."
Taylor KlassmanShaping the Next Era of UX Research: Collaborative Forum
March 11, 2025
Latest Books All books
Dig deeper with the Rosenbot
What are effective ways to include people with disabilities in generative and usability research?
Who are the multiple user types involved in designing services for public sector innovation portfolios?
How can jobs-to-be-done be applied to understand multiple roles within a complex B2B customer system?