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
"We have to go from shipping a minimal viable product to creating a minimal lovable experience."
Maria GiudiceRemaking the Making Company: Moving from Product to Experience
June 9, 2016
"Use your UX skills to design better working relationships by empathizing with colleagues like you do with users."
Christian CrumlishAMA with Christian Crumlish, author of Product Management for UX People
March 24, 2022
"When you deliver MVPs without understanding the problem fully, you end up in endless cycles of fix-it-later and rework."
Rima Campbell Amrit S BhachuIncrease Productivity and Drive Business Impact
September 24, 2024
"We still think of accessibility as a binary when it should be recognized as a continuum."
Sam ProulxTo Boldly Go: The New Frontiers of Accessibility
June 10, 2022
"Radical participatory design means community members are always present, outnumber professionals, and own the outcomes and narratives."
Victor UdoewaRadical Participatory Design: Decolonizing Participatory Design Processes
December 10, 2021
"Without a human in the loop, AI can go off and do crazy disastrous things."
Jon Fukuda Amy Evans Ignacio Martinez Joe MeersmanThe Big Question about Innovation: A Panel Discussion
September 25, 2024
"To be anti-racist, you must be trauma-informed; to be trauma-informed, you must commit to anti-racist work."
Rachael Dietkus, LCSWTrauma-Responsive Design: Reimagining the Future of Design Now
December 10, 2021
"Political leaders had to show up and just listen, without campaigning or trying to say anything."
Kyria Stephens Marlon KernerPower to Heal: Civic Design in the Aftermath of Tragedy
November 17, 2022
"The red buttons are forbidden to reduce excessive engagement — that runs counter to typical design goals."
Niko LaitinenAdaptable Org Design for Resilient Times
June 10, 2021
