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."
Dig deeper—ask the Rosenbot:
More Videos
"I hadn’t realized that we were both going to need that advice."
Randolph Duke IIWar Stories LIVE! Randy Duke II
March 30, 2020
"You do not have to go publicly thank the employer who just laid you off. They’ll be fine without it."
Corey Nelson Amy SanteeLayoffs
November 15, 2022
"If you measure an infinite number of customers, every change would be statistically significant, but not every change would be meaningful."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"Nudges are not a magic wand; they can help but need to fit within a larger system and behavioral pathway to truly work."
Amy BucherHarnessing behavioral science to uncover deeper truths
March 12, 2025
"Behavioral turbulence happens when flow breaks down, causing chaotic and unpredictable user interactions."
David SternbergUncovering the hidden forces shaping user behavior
July 17, 2025
"Assessing feedback urgency means understanding if the issue blocks critical work or if there are workarounds."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"Provocative prototypes provoke conversation and surface unspoken values."
Jennifer StricklandAdopting a "Design By" Method
December 9, 2021
"COVID has maybe made us a better global team by forcing us to figure out how to work across time zones and communication preferences."
Rachel Posman John CalhounA Closer Look at Team Ops and Product Ops (Two Sides of the DesignOps Coin)
November 19, 2020
"Creating and holding space is like putting bumpers up in bowling so people know they won’t fail if they engage."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
