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.
Building a New Home for the Atlassian Design System
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
"Our curators have been working for months taking presentations from little ideas to something big that advances design ops as practice."
Louis Rosenfeld Bria AlexanderDay 1 Welcome
September 23, 2024
"We translate absolute positioning from design tools into web-based layouts using row and flex concepts familiar to developers."
George Abraham Stefan IvanovDesign Systems To-Go: Reimagining Developer Handoff, and Introducing App Builder (Part 2)
October 1, 2021
"Don't think constraints are real. Executives see them as excuses for not delivering."
Jess GrecoClaiming your power: Practical tools for amplifying your unique voice
March 13, 2025
"Find somebody else with a really big problem and go solve it for them using your tools. Don’t even talk about what design is."
Robert SchwartzWe're Here for the Humans
June 9, 2017
"Destiny is the belief that a certain future outcome is predetermined regardless of the path."
Nicole AleongFuture Orientations to Everyday Life: Futures Anthropology as a Methodology
March 26, 2024
"Make sure children understand they can stop the session at any time, and confirm they really get that."
Mila Kuznetsova Lucy DentonHow Lessons Learned from Our Youngest Users Can Help Us Evolve our Practices
March 9, 2022
"Language is very important; sometimes new vocabulary helps because people didn’t have a word before."
John Mortimer Milan Guenther Lucy Ellis Patrick QuattlebaumPanel Discussion
December 3, 2024
"Accessibility used to be considered an inspiring hack, something available only to the lucky few."
Sam ProulxTo Boldly Go: The New Frontiers of Accessibility
November 18, 2022
"AI can transform accessibility by changing experiences to meet user needs in the moment."
Josh Clark Veronika KindredSentient Scenes and Radically Adaptive Experiences
June 11, 2025
