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
-
•
Inconsistencies between design specs, Figma, Sketch, and code caused user confusion and mistrust of documentation.
-
•
Atlassian’s Constellation project aims to create a single source of truth unifying designer and developer documentation.
-
•
Live code examples embedded in documentation replace static images, ensuring up-to-date and interactive component previews.
-
•
Collaboration and early involvement between designers and engineers are critical to successful design system evolution.
-
•
The project spanned multiple years and team changes, requiring extensive documentation and ‘run books’ for onboarding.
-
•
Governance is framed as shared execution rather than policing, fostering buy-in instead of compliance tension.
-
•
Design tokens improve handoff accuracy, although integration with Figma is still partly manual and evolving.
-
•
Multiple local design systems coexist alongside the central system, typically as downstream consumers of core components.
-
•
Roadmap alignment between platform teams and product teams remains one of the biggest operational challenges.
-
•
Extensive user research including usability tests and tree card sorts informed navigation, IA, and content strategy.
Notable Quotes
"Kate considers live code to be the source of truth because she can’t trust the design site due to inconsistencies."
"If engineers don’t like what we’re doing, they absolutely will not adopt our design system."
"Governance shouldn’t be policing; we’re here to help create the best experience and save time."
"This project has a lot of history and required synthesizing findings from many people over years."
"Design systems reflect organizational structure – if designers and engineers are siloed, no tooling will fix that."
"Updating and adopting design system components requires company time and planning—for some teams, fast release cycles were too frequent to keep up."
"Docs as code is a philosophy that keeps documentation in workflows familiar to content designers and engineers alike."
"Prior prototypes and documentation of pain points helped pave the way and garner stakeholder buy-in for Constellation."
"We use MDX and markdown so designers can edit documentation directly through pull requests."
"Empathy on both sides is key—engineers need scoped work, designers need to understand engineering constraints."
Dig deeper—ask the Rosenbot:
More Videos
"Human translation is preferred for accuracy, though Google Translate is used occasionally for urgent needs."
Wyatt HaymanGlobal Research Panels (Videoconference)
August 8, 2020
"Naming things is the hardest thing; it’s an ongoing process involving components, their parts, and properties."
PJ Buddhari Nate BaldwinMeet Spectrum, Adobe’s Design System
June 9, 2021
"If we center design on people and place before technology, we create more meaningful futures."
Sarah GallimoreInspire Progress with Artifacts from the Future
November 18, 2022
"UXers are less satisfied than their peers because we have failed to set expectations about the real work of UX in organizations."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"If we continue to peak participants from homogenized groups, we risk perpetuating women’s everyday exclusions."
Dr. Jamika D. Burge Mansi GuptaAdvancing the Inclusion of Womxn in Research Practices (Videoconference)
September 15, 2022
"You have to understand how your company actually makes money."
Amy MarquezINVEST: Discussion
June 15, 2018
"Games are not a point in time you run away from — you don’t just drop the cartridge and walk away."
Dane DeSutter Natalie Gedeon Deborah Hendersen Cheryl PlatzBeyond the Console: The rise of the Gamer Experience and how gaming will impact UX Research across industries (Videoconference)
May 17, 2024
"If you are silent about your pain, they will kill you and say you enjoyed it."
Zariah CameronReDesigning Wellbeing for Equitable Care in the Workplace
September 23, 2024
"In design Ops, the same ADHD traits—like managing ambiguity and dynamic change—are often strengths."
Jessica NorrisADHD: A DesignOps Superpower
September 9, 2022
